Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manually editing Registry database for a change in geographic extent #139

Open
maccraymer opened this issue Dec 8, 2020 · 1 comment
Open
Labels
bug Something isn't working

Comments

@maccraymer
Copy link

maccraymer commented Dec 8, 2020

Using the staging registry, test the possibility of manually editing the contents of the SQL database to implement clarifications that cannot be made in the GUI because of interface bugs. For a specific example, try changing the geographic extent of item 736 (NAD83(Original) to NAD83(CSRS) v6 [NLv1]). The extent is presently:

Canada - onshore and offshore - Newfoundland and Labrador.
60.38 deg North Latitude
46.56 deg South Latitude
-52.54 deg East Longitude
-67.82 deg West Longitude

It should be changed to:

Canada - onshore and offshore - Newfoundland.
54.0 deg North Latitude
46.0 deg South Latitude
-52.0 deg East Longitude
-61.0 deg West Longitude

@maccraymer maccraymer changed the title Directly correcting an geographic extent for item Manually correcting Registry database for a change in geographic extent Dec 8, 2020
@maccraymer maccraymer changed the title Manually correcting Registry database for a change in geographic extent Manually editing Registry database for a change in geographic extent Dec 8, 2020
@maccraymer
Copy link
Author

I was able to submit a clarification proposal without any changes to the item's content but with a comment added in the Justification field. The Justification field can be used to record any manual edits to the Registry database. The justification notes will then appear in the Management tab of the items details view as a clarification.

@maccraymer maccraymer added the bug Something isn't working label Dec 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant