search

OregonDigital / oregondigital_2

The active development on Oregon Digital 2 is in the https://github.com/OregonDigital/OD2 repo.
Other
1 stars 1 forks source link

Rights statement should define access permissions #177

Open tpendragon opened 9 years ago

jsimic commented 9 years ago

So this will no longer be two different metadata fields?

tpendragon commented 9 years ago

The current recommendation from the Hydra rights sub-group is here: https://wiki.duraspace.org/display/hydra/Rights+Metadata+Subgroup

Effectively use EDM.rights for URIs, rightsHolder for things like RR-R, and DCE.rights for human readable rights information.

jsimic commented 9 years ago

@srabun Just reading your reply to Randy Parks...

wickr commented 9 years ago

@terrellt wouldn't RR-R also go in EDM.rights? I read it as rightsHolder would be URIs for institutions or other entities, maybe people

kestlund commented 9 years ago

@wickr is correct.

tpendragon commented 9 years ago

@wickr Yes- - I meant the rightsHolder would be used to figure out access permissions in cases where rights are restricted.

jsimic commented 8 years ago

Some collections contain licensed public domain permissions, therefore we created accessPermissions field to prevent this material from appearing to non-institutional users.

jechols commented 8 years ago

Just a quick note from a discussion today: we may need to make sure we don't give blanket rights just because somebody is a curator. e.g., being allowed to ingest an Image for OSU doesn't mean you can download restricted images from a UO collection.

This may not be important enough to spend time implementing, but it's something we want to be keeping in mind.