Closed NancyL closed 3 years ago
We're going to add it as a bflc property.
hmm, they are still not collapsible if the field is mandatory or already has metadata in it. I think there were requests for this as well.
I don't know if I follow the concern/issue/comment, @NancyL . What aren't collapsible if which field is mandatory?
oops sorry. It ended up on the wrong hub somehow. Sorry, nothing at all to do with this! And thank you for responding to me so quickly.
Sinopia, in part, makes use of un-nested profiles in order that we can relate resource templates bi-directionally, so that we relate the work to an instance and an instance to a work. One template we are not able to do this using BF vocabulary is bf:adminMetadata. We are temporarily going to use bflc:target, but it would make more sense to have the inverse property bf:adminMetadataFor.