ISO-TC211 / iso-geodetic-registry

ISO Geodetic Registry backend
https://registry.isotc211.org
Other
5 stars 4 forks source link

Japanese Geodetic Datum 2011 entry corrupted? #125

Open maccraymer opened 4 years ago

maccraymer commented 4 years ago

The Japanese Geodetic Datum 2011 (JGD2011) entry in the public and staging Registry (item 138) appears to be corrupted. When I create and save (or submit) a simple clarification of this item, I get an HTTP Status 500 – Internal Server Error when trying to display the details of the original item in the Registry. The beginning of the error message is:

Type: Exception Report

Message: Request processing failed; nested exception is org.thymeleaf.exceptions.TemplateProcessingException: Exception evaluating SpringEL expression: "pmi.fromJson('{"aliases":["JGD2011"],"definition":["Japanese Geodetic Datum 2011"],"anchorDefinition":[" Equivalent to ITRF2008 at epoch 2011.395 (2011-05-24, 12:00 UTC) in Northern Honshu area. Fundamental point: Tokyo-Taisho, latitude: 35°39'29.1572\"N, longitude: 139°44'28.8869\"E (of Greenwich). Equivalent to JGD2000 elsewhere."]}')" (registry/item:212)

Although the first part of the Message gives the correct attributes for the JGD2011 item but the very last bit indicates it is registry item 212, which is a completely different item (CRS entry SIRGAS-CON DGF04P01 - LatLonEHt). The original JGD2011 item is actually item 138.

At first the error was resolved by returning the proposal to the submitter and deleting it. However, upon re-creating the clarification, re-submitting it again, then testing the CB rejection of the proposal and having the submitter appeal it, the proposal was subsequently withdrawn, the original item could no longer be displayed properly even after withdrawing the proposal. The database now appears to be corrupted.

Submitting, accepting and approving the clarification proposal into the Register did not resolve the problem. The item still gives the Internet Server Error. I will submit a separate request to restore the database again.