ArcServer generated Dublin Core records may require vendor specific paths

Ecotrust / wc-data-registry

Data Registry for the West Coast Governors Alliance

Other

10 stars 8 forks source link

ArcServer generated Dublin Core records may require vendor specific paths #100

Open tchaddad opened 10 years ago

tchaddad commented 10 years ago

Related to records coming from some California agency contributors that provide auto-generated metadata directly from ArcServer to the California Geoportal.

The default Dublin Core records from ArcServer contain vendor-specific identifiers, and seem to be incomplete (e.g. missing Publisher and Date fields).

tchaddad commented 10 years ago

First cut on the ArcServer Dublin core paths for metadata.js:

DATE PUBLISHED

Not available

CREATOR

rdf\\:RDF > rdf\\:Description > dc\\:creator

PUBLISHER

Not available

CONTACT

Not available

CONSTRAINTS

rdf\\:RDF > rdf\\:Description > dct\\:abstract > rdf\\:value[rdf\\:resource='mxd.subject']

tchaddad commented 10 years ago

Have added the following to Dev Server (these are now working)

CREATOR

rdf\\:RDF > rdf\\:Description > dc\\:creator

CONSTRAINTS

rdf\\:RDF > rdf\\:Description > dct\\:abstract > rdf\\:value[rdf\\:resource='mxd.subject']

emiliom commented 10 years ago

I can't remember if Tanya sent sample record info to evaluate these. So I haven't evaluated these, but I'll guess they're good to go :) Still, I won't close the issue.