Archiving / record invalidation feature

elixir-luxembourg / data-catalog

GNU Affero General Public License v3.0

0 stars 1 forks source link

Archiving / record invalidation feature #13

Open vildead opened 1 year ago

vildead commented 1 year ago

Snapshot of the record (metadata) shall be retained and moved to “archived” section or somehow separated from "active" records.

This action will require several steps:

add statement of the in-availability of the dataset or link to new resource where the dataset can be reached
display new date (archival date)

vildead commented 4 months ago

2024-06-18 meeting - it was decided it can be called "deprication"

vildead commented 2 months ago

This can require more heavy updates on DAISY side to avoid inconsistencies.

Naturally, the deprecation is linked to the Exposure of a dataset in DAISY. That would allow deprecate records in different catalogs.

Alternatively, it can be status of a dataset in DAISY (if ever anything like this comes. That would deprecate records in all catalogs (makes sense as the daisy record is about "active" use including also hosting).

vildead commented 2 months ago

DC JSON files can have "depricated" flag, "deprication date" and "deprication note". The same should be on the level of exposure whenever the exposure is marked as deleted (that might be actually deprecated button).

The disclaimer about deprication shall be displayed with date and the note/reason on the dataset page (top - highlighted ribbon). All deprecated datasets should be removed from the index.