Open NancyL opened 4 years ago
Do we want this for other RTs? (Cartographic, Rare Materials, Serials?)
Yes, I'll do this in the serials unnested RTs. I think we should add it to unnested Works too.
So the question has changed somewhat. Do we want admin metadata un-nested as well? This way people could create individual templates for their institutions with defaults filled in.
Hello, There’s something to be said for that approach. Besides setting defaults, one could also use an unnested template to provided admin metadata for works if we ever decide that’s desirable.
Robert
Robert J. Rohrbacher Metadata Librarian for Social Sciences and Government Documents Metadata Dept. Stanford University Libraries phone: 650-725-7992 fax: 650-725-1120 rrohrbac@stanford.edu
From: NancyL notifications@github.com Sent: Friday, March 20, 2020 2:18 PM To: LD4P/ld4ptemplates ld4ptemplates@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [LD4P/ld4ptemplates] add AdminMetadata RT to Instance RT for monographs (#40)
So the question has changed somewhat. Do we want admin metadata un-nested as well? This way people could create individual templates for their institutions with defaults filled in.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/LD4P/ld4ptemplates/issues/40#issuecomment-601914735, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALOX3DBF7ESNP6LMI477BRLRIPMQRANCNFSM4KH7EAZQ.
I'm ok with this for all the above reasons -- being able to apply it as need is identified to Works, Instances, and Items and to facilitate local customized templates.
In dev server. Since the name RT is shared with all provision activities, role appears with all of them.
ld4p:RT:bf2:Monograph:Work:Un-nested and ld4p:RT:bf2:Monograph:Work
There has been a request to add the admin metadata RT to Instance RTs. This is particularly valuable for un-nested templates, where the two templates are separated, but it may be the case even with a nested template that the admin metadata differs