Automated database updates in SECORE

[Dimitar Misev]

SECORE currently puts everything in one XML document, in one database:

1. the whole EPSG database in GML (logging in to ​http://www.epsg-registry.org/ allows one to export it)
2. custom definitions added via the admin interface, while browsing at ​http://localhost:8080/def/browse.jsp

These need to be separated into whatever way possible (e.g. two separate XML documents, two separate collections, databases, etc., depending on the capabilities of the XML database !BaseX), so that we have

1. a static EPSG database (db1)
2. a database of user defined definitions (db2)

db1 can only be updated via an "Update EPSG database" link in the admin interface at ​http://localhost:8080/def/index.jsp, and is otherwise read-only. Any actions via the browser interface (adding definitions, changing, deleting, …), target db2.

In summary

1. separate EPSG database from user-defined defs, so that the EPSG db can be updated separately
2. provide means to update db1 automatically, by clicking a link on the admin page

Helpful links

• SECORE source code: source:applications/secore
• SECORE docs: wiki:SecoreUserGuide, wiki:SecoreDevGuide

[Dimitar Misev]

Piero I think it will be best if we both look at what are the options here and how to implement this. We just need to study the ​BaseX documentation a bit.

[Dimitar Misev]

There's a new "Update EPSG database" link at index.jsp

[Piero Campalani]

changeset:5bf563a.

[Piero Campalani]

That fix broke the capability of SECORE to support parametrized CRS, due to a tiny XQuery syntax error.
Fixed in changeset:f2e20b5.

[Dimitar Misev]

I think might be issue of BaseX version, with the 7.2 that syntax worked well, with reverting back to 6.x maybe it got broken. In any case, thanks for the fix!