Skip to content
This repository has been archived by the owner on May 10, 2023. It is now read-only.

Database schema version shouldn't appear in publicID #67

Open
fabienengels opened this issue Jun 10, 2016 · 2 comments
Open

Database schema version shouldn't appear in publicID #67

fabienengels opened this issue Jun 10, 2016 · 2 comments

Comments

@fabienengels
Copy link
Contributor

Hi,

We found an issue on how publicID are generated in QuakeML issued by fdsn-event. The database schema version appears in the smi, ex :
publicID="smi:scs/0.7/eost2016ljdn"

Database schema version shouldn't be used in publicID as they are not supposed to change over time.

@fabienengels
Copy link
Contributor Author

Don't know if anyone read this issue, should I send a email to the mailing list ? Thank you in advance

@gempa-stephan
Copy link
Member

The SC3 QuakeML exporter used by the fdsnws module uses the fixed prefix smi:scs/0.7/. It will not change when updating to 2016.161 respectively database version 0.8.

I guess instead of a fixed prefix you want to see DNS name of the organization here. Therefore the exporter interface needs to be changed and a configuration parameter should be added.

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

No branches or pull requests

2 participants