-
Notifications
You must be signed in to change notification settings - Fork 0
Use Cases
Rocky Mountain Names use cases, derived from the User Personas.
Named Entity: An entity represented by data in the Rocky Mountain Names project. An entity may have more than one name. An entity may be sub-classed as a Person, Corporate Entity, or Family, in line with the International Standard Archival Authority Record guidelines. Named Entities are represented in Rocky Mountain Names by Uniform Resource Identifiers (URIs).
Named Entity Data: The data representing a named entity.
Submit data directly to the Rocky Mountain Names data store. This may be a new named entity, or an addition or revision of data properties and values for an existing named entity. There is no expectation that these contributions will be reviewed by a Site Data Contributor or System Administrator.
User Personas to whom this Use Case is relevant:
Submit data to the Rocky Mountain Names data store for review by a Site Data Contributor or System Administrator. This may be a new named entity, or an addition or revision of data properties and values for an existing named entity. There is an expectation that these contributions will be reviewed by a Site Data Contributor or System Administrator; this review process is a separate use case.
User Personas to whom this Use Case is relevant:
Create a new Named Entity in the data store directly (i.e. not as the end result of a data contribution workflow, with or without a review process). This may be done by a System Administrator, or by a Site Data Contributor in cases where the function of an organization changes sufficiently that it requires a new entity to represent it (rather than a new name form for an existing entity), but information from its previous functional representation is to be retained in the new entity record.
User Personas to whom this Use Case is relevant:
Remove a Named Entity entirely from the data store. This should be done rarely -- in most cases a deprecated Named Entity should instead re-direct to an updated Named Entity record -- but may be necessary in some data contribution workflows where errors are not detected in the review process. It should be an administrative function only.
User Personas to whom this Use Case is relevant:
Retrieve information about a single Named Entity, for use in collection management systems or local history applications. The data may be serialized in a number of formats, including JSON (whether linked data or not), RDF, or XML (using archival standards such as EAC-CPF, or library standards such as MADS or MARC).
Examples of downloads of named entity data may be found on any Library of Congress Name Authority File record in the "Alternate Formats" section. See here for an example.
User Personas to whom this use case is relevant:
Retrieve information about an arbitrary set of Named Entities, for use in collection management systems or local history applications. The data may be serialized in a number of formats, including JSON (whether linked data or not), RDF, or XML (using archival standards such as EAC-CPF, or library standards such as MADS or MARC). It is assumed at this stage of development that the "arbitrary set" is the entire data store, as in the dump of the Library of Congress Name Authority File made available by the Library of Congress (link).
User Personas to whom this use case is relevant:
Merge the data for one Named Entity into another Named Entity, including links it has to other Named Entities. The name form(s) for the merged Named Entity may or may not be retained by the Named Entity into which its data is merged. This may be done directly or as the end result of a review process.
This may be considered a sub-class of the "Update Named Entity" use case.
User Personas to whom this use case is relevant:
Review data contributions to Rocky Mountain Names; approve, revise, or reject contributions.
A prerequisite to this use case is a model of governance for the Rocky Mountain Names project, and specifically for contributions made thereto.
User Personas to whom this use case is relevant:
Search the Rocky Mountain Names data store. Searches may be by keyword or according to specific data properties, such as name, biographical/historical note, or geographic location.
User Personas to whom this use case is relevant:
Add data properties and values to the Rocky Mountain Names representation of a Named Entity, or revise existing properties and values for a Named Entity. This may be done directly or as the end result of a review process.
User Personas to whom this use case is relevant:
View a Named Entity and the data describing it. This is primarily done via a Web browser; viewing in alternate formats, such as JSON or XML serializations, is covered by the "Download Named Entity" use case.
User Personas to whom this use case is relevant:
Use cases defined at initial project stakeholders meeting w/ Douglas County Libraries, Boulder Public Library
- Search CoLA for names of people or organizations
- Retrieve an HTML or RDF representation of a person or organization
- Contribute one or more complete CoLA name records
- Contribute one or more RDF statements about an existing CoLA name
- Link to a CoLA name record in an external application (ArchivesSpace, etc.)
- Fetch data for a CoLA name record based on its URI