SKBP Needs » History » Revision 2
Revision 1 (Kurt Gerber, 23 May 2016 10:19) → Revision 2/3 (Kurt Gerber, 23 May 2016 10:39)
h1. 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 ** climateones * *metadata.language* ** langname ** languages * Open questions: In tha attached documen * Can or will some of those attributes be autgenerated by the SKBP application (aspire)? * Is