Managing CoNE entities - Persons
This is a protected page.
prelim scenarios and use cases for specification of Service for control of named entities, for dealing with persons in the context of PubMan solution. Both scenarios and service will be extended in future.
Data pools[edit]
Based on requirements from 2 Early Adopters, we will extend the Control of named entities for persons. We will maintain 2 pools of person data:
Un-authorized person data[edit]
- i.e. names, name variants and respective affiliations
- the data pool will be created by using current name variants on pubman plus any new entry on pubman during submission and import.
- The user will be supported by an autosuggest list containing all currently available un-auhtorized data, to reduce duplicate entries
- The person information stored with a publication item will not be altered, i.e. the person information stored with a publication item is un-authorized data, but can be related afterwards to a PersonID stored in CONE (see authorized person data)
- Therefore, the publication item will be linked to only one naming variant, which is the one provided during submission/import.
- The entries in the un-authorized pool of data will have internal ID, to be linked to CONE IDs.
- GUI: should consider support for user in identifying from auto-suggest, which of the entries is "authorized"/"un-authorized" (see example WorldCat)
Authorized person data[edit]
- will be controlled by the CONE service
- contains main name entry, controlled alternative name variants, controlled affiliation (see final data structure, based on NIMS and ICE requirements)
- Only selected users can access the CONE service to edit and maintain the controlled person IDs
- Selected users can relate un-auhtorized person name IDs to permanent, controlled, authorized person IDs in CONE.
Scenarios[edit]
- Integration on submission mask
- Integration during search