Actions
SKBP Needs¶
SKBP gets the available data through an API access in XML format. Then it does a mapping of the 'source' fields to their internally defined fields. This is done through a software called Aspire.
The output is then handed over to solr search engine.
The core fields they try to map are the follwings:
- content.title
- title
- content.main
- authors
- accesslevel
- abstract
- content.address
- url
- internal.technical
- source
- metadata.technical
- datasourcetechnicalformat
- medtata.topic
- unccdkeywords
- landmanagement
- metadata.date
- dataepublishedonline
- datepublished
- metadata.geolocation
- countries
- geographicalregions
- unccdregionalclassification
- climatezones
- metadata.language
- langname
- languages
- Open questions:
- Are the 'internal' source attributes renamed or mapped by Aspire?
- Can or will some of those attributes (e.g. source, keywords, unccdregionalclassification) be autogenerated by the SKBP application (aspire)?
Updated by Kurt Gerber over 8 years ago · 3 revisions