Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine weco:patron_role to DLCS role mapping #5496

Open
donaldgray opened this issue Apr 21, 2022 · 2 comments
Open

Determine weco:patron_role to DLCS role mapping #5496

donaldgray opened this issue Apr 21, 2022 · 2 comments

Comments

@donaldgray
Copy link
Member

donaldgray commented Apr 21, 2022

dlcs/protagonist#278 provided a sample app for mapping patron roles to DLCS roles.

We need to determine:

  • What roles we require in DLCS (currently restrictedFiles, clinicalImages and clickthrough).
  • How the weco patrol roles are mapped to these (from Reader, Staff, SelfRegistered and Excluded), and whether these are granular enough.

The mappings configured in the demo app are visible here : https://auth-test.wellcomecollection.digirati.io/mappings

@donaldgray donaldgray changed the title Determine weco:patrol_role to DLCS role mapping Determine weco:patron_role to DLCS role mapping Apr 25, 2022
@tomcrane
Copy link
Contributor

See discussion in Slack
https://digirati.slack.com/archives/CBT40CMKQ/p1664283005119249

In the experiemental Archivematica METS some assets have "Restricted" and in order to process them I have added this as a known AccessCondition. This should be removed once the final form of METS is in use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants