Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#382 closed defect (fixed)

Automated database updates in SECORE

Reported by: dmisev Owned by: pcampalani
Priority: major Milestone: 9.0
Component: secore Version: 8.4
Keywords: Cc: pbaumann, dmisev
Complexity: Hard


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

  1. the whole EPSG database in GML (logging in to 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

Change History (8)

comment:1 Changed 4 years ago by pcampalani

  • Owner changed from nkolev to pcampalani
  • Status changed from new to assigned

comment:2 Changed 4 years ago by pcampalani

  • Cc dmisev added; pcampalani.mrusu removed

comment:3 Changed 4 years ago by pcampalani

  • Cc pbaumann added; pbauman removed

comment:4 Changed 4 years ago by dmisev

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.

comment:5 Changed 4 years ago by dmisev

  • Resolution set to fixed
  • Status changed from assigned to closed

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

comment:6 Changed 4 years ago by pcampalani

comment:7 Changed 4 years ago by pcampalani

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

comment:8 Changed 4 years ago by dmisev

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!

Note: See TracTickets for help on using tickets.