what happened to retired status

geonetwork / core-geonetwork

GeoNetwork is a catalog application to manage spatially referenced resources. It provides powerful metadata editing and search functions as well as an interactive web map viewer. It is currently used in numerous Spatial Data Infrastructure initiatives across the world.

http://geonetwork-opensource.org/

GNU General Public License v2.0

412 stars 487 forks source link

what happened to retired status #5835

Open pvgenuchten opened 3 years ago

pvgenuchten commented 3 years ago

Before the workspace-workflow was merged, there was an option to set the state of records to 'retired'. This option seems not available anymore. Has i been an intentional choice to remove this status? If not, is there work envisioned to restore the functionality?

fxprunayre commented 3 years ago

Should be around https://github.com/geonetwork/core-geonetwork/blob/main/web/src/main/webapp/WEB-INF/classes/setup/sql/data/data-db-default.sql#L529 ...

archaeogeek commented 3 years ago

@fxprunayre Afaict it is only possible to set the status of a submitted working copy record to retired. It is not possible to set the status of an approved record. This seems wrong to me- is it expected behaviour?

josegar74 commented 3 years ago

There is no much documentation about this Retired status: https://geonetwork-opensource.org/manuals/trunk/en/user-guide/workflow/life-cycle.html

@archaeogeek some questions about the Retired status:

I understand only makes sense to set that status for metadata that are in Approved?
If the metadata is also published, I understand that should be also unpublished?
I understood from older versions that the metadata in this status was not searchable (at least in the search UI) or I'm wrong? Doesn't seem the case in the current version.

archaeogeek commented 3 years ago

@josegar74 yes- you should definitely be able to set the status of an Approved record to Retired. I think the behaviour in older versions is that it is unpublished. I think it is still searchable in the UI (in 3.4.4 at least) and I would like it to stay that way if possible.