But why should we also considered the primary purpose of ?Because you need authority control to accomplish this goal with the degree of accuracy we want. We can also say that the purpose of authority control is in establishing un-ambiguous relationships between entities–or in practice, it’s really more clear to say between our records for given entities.
Though the Web in general or any particular structured database would greatly benefit from increased authority control, it should be noted that our following considerations only refer to authority control with regard to databases of "memory institutions" (i.e., libraries, archives, and museums).
Moreover, when talking about authority records, we exclusively refer to personal name authority records that describe a specific person.
The ORCID integration adds ORCID compatibility to the existing solutions for Authority control in DSpace.
String names of authors are still being stored in DSpace metadata.
The workflow described below is intended for Yale University Library catalog librarians.
It is not intended for other cataloging staff responsible for copy cataloging or for acquisitions staff involved in FASTCAT processing.
As DSpace aims to provide turnkey Institutional Repository functionality, the platform is expected to provide more functionality out of the box.
Only an elite selection of members in the DSpace community has software development resources readily available to implement this kind of functionality.
However, catalogers may use judgment in this area (e.g.
if it is important to get an authority record into Orbis right away).
The vision behind this project consists of the following two aspects: ORCID’s API has enabled developers across the globe to build points of integration between ORCID and third party applications.