SKBP Needs » History » Version 1
Kurt Gerber, 23 May 2016 10:19
1 | 1 | Kurt Gerber | h1. SKBP Needs |
---|---|---|---|
2 | |||
3 | |||
4 | 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. |
||
5 | The output is then handed over to solr search engine. |
||
6 | |||
7 | *The core fields they try to map are the follwings:* |
||
8 | |||
9 | * *content.title* |
||
10 | ** title |
||
11 | * *content.main* |
||
12 | ** authors |
||
13 | ** accesslevel |
||
14 | ** abstract |
||
15 | * *content.address* |
||
16 | ** url |
||
17 | * *internal.technical* |
||
18 | ** source |
||
19 | * *metadata.technical* |
||
20 | ** datasourcetechnicalformat |
||
21 | * *medtata.topic* |
||
22 | ** unccdkeywords |
||
23 | ** landmanagement |
||
24 | * *metadata.date* |
||
25 | ** dataepublishedonline |
||
26 | ** datepublished |
||
27 | * *metadata.geolocation* |
||
28 | ** countries |
||
29 | ** geographicalregions |
||
30 | ** unccdregionalclassification |
||
31 | ** climateones |
||
32 | * *metadata.language* |
||
33 | ** langname |
||
34 | ** languages |
||
35 | |||
36 | |||
37 | |||
38 | In tha attached documen |