Authority control with Agent objects
Agent objects
- Used for personal / corporate name entities. Used as values for 'maker' fields.
- Can be entered as
- Full linked data URI (either VIAF or FAST).
- String
- Searches our existing Agent objects and suggests autocomplete options therefrom.
- Autocompletes show count of #times used in our repo.
- Probably don't live in Fedora, but in a separate triple store
- Set-up of triplestore (using ansible)
- Integration of triplestore with sufia app
- Backup/recovery process
- Can be entered as part of existing metadata forms (like a nested attribute)
- If the agent entered already exists in our triplestore, it can be selected via autocompleted; text entry is then disabled / greyed out on that field.
- If an agent entered does not exist in our triplestore, it is added as a local entry.
- Indexed with file objects that use them.
- 'Edit authorities' area - local entries can be created, edited, deleted by a user with permission.
- Reporting?
- Implementation should be extensible / generalizable where it makes sense, so we can apply same strategy to other objects like Places or subjects.
Relevant Work
- Trey's Hydra Connect presentation: http://www.slideshare.net/JosephSchmoseph1/linked-data-labels-uris
- Applied Linked Data group: https://wiki.duraspace.org/display/hydra/Applied+Linked+Data+Working+Group