You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?The text was updated successfully, but these errors were encountered: