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.

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

URL type needed for additional metadata fields? #137

Open
nuest opened this issue Dec 10, 2015 · 1 comment
Open

URL type needed for additional metadata fields? #137

nuest opened this issue Dec 10, 2015 · 1 comment
Assignees
Labels

Comments

@nuest
Copy link

nuest commented Dec 10, 2015

The flexible /extra endpoint would be interesting to use in the following scenario: A Geonetwork catalog harvests an SOS and create ISO metadata. This ISO metadata can easily be edited in the Geonetwork editor then. The link to the full ISO metadata should also be available in an extended metadata view in the JavaScript client, which is possible using the metadata extension mechanism.

Is it necessary or useful to have a specific URL data type for the metadata table? Or is string just fine?

@ridoo
Copy link
Member

ridoo commented Apr 11, 2016

A type url could make sense to differentiate from string as there might be parameters to URL-encode. Otherwise a client will get an invalid URL. So, yes: I think to differ here is useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants