Changes between Version 8 and Version 9 of Ticket #1257


Ignore:
Timestamp:
Sep 26, 2016, 1:20:41 PM (8 years ago)
Author:
Bang Pham Huu
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1257

    • Property Summary SECORE_Separte Rasdaman CRSs definition from userdb → SECORE_Update Secoredb by update scripts
    • Property Milestone 10.0 → 9.3

  • Ticket #1257 – Description

    v8 v9  
    1 By default, SECORE deploy with EPSGdb and userdb which contains Rasdaman CRSs (like TimeCrs, IndexND,...). When user want to add their CRSs, they can add/update via webpage. However, these new CRSs are not updated to usedb file but stored as changes by BaseX.
    2  
    3 The problem is when Rasdaman want to add some new CRSs (e.g: Alex just added some CRSs from PlanetServer on opengis by webpage (not by update the userdb file)), to active these CRSs, user need to clean the old changes from BaseX, then SECORE will recreate new cache. This will lead to remove the user definitions explicitly.
     1From Dimitar's revision, so we can make a UpdateSecore handler which will get the request based on file names (insert, delete) and each file contain a single CRS:
    42
    5 So, to make this problem will not affect in future:
     3    1-insert: will add a new CRS definition (e.g. UnixTime) and the handler class will insert it to the BaseX database. It will contain full valid XML for the CRS definition.
     4    2-delete: don't need the GML, just list a single gml:id, example: crs/OGC/0/UnixTime
    65
    7 + It will need to separate Rasdaman CRS from userdb to another file, such as: rasdamandb.
     6We don't have any place to store userdb update version yet. The latest update version will be stored in BaseX (in some way..). On startup, secore will automatically read the version:
    87
    9 + It will backup all the user defined CRSs from SECORE to userdb file (this is a tricky problem as need to know which CRSs were added/updated on their SECORE and read changes from BaseX).
     8   + if no version exists, then it runs the updates and stores the latest version
     9   + if a version exists, then it reads the version, checks if it equals the last update version; if it doesn't equal then it runs the updates and stores the latest version
    1010
    11 + Add a feature to save changes from BaseX for rasdamandb, userdb to GML files (so when add/update on these db by webpage, will not need to do it again by manually editing GML file).
    1211
     12The updates (each file is a new version) (1-delete, 2-insert, ...) should be stored somewhere. $RMANHOME/share/rasdaman/secore would be a good place.
     13
     14
     15With these changes, user defined CRSs can be kept and we can adjust rasdaman CRSs from userdb simultaneously.