You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Option(s) for creating Digital Objects pre-populated with specified and/or inherited metadata values
A) Digital Object Template
Users create a Template for a particular type of Digital Object, pre-populated with specified metadata values
Example use case:
When creating a Collection for a particular Newspaper, users could select to use a Digital Object template for ADOs with a type of ‘NewspaperIssue’ containing metadata (such as Publisher, Subjects) common to all issues in this Newspaper Collection
And/or:
B) Option to inherit metadata values from Parent Objects/Collections
Users could choose to pre-populate new Digital Objects added to a Collection (or other type of Parent-Child relationship setup) with metadata values from the Parent
Example use case:
When creating a Collection for a particular Newspaper, all new/added (child) ADOs with a type of ‘NewspaperIssue’ would inherit certain common metadata (such as Publisher, Subjects) from the Parent Newspaper Collection
@DiegoPino and @pcambra, placing these both together for now, to keep the discussion about different approaches to this topic rolling. What are your thoughts?
The text was updated successfully, but these errors were encountered:
A generic metadata injector for any new Object (into the Widget probably)
A configurable Source
A Cleaner to remove non sense
Correct inheritance (that is easy)
A config form to set this up. Actually all this can be also Metadata of the Collection itself (means the Collection stores what it can share with others)
An "Ingest" into this collection button with some triggers (and a button/Task link) on each Object that we allow so (Newspapers, collections, etc)
What is needed?
Option(s) for creating Digital Objects pre-populated with specified and/or inherited metadata values
A) Digital Object Template
And/or:
B) Option to inherit metadata values from Parent Objects/Collections
@DiegoPino and @pcambra, placing these both together for now, to keep the discussion about different approaches to this topic rolling. What are your thoughts?
The text was updated successfully, but these errors were encountered: