Difference between revisions of "Demo Starter Kit"
m |
|||
| Line 20: | Line 20: | ||
*** resource constraints default to values applicable to open data | *** resource constraints default to values applicable to open data | ||
*** many fields default to values computed at data upload-time (e.g., the bounding box) | *** many fields default to values computed at data upload-time (e.g., the bounding box) | ||
| + | ** upon POSTing of data: | ||
| + | *** the XML file is generated for insertion in the appropriate catalog service | ||
| + | *** semantic information is stored for later use by the central repository (e.g., the URIs of people, institutions, codes) | ||
Revision as of 12:25, 29 July 2014
Link allo SK di ISMAR (per avere anche la parte SOS).
Changes w.r.t. the available GeoNode software:
- added menus for sensors and services (why are services not exposed in the GeoNode demo?)
- changed ordering and naming of menus
- integrated the SOS Client
- integrated the Edi metadata editing software
- Edi = Italian counterpart to "The Helper", Gyro's (Archimede) first invention in Disney's comics
- of the 43 fields required by the Italian profile for INSPIRE metadata (34 mandatory, some require multiple values to be provided)
- 11 are automatically assigned
- 4 are computed at data upload-time
- 8 are defaulted to (meaningful) values
- 10 are supported by codelists/controlled vocabularies/generic RDF data structures
- only 10 need to be provided from scratch (6 mandatory)
- features:
- SKOS codelists translated into the language chosen for metadata (e.g. switch from Italian to English or vice-versa)
- lookup in FOAF description of people and institutions, also good for later use for access control/governance, (e.g., select an email among the IREA personnell)
- widgets for prividing dates
- autocompletion for SKOS thesauri too large for rendering as a dropdown list (e.g., start filling in "observation parameter" with "conc")
- resource constraints default to values applicable to open data
- many fields default to values computed at data upload-time (e.g., the bounding box)
- upon POSTing of data:
- the XML file is generated for insertion in the appropriate catalog service
- semantic information is stored for later use by the central repository (e.g., the URIs of people, institutions, codes)