Closed reliztrent closed 6 years ago
We should also consider using two Rights-related metadata fields:
This would be key in helping our metadata to be re-used in other systems, so that it is easy to parse dynamic vs free text rights statements
As per discussion on 18-June-2018:
license
and rights_statement
will be required fields.rights
in the metadata JSON should be used to populate license
rights
is None
then set license
to All rights reserved
. Else, accept the value as-is with no transformation.rights_statement
to In Copyright
license
to All rights reserved
rights_statement
to In Copyright
Alternative representation:
LD/RDF | Sufia label | Hyrax label | Migration - from GWSS | Migration - ETDs from ProQuest, and Hyrax 1 --> 2 upgrade |
---|---|---|---|---|
dc:rights | Rights | License | From GWSS: If None --> All rights reserved , else migrate as-is |
Set to All rights reserved |
edm:rights | N/A | Rights Statement | Set to In Copyright |
Set to In Copyright |
Suggest replacing "All Rights Reserved" rights statement (which is a retired Europeana statement) with "In Copyright" http://rightsstatements.org/page/InC/1.0 statement