Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
tchaddad opened this issue Jan 9, 2014 · 3 comments
Open

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

tchaddad opened this issue Jan 9, 2014 · 3 comments
Labels
bug

Comments

@tchaddad
Copy link
Collaborator

tchaddad commented Jan 9, 2014

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 tchaddad mentioned this issue Jan 9, 2014
Open
@tchaddad
Copy link
Collaborator Author

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
Copy link
Collaborator Author

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
Copy link
Collaborator

emiliom commented Jan 16, 2014

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.

timglaser pushed a commit that referenced this issue Jan 16, 2014
A series of changes by Tanya, Emilio and Todd.
286f123 
As reported by Tanya, this commit fixes the following tickets:
Related #85
Related #91
Related #92
Related #100
Related #101
Related #103
Related #104
@fishytodd fishytodd mentioned this issue Jan 20, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@emiliom @tchaddad