Open milanmajchrak opened 6 months ago
Provenance issue - the provenance info wasn't added into metadata like in the v5
Now the provenance is added when:
Discussion - the provenance could be added when:
- 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):
Summary:
[x] Add\Update\Remove Item's metadata
[x] Add\Update Bitstream's metadata
[x] Add/Remove bitstream
[x] Update/Remove Item's license
[x] Add/Remove item policies - access control
[x] Add/Remove bitstream policies - access control
[x] Move item to another collection
[x] Make item non-discoverable
[x] Approved by
[x] withdraw/reinstate
[x] item created = Submitted by / Made available - Is that enough?
[x] in_archive - Approved for entry into archive by...
[x] manage mapped collections
[x] Submitter id changed - for now I cannot add this provenance - because there is not option for submitter changing (I cannot find it)
[x] withdrawn reason - for now dspace doesn't support this function [added to https://github.com/dataquest-dev/dspace-angular/issues/590 ]
Original issue: https://github.com/ufal/clarin-dspace/issues/1111
Analysis:
Item editing - add, remove, update license, metadata, bitstream, rights item - update, embargo
Item management withdrawn, rejacted, submitted, transformed, reinstated, approved, made available