Are people using additional values for rightsBasis beyond
copyright, license, and statute?
We are considering two other values that we recognize are a
stretch. We would like to express two additional foundations for
not rights per se, but for restrictions placed on the content.
One basis would be "institutional policy." These are explicit, published,
citable policy documents. We would include a rightsExtension block
for the policy, including
policyIdentifier
policyIdentifierType
policyIdentifierValue
citation or title (one or two elements?)
alternateTitle
issuingAuthority (Can be an agent)
policyEffectiveDate
startDate
endDate
policyText
This would be used as the basis for expressing embargoes on
archived emails, for example.
Another value is even further afield, "curator decision." This is meant to
allow us to express that a particular restriction or set of restrictions are
enforced, in the absence of an explicit license or statute requirement,
based on a curator's judgment.
We can use these additional values locally to meet our preservation
management needs, but would rather not if they'd be a Really Bad Idea.
If so, what would be a better approach to express such information?
Thank you,
--Robin
Robin Wendler
Harvard University Library
Office for Information Systems
90 Mt. Auburn St.
Cambridge, MA 02138 USA
617-495-3724 (W)
[log in to unmask]
|