Service for Control of Named Entities

This is a protected page.

eSciDoc Solutions PubMan: Overview · Functionalities Interfaces · Support Faces: Overview · Functionalities Scope · Support ViRR: Overview · Functionalities Scope · Support imeji Digitization Lifecycle edit

The aim of this page is to collect information concerning control of named entities in the context of PubMan/eSciDoc. The page contains functional and technical specifications of envisioned PubMan services in this domain. General information concerning control of named entities and be found on the page called Control_of_Named_Entities.

Note for users maintaining this page:

Issues that are still work in progress or need to be discussed should be put on the discussion page first. As soon as something has been agreed, it will be moved to the main article page.

First services

Core service "organizational unit handler

The eSciDoc system provides a core service "organizational unit handler which manages the organizational units for the eSciDoc system. In future, this core service might be extended by an additional service for named entity control for organizational units, to be able to track and manage more information needed for organisational units.

The basic descriptive elements which will be covered by the core service are:

• Name

The name of the organization, including translations. (Translations need respective language flag)

Cataloging rules are necessary, i.e. the full network path should be visible in the name of the organizational unit.

• Alternative name

Any alternative name or abbreviation used for the organization

• City

The city where the organization is located

• Country

The country where the organization is located

• Type

Type of organization, i.e. institution, institute, department, group, research unit, project, sub-project, research school

• Time period

Indication, in which time period the organization was active.

• Relations
  • actual hierarchies and network-relations, e.g. sub-units

    Remark Traugott: hierarchical relations between org units might be keep sufficiently within the titel/name element, with the sequence from higher to lower.

  • historical dependencies, i.e. successor-predecessor

• Identifier

URI, eSciDoc Identifier for the organisation. In addition, other identifiers can be kept.

Ongoing work on the core service definition, see Discussion page on functional specification for org unit management

Future Development

Classification/Tagging

• MPS-Section(?)

Affiliation of the organisational unit to one of the three sections

Prototype service for controlled named entities - journal names

To understand better the issues of controlled named entities for a certain application, we decided to start with a prototype service for PubMan on controlled named entitites.

Stages of prototyping:

1. select an authority file (corporate bodies, journals, authors) and available external source
2. create (import) data locally into an authority file from a selected source
3. implement the referencing from the PubMan edit interface (enable automatic grow of the authority file for start when reference is not done)
4. create very simple viewer/editor for the authority file data
5. get feedback from potential pilot users
6. extend the prototype with another authority file and repeat the steps 2-5
7. modify/add functionalities based on the functional and technical feedback

Please see work in progress on Talk:Service_for_Control_of_Named_Entities

Publication Management

Enhanced Scientific Documentation

Uniform Resource Identifier

Max Planck Society