Service for Control of Named Entities
The purpose of this service is to provide methods to deal with controlled lists of named entities to assure data quality and facilitate data access and data entry. Read more on the background here.
Introduction[edit]
The Control of named entities (Cone) service at present supports the named entity types listed below. It is integrated with PubMan in the publication metadata editing forms via "auto suggest" component for respective metadata edit fields (journal name, language of the publication).
Operations[edit]
The CoNE service supports the following operations:
- searching (based on the metadata of named entity i.e. in case of journals: journal name, publisher name, place of publication
- retrieving details of selected named entity e.g. retrieving the metadata of a selected journal based on the journal identifier
Operation | Status | Input | Output | Description |
---|---|---|---|---|
query | implemented | q:String (opt)lang: String |
String | Scope:Public Gives back a list of resources/ids in the given language (default 'en') matching the given query. The number of maximum hits given back is configurable (default 50). |
details | implemented | id: String (opt)lang: String |
String | Scope:Public Returns all available information on the resource in the given language (default 'en') identified by the given id. |
all | implemented | (opt)lang: String | String | Scope:Public Gives back a list of all resources/ids in the given language (default 'en'). |
Interfaces[edit]
The CoNE service comes with a flexible interface definition that defines the Input/Output formats. The following formats are available
Interface | Status | Input | Output | Description |
---|---|---|---|---|
jquery | implemented | HTTP Get-Request | jquery proprietary list, JSON | HTTPServlet used by jquery Javascript components for autosuggest features |
options | implemented | HTTP Get-Request | Format that can easily be read by Java to generate JSF options | HTTPServlet usable by Java a.o. |
json | implemented | HTTP Get-Request | pure JSON | HTTPServlet usable by Javascript/AJAX components |
html | implemented | HTTP Get-Request | (X)HTML | HTTPServlet that provides a human readable overview on the data (planned to be used for author pages) |
rdf | implemented | HTTP Get-Request | RDF/XML | HTTPServlet that provides a RDF view on the data |
unapi | planned | HTTP Get-Request | varying | HTTPServlet that conforms to the unAPI interface specification |
vcard | planned | HTTP Get-Request | ASCII(UTF-8 for single values possible using BASE64 encoding?) | HTTPServlet that conforms to the vCard specification (RFC2425) |
Supported Named Entity Types[edit]
Currently, we support following vocabularies:
Journals[edit]
Details to be provided:
- url to the journal service interface
- metadata description for CoNE Journal
- example urls to the service
- url to the test-jsp
Languages[edit]
Details to be provided:
- url to the language service interface
- metadata description
- example urls to the service
Persons[edit]
see Profile under CoNE_Person
DDC[edit]
Details to be provided: Dewey Decimal Classification
Mimetypes[edit]
A list of the IANA mimetype list plus additional mimetypes needed for PubMan (currently used for validation).
eSciDoc mimetypes[edit]
A subset of the mimetypes list above. Planned to be used for PubMan in the future.
Candidates for Named Entity Types[edit]
Potential further candidates for normalized metadata entries:
MPG Units[edit]
Potential metadata elements[edit]
Complete name In Englisch and/or German?
Alternative name
Place
Address
Homepage
Resources[edit]
- http://www.mpg.de/english/institutesProjectsFacilities/index.html - MPG website, the authorative source?
- http://wiki.mpg.de/index.php/Alumni:ListeInstitute - list of MPG units (existing and former) provided by maxnet wiki
- http://www.biochem.mpg.de/iv/strategy_tab.html#mpg - Search queries for MPG units provided by IVS-BM
- http://de.wikipedia.org/wiki/Max-Planck-Gesellschaft#Forschungseinrichtungen_der_Max-Planck-Gesellschaft
Conferences/events[edit]
Potential metadata elements[edit]
Title The name of the event (e.g. Symposium on Theory of Computing)
Alternative title Any alternative name of the event
Abbreviation Abbreviated name of the event (e.g. STOC)
Start date Start date of the event
End date End date of the event
Place Place where the event took place
Invitation status The information if the creator was explicitly invited
- Remark Sabine: Should this information be stored in controlled metadata record?
- Remark Ulla: No, not to my understanding
- To my understanding, the invitation status can only be specified for each talk individually and is therefore no generic metadata for the conference --Inga 12:19, 28 December 2007 (CET)