NicNames as a webservice

The current perspective is of NicNames as a webservice and as such supplying an API set allowing for submission of names and the extraction of names and associated metadata. The standard set of DB maintenance methods (Add, Edit, Reports etc) is supplied together with extensions that enable the tie of the service to a web application (e.g. Valet) supplying resolution of names and metadata usable to populate application fields. As such there are two forms of access, via direct access to NicNames or via calls to NicNames through such as Valet or repository management applications (E.g. VITAL) - the latter requiring customisation to integrate NicNames with the application.

Since the Valet environment covers self-submission of data to the repository there are (a) some restrictions on access to NicName methods and (b) requirements for repository staff to later validate name entries when input from a Valet environment (The X-Files element - trust no one!). The security also covers harvesting attempts where NicNames data can be extracted (OAI-PMH format) covering the name(s) and a defined set/subset of existing data - the definition as set down by the associated repository manager(s) and so limiting access to such as staff IDs etc that could be exploited as part of identity theft etc. but are essential for disambiguation methods.

As a webservice NicNames is dominantly passive; population of the DB with existing names from the repository done in the form of repository staff extracting data into an XML file and submission of that file to NicNames. Once data has been added, any additional data defined when setting up the NicNames schema is required to be added to the system. The amount of data is determined by the repository manager or else one can accept the default schema that is comprehensive in its coverage of data usable to aid in the disambiguation process.

The simplicity of the approach i.e. a webservice that enables the 'transcending' of current authority control data (as MARC format etc), hides the complexity in use of that data to disambiguate names where the essential feature of NicNames is in the speed and precision achieved in the disambiguation focus. The additional benefits include access to additional metadata beyond their use in resolving ambiguities.