Update (and future plans) on CADIS
40 likes | 204 Vues
Update (and future plans) on CADIS. the next generation portal, a gateway now, is under development it should be in beta by October should go live in December, replacing the present portal the gateway will have enhanced search capabilities
Update (and future plans) on CADIS
E N D
Presentation Transcript
Update (and future plans) on CADIS • the next generation portal, a gateway now, is under development • it should be in beta by October • should go live in December, replacing the present portal • the gateway will have enhanced search capabilities • no longer will rely on a hierarchical structure for finding data • metadata will reside in two databases • THREDDS catalogs will be generated as needed from the PostgreSQL database, similar to the way EOL has been doing it for the CDP • searches will use the RDF (Resource Description Framework)Triple Store database • queries short statements in the form of subject-predicate-object • for both text and geospatial searches
Update (and future plans) on CADIS • the present CADIS metadata profile will continue to define data sets • metadata can come into the databases and gateway through several routes • metadata input form • same as present portal • changes to it may be made after gateway has been live for a while • DIF or other XML file uploaded to gateway • OAI-PMH harvesting of other data repositories • THREDDS catalogs • ARMAP and ARLISS (various web services)
Update (and future plans) on CADIS • the ingest of existing THREDDS catalogs will be used to initially populate the gateway • a one-time operation • need to make sure all metadata is represented in the present THREDDS catalogs before ingest • no file level metadata have been defined for CADIS, yet, nor collected • need to extend the metadata input interface to include file level metadata for search, visualization and other planned services • need site information in the database for mapping and searching • lat/lon information for sites has been entered into the mapserver, and shared with the gateway team