Difference between revisions of "Talk:Service for Control of Named Entities"

From MPDLMediaWiki
Jump to: navigation, search
(trac URL changed)
 
Line 311: Line 311:
 
*Automatic “Umverknüpfungsprozess” has to be specified. Privileges and rights of IR items have to be considered (i.e. how to handle the re-direction of items from other collections).
 
*Automatic “Umverknüpfungsprozess” has to be specified. Privileges and rights of IR items have to be considered (i.e. how to handle the re-direction of items from other collections).
 
==Related Information==
 
==Related Information==
[https://dev.livingreviews.org/projects/vlib/wiki/AuthFiles Misc on Authority Files by Inga]
+
[https://devtools.mpdl.mpg.de/projects/vlib/wiki/AuthFiles Misc on Authority Files by Inga]

Latest revision as of 12:41, 14 August 2012

Preliminary functional specification for handling named entities.

To be used for functional specification for handling different types of entities, such as Persons or Journals

Potential use cases

(First ideas, needs to be discussed)

This section contains a first draft of potential use cases, described in a generic way that have to be adapted according to the respective type of authority file (e.g. journal, person, etc.):

  • Create an authority record
  • Use an authority record as template
  • Display an authority record
  • Edit an authority record
  • Delete an authority record
  • Link an authority record to an IR item
  • Redirect an authority record
  • Search an authority record

Whether the described use cases can also be applied for affiliations has to be evaluated further. The description of potential use cases is based on the assumption that the system supports the incremental build-up of internal authority files and external sources are used and integrated as a start content.

Please note: in the usage scenarios/use cases the deletion of a record should be stated as exception. Instead the deactivation of a record happens more often.

Create an authority record

Preconditions, assumptions

  • IR item is self-contained
  • Authority record is immediately visible and selectable (no status: pending, submitted, etc.)
  • Depositor is not allowed to create, edit, delete or redirect an authority record
  • Potential new role “AF-Editor” is not considered
  • An authority record has no obligatory descriptive elements (=> no validation process is required)
  • UCUse Case can be triggered independently or during FQA process as an extension of UCUse Case_PM_QAQuality Assurance_XXX in case IR item has not been assigned to an authority record during submission process or has been assigned to the wrong authority record and the appropriate record is not yet available
  • Nice to have: system provides interface to external authority files for inquiries and data transfer (not considered)

Actors

  • Moderator, MDMetadata-Editor

Basic course of events (creation during FQA process)

  • The user chooses to create an authority record
  • The system creates a new authority record for the respective metadata field
  • Continue with UCUse Case edit an authority record
  • The system links the selected IR item with the authority record (via IDIdentifier)

Alternative a (in case use case is triggered independently)

  • The user chooses to create an authority record
  • The system displays a list of all authority files for which the user has privileges
  • The user selects an authority file and confirms the choice
  • The system creates a new authority record
  • Continue with UCUse Case edit an authority record

Alternative b (in case use case is triggered independently)

  • If the user has rights for only one authority file, the authority file selection is automatically performed by the system

Use an authority record as template

Preconditions, assumptions

  • IR item is self-contained
  • Potential new role of “AF-Editor” is not considered
  • UCUse Case can be triggered during FQA process or independently
  • One authority record is selected

Actors

  • Moderator, MDMetadata-Editor

Basic course of events

  • The user chooses to use the selected authority record as template
  • The system creates a new authority record and populates the new record with the metadata of the selected record
  • Continue with UCUse Case edit authority record

Display an authority record

Preconditions, assumptions

  • IR item is self-contained
  • Potential new role of “AF-Editor” is not considered
  • UCUse Case can be triggered during Submission, FQA process or independently
  • One authority record is selected

Actors

  • Moderator, MDMetadata-Editor, (Depositor) (authority record view for Depositor must not contain personal data, e.g. date of birth etc.)

Basic course of events

  • User chooses to display the selected authority record
  • The system displays the authority record

Edit an authority record

Preconditions, assumptions

  • IR item is self-contained
  • Depositor is not allowed to create, edit, delete or redirect an authority record
  • Potential new role “AF-Editor” is not considered
  • Check of correct assignment of authority record is performed during FQA process and no separate authority record quality assurance process is implemented => UCUse Case can be triggered during FQA process or independently
  • UCUse Case is included by UCUse Case create an authority record and by UCUse Case use an authority record as template
  • The user wants to change or provide data for an authority record

Actors

  • Moderator, MDMetadata-Editor

Basic course of events

  • The user chooses to edit the selected authority record
  • The system displays an edit view for the selected authority record
  • (Optional) the user adds new metadata values or modifies existing metadata values
  • The user chooses to finalize the data
  • The system stores the authority record and displays a success message

Delete an authority record

Preconditions, assumptions

  • IR item is self-contained
  • Deletion of authority records is important in case duplicates have been generated
  • Always the newer authority record should be deleted (=> date of creation is an important information and should be displayed somewhere in the authority record view)
  • Only authority records with no IR items assigned can be deleted. In case to be deleted authority record is still linked to IR items, links have to be changed manually beforehand (cf. UCUse Case redirect an authority record). Maybe an automatic “Umverknüpfungsprozess” should be implemented at a later date.
  • Depositor is not allowed to create, edit, delete or redirect an authority record
  • Potential new role “AF-Editor” is not considered
  • One authority record is selected

Actors

  • Moderator

Basic course of events

  • The user chooses to delete the selected authority record
  • The sytem checks if not IR items are linked with the selected authority record
  • No IR items are linked with the authority record
  • The system prompts the user to confirm the deletion
  • The user confirms to delete the authority record
  • The system deletes the authority record and displays a success message

Alternative a

  • The selected authority record is still linked to one or more IR items
  • The deletion fails

Alternative b

  • The user does not confirm to delete the authority record
  • The selected authority record is unaffected

Link an authority record

Preconditions, assumptions

  • IR item is self-contained
  • After selecting an authority record (and establishing a link between authority record and IR item) the user is still allowed to edit the medatata field but the established link will not remain. Incorrect links should be discovered and corrected during FQA process
  • Potential new role “AF-Editor” is not considered
  • Use case is part of USC submission or USC FQA an should be integrated as an include association in UCUse Case_PM_SM_XXX

Actors

  • Depositor, Moderator, MDMetadata-Editor

Basic course of events

  • User fills in the corresponding metadata field. During his/her typing the system automatically suggests a list of potential authority records (Wörterbuchfunktion)
  • The user selects an authority record
  • The system links the item with the selected authority record via AR-IDIdentifier. In case a link has already been established, the system overwrites the previous AR-IDIdentifier (relevant in case UCUse Case is triggered during FQA process)
  • (Optional) the user edits the corresponding metadata field. The link between the item and the authority record does not remain and the item is marked as <not assigned to authority record>

Alternative

  • No appropriate authority record is available. The user enters a free-text
  • The item is marked as <not assigned to authority record>

Redirect an authority record

Preconditions, assumption

  • IR item is self-contained
  • Depositor is not allowed to create, edit, delete or redirect an authority record
  • Potential new role “AF-Editor” is not considered
  • UCUse Case is triggered in case duplicate has been detected or in case IR item has been assigned to the wrong authority record

Actors

  • Moderator, System

Basic course of events

  • Moderator triggers automatic Umverknüpfungsprozess

Search an authority record

Preconditions, assumptions

  • IR item is self-contained
  • Potential new role “AF-Editor” is not considered
  • UCUse Case can be triggered during FQA process or independently

Actors

  • Moderator, MDMetadata-Editor

Basic course of events

  • The user selects one or more authority files
  • The system displays a simple search field
  • The user enters a search string and chooses to start the search
  • The system searches in all metadata fields of authority records
  • The system displays the list of items of the search result

Alternative

  • No item matched the search string
  • The system displays a message

Potential new role: AF-Editor

(First idea, needs to be discussed)

It has to be discussed further if a new role called AF-Editor has to be established. The idea is that the AF-Editor is responsible to provide and maintain high data quality of authority records and to ensure the consistency of the authority file databases. He/she is familiar with relevant cataloging and standardization rules and takes care of the standardization of selected data. The AF-Editor complements the area of responsibilities of the Moderator and the MDMetadata-Editor and has special privileges to authorize and to deactivate authority records. Once an authority record has been authorized it is locked and can only be edited by the AF-Editor him-/herself.

Potential new use cases

  • authorize an authority record
  • send an authority record back for revision (in case e.g. Moderator wants to edit an authority record which has been already authorized)
  • propose an authority record for deactivation

Potential new status

  • After creation authority record is either in state pending or submitted.

Potential privileges/competencies

  • AF-Editor is allowed to authorize and to deactivate authority records and beyond that has privileges to all other actions connected to authority files/authority records.
  • During separate AFQA process authority record gets checked and authoritzed by the AF-Editor. A list of newly created authority records is displayed in the AF-Editors’ workspace.

Open issues

  • Separate AFQA process and its interaction with FQA process has to be specified. We assume that the release process of IR items is not affected by new AF workflow when IR items are self-contained and follow Autopsie-Prinzip.

Potential privileges/competencies

(First idea, needs to be discussed)

Depositor

  • display an authority record
  • link an authority record

Moderator

  • create an authority record
  • display an authority record
  • edit an authority record
  • deactivate an authority record
  • link an authority record to an IR item
  • redirect an authority record
  • search an authority record

MDMetadata-Editor

  • create an authority record
  • display an authority record
  • edit an authority record
  • link an authority record to an IR item
  • search an authority record


Open Issues

Metadata

  • Agree on a list of potential candidates for authority files. Note: If a generic mechanism like CDS Invenio's knowledge base would be implemented no such list would be needed in advance.
  • Define what kind of descriptive elements an authority record should contain. Descriptive elements may differ from authority file to authority file and should therefore be defined individually.
  • Decide whether an IR-item should be self-contained or not. Question: What does self-contained mean? Even right now, IR items are not self-contained in the sense that they contain all relevant metadata values, because other repository objects like creators are only referenced.
  • Define how to map authority files to a MDMetadata element in a specific MDS. Note: for every MDMetadata element the system supports authority files for, we probably need to specify a list of descriptive information available for the authority file (e.g. journal names: title, translation of title, title abbreviations, ISSNInternational Standard Serial Number, eISSN, etc. persons: last name, first name, etc.)
  • Specify linking between IR items and authority records via IDIdentifier.
  • Specify linking of different authority files/databases (e.g. user database - personal name authority file - affiliation authority file).
  • Describe selection of authority record (Depositor during submission? Free-text field? System suggests authority record while Depositor fills in information? Depositor may search within authority file database and selects an record?).

Handling of authority files

  • Specify assignment of items to an authority record and when it will take place (while submission by selecting an authority record from the selection list? While submission by accepting an authority record selected by the system? While FQA?).
  • Describe administration and control of authority files (who is allowed to create, edit, delete, redirect, and authorize authority records? (see proposal of new role AF-Editor).
  • Define what will happen in case no appropriate authority record is available.
  • Specify if different kinds of authority files require different handling.
  • Clarify dilemma between authority files and Autopsie-Prinzip (scenario: user selects an authority record. System fills in certain fields automatically. User edits one or more of the automatically selected fields afterwards) (proposal made by Inga: entry in IR item follows Autopsie-Prinzip but browse tree will be generated from authority record and standardized data. Notation of original (Vorlage) should be integrated in authority record as an alternative (e.g. alternative name).
  • Specify duplicate checking for authority records. Duplicate checking should also compare e.g. name and alternative name.
  • Specify users and their rights and privileges concerning authority files.
  • Specify if a separate authority file workflow is required.
  • Describe entry of multiple authors (via copy and paste).

Handling of new authority records

  • Describe creation of new authority records (e.g. when does user create a new record? (Depositor during submission? Moderator during FQA? AF-Editor in a separate workflow? Is it possible to use an existing entry as template? Should the system generate a message to AF-Editor in case a new authority record has been created?).
  • Specify a “Regelwerk” for the creation of new authority records.
  • Specify if an authority record has obligatory elements.

Import of external authority files

  • Specify how external authority files can be provided (licensed by MPSMax Planck Society? Online available? CD-ROM?) and which procedures are required (includes: harvesting, data conversion (format and character set), linking to IR items, update mechanism, maintenance).
  • Describe import of external authority files or subset of it.
  • Where will be imports of data sets like: name authority files (e.g. PNDPersonen Normdatei), user/person related information; imports from MPG-IPInternet Protocol-database hosted at GWDGGesellschaft für Wissenschaftliche Datenverarbeitung Göttingen, other authority files (e.g. Zeitschriftendatenbank) described and handled? – They are not described in USC_ingestion.

Build-up of internal authority files

  • Describe procedure of how to create incrementally built authority files.
  • Clarify integration/interaction of internal and external authority files (initial import of external authority files or harvest of authority files scheduled on a regular basis?).
  • Will it be possible to extend/modify authority records in case of loading/synchronizing authority files from external source (assumption: no or by customizable fields).

Customization

  • Clarify on which criteria authority files are chosen (customization of authority files on collection, user, user group level?).
  • Describe setup of authority files on collection level.

Export

  • Specify export of authority records/authority files
  • Define what kind of descriptive elements of an authority record should be exportable in case IR item is not self-contained or in case IR item should be enriched with additional information from authority record.

Ingestion

  • Specify assignment of authority records for ingested data.

Searching

  • Define which elements of authority records are searchable (simple, advanced and expert search).
  • Specify searching in external authority files (provide interface for AF-Editor and Moderator to external authority files for inquiries and data transfer).
  • Define generation of browse trees (proposal: browse trees should be generated of standardized data of authority record).
  • Specify search in internal authority files.
  • Describe basket functionality for authority records (e.g. important for re-direction in batch mode or re-use of data).

Migration of eDocElectronic Documentation data

  • Specify assignment of authority records to migrated eDocElectronic Documentation items.

Others

  • Is the SFXOpenURL Link Resolver knowledge base an alternative to the ZDBZeitschriftendatenbank?
  • Favourite co-authors feature has to be implemented in accordance with authority file concept (Wörterbuchfunktion could be an alternative to the favourite coauthors feature).
  • Automatic “Umverknüpfungsprozess” has to be specified. Privileges and rights of IR items have to be considered (i.e. how to handle the re-direction of items from other collections).

Related Information

Misc on Authority Files by Inga