Participants:

Esme Cowles, chair (UC San Diego)
kestlund (Oregon)
Nick Ruest (York)

References

Archives Hub: http://data.archiveshub.ac.uk/def/
Creative Commons: http://creativecommons.org/ns
DC/DC Terms: http://dublincore.org/documents/dcmi-terms/
Europeana: https://github.com/europeana/corelib/blob/master/corelib-edm-definitions/src/main/resources/eu/rdf/edm.owl
Hydra Rights: https://github.com/projecthydra/hydra-head/wiki/Embargos-and-Leases
MARC Relators: http://id.loc.gov/vocabulary/relators.html
PREMIS: http://id.loc.gov/ontologies/premis.html

Agenda

Which predicates to use?
1. Rights
  1. dc:rights
  2. dcterms:rights
  3. edm:rights
2. Rights Holder
  1. dcterms:rightsHolder
  2. marcrel:cpc (copyright claimant)
3. Copyright
  1. premis:hasCopyrightStatus
  2. premis:hasCopyrightJurisdiction
4. Rights Override
  1. dcterms:accessRights
  2. cc:license
  3. archiveshub:accessRestrictions
  4. archiveshub:useRestrictions
  5. hydrarights:embargoReleaseDate
  6. hydrarights:leaseExpirationDate

Notes

Rights
1. Different practices between OregonDigital and Europeana
  1. dcterms:rights pointing to URI, with other properties for embargo, or other complicating factors
  2. edm:rights pointing to a URI, which is an object containing other statements if needed
  3. mods:rights with text rights description, mapping to Fedora 4 will map to dcterms:rights
  4. Recommend: use dcterms:rights with URIs
Rights Holder
1. Oregon has used copyright claimant to record historical rights holder as descriptive metadata, not as rights metadata
2. Recommend: use dcterms:rightsHolder with URI, use marcrel:cpc to record historical rights holders if desired
  1. Put contact information in use restrictions
Rights Override
1. At UCSD, moving towards one predicate (dcterms:accessRights or archiveshub:accessRestrictions) for extraordinary/temporary rights, with a single expiration date
2. Hydra ACL implementation has two predicates (embargo and lease) and expiration dates for both
3. Europeana is more like Hydra, but it feels somewhat overcomplicated
4. Question: Is there a case where we need both a lease and an embargo, or can we simplify to a single accessRights property?
5. Question: What should we do with use/access restriction notes?
License
1. This duplicates dcterms:rights. In theory there could be more there, or more use but it seems like a thing to remove.
2. Recommend: Remove
Copyright
1. At UCSD, we like having this, but it does duplicate rightsstatements.org statements somewhat.
2. Can be added to the CC or rightsstatements.org licenses, so somewhat redundant.
3. Question: Should this be recommended?

Browser not supported