Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option(s) for creating Digital Objects pre-populated with specified and/or inherited metadata values #105

Open
alliomeria opened this issue Feb 26, 2021 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@alliomeria
Copy link
Contributor

What is needed?

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?

@alliomeria alliomeria added the enhancement New feature or request label Feb 26, 2021
@DiegoPino
Copy link
Member

OK! This sounds like fun

So for this I need:

  1. A generic metadata injector for any new Object (into the Widget probably)
  2. A configurable Source
  3. A Cleaner to remove non sense
  4. Correct inheritance (that is easy)
  5. 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)
  6. An "Ingest" into this collection button with some triggers (and a button/Task link) on each Object that we allow so (Newspapers, collections, etc)

Cool!

@DiegoPino
Copy link
Member

Let's talk about this one next week. It will improve a lot of things. RE: larger discussion -> Collection managment: maybe time to reply to this one?

https://groups.google.com/g/archipelago-commons/c/MQHUxU3_9wA/m/xmL7_rXWFQAJ

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants