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

Metadata edits and provenance #643

Open
milanmajchrak opened this issue Apr 25, 2024 · 3 comments · May be fixed by #730
Open

Metadata edits and provenance #643

milanmajchrak opened this issue Apr 25, 2024 · 3 comments · May be fixed by #730

Comments

@milanmajchrak
Copy link
Collaborator

milanmajchrak commented Apr 25, 2024

Original issue: ufal#1111

Analysis:

Item editing - add, remove, update
license, metadata, bitstream, rights
item - update, embargo

Item management
withdrawn, rejacted, submitted, transformed, reinstated, approved, made available

@milanmajchrak
Copy link
Collaborator Author

Provenance issue - the provenance info wasn't added into metadata like in the v5

Now the provenance is added when:

  • Add/Update/Remove Item's metadata
  • Add/Update/Remove Bitstream's metadata
  • Change Item's license
  • Change embargo

Discussion - the provenance could be added when:

  1. Add a new bitstream
  2. Submitter id changed
  3. Approved by
    (not in v5)
  4. Move item to another collection
  5. Make item non-discoverable
  6. Manage mapped collections
  7. Edit item’s authorization policies

@kosarko
Copy link

kosarko commented Aug 15, 2024

  • Add a new bitstream

Add/Remove bitstream

  • Submitter id changed

urcite

  • Approved by
    (not in v5)

Tohle je workflow? Podle me se reject (vcetne duvodu)/approve zapisuje i v clarin-dspace v5

  • Move item to another collection

To by asi bylo fajn. Dle kolekce (vlastne komunity) se vybira handle prefix. Takze nejakej zaznam zmenila se kolekce by mohl pomoct najit proc ma item jinej prefix nez admin ceka.

  • Make item non-discoverable

toggle public/private

  • Manage mapped collections

To ve v5 asi neni, ale pokud to neni narocnej projekt...

  • Edit item’s authorization policies

Tady mam obavu, ze by to mohlo byt hodne zmen. Policies se updatujou (v databazi), nebo se pridavaj nove. Ono je na nich nejake valid from-to...


jeste asi nekolik dalsich (ono to mozna bude ve vanille):

  1. item created
  2. item in_archive
  3. withdraw/reinstate item (tam do provenance davame i withdrawn reason)

@Paurikova2
Copy link
Collaborator

Paurikova2 commented Aug 19, 2024

Summary:

  • Add\Update\Remove Item's metadata

  • Add\Update Bitstream's metadata

  • Add/Remove bitstream

  • Update/Remove Item's license

  • Add/Remove item policies - access control

  • Add/Remove bitstream policies - access control

  • Move item to another collection

  • Make item non-discoverable

  • Approved by

  • withdraw/reinstate

  • item created = Submitted by / Made available - Is that enough?

  • in_archive - Approved for entry into archive by...

  • manage mapped collections

  • Submitter id changed - for now I cannot add this provenance - because there is not option for submitter changing (I cannot find it)

  • withdrawn reason - for now dspace doesn't support this function [added to https://github.com/Reason for withdrawal dspace-angular#590 ]

@Paurikova2 Paurikova2 mentioned this issue Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants