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

dcterms:accessRights not assigned #272

Closed
1 task
danydvd opened this issue Mar 14, 2018 · 1 comment
Closed
1 task

dcterms:accessRights not assigned #272

danydvd opened this issue Mar 14, 2018 · 1 comment
Assignees

Comments

@danydvd
Copy link
Contributor

danydvd commented Mar 14, 2018

In the migration script, dcterms:accessRights is assigned based on value of "http://www.w3.org/ns/auth/acl#agent" in the permission object that has "http://www.w3.org/ns/auth/acl#mode" : "http://www.w3.org/ns/auth/acl#Read".

there are many object (private items in ERA) that only has a permission object with #mode:Write. Therefore, this items would not get a dcterms:accessRights triple.

Possible solution:

  • modify the migration script to use the permission object with #mode:Read when there is no permission object with #mode:Write. The #agent for #mode:Write is often a person's ualberta email address which will set the visibility to ual:draft.
@danydvd danydvd self-assigned this Mar 14, 2018
danydvd added a commit that referenced this issue Mar 14, 2018
@danydvd
Copy link
Contributor Author

danydvd commented Mar 15, 2018

Work is completed. However, the 27 items without a permission object still don't have a dcterms:accessRights triple. See #264

@danydvd danydvd closed this as completed Mar 15, 2018
metadata-bot pushed a commit that referenced this issue Jun 22, 2018
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

1 participant