1. OpenREM Avatar OpenREM
  2. OpenREM
  3. OpenREM
  4. Issues

Add ability to refresh standard name linking in the database

Issue #956 resolved
David Platten created an issue

I would find it useful to be able to import an existing standard name table from a test system into a new install and make it work with existing data. For this to happen it must be possible to refresh the hidden relationship between the standard names and the associated studies and acquisitions.

Comments (10)

  2. David Platten reporter

    The current code works, but the location of the buttons and how they react when clicked makes it inappropriate for merging:

    • The process takes some time, so once a “refresh” button is clicked it needs to be made inactive (together with any other buttons on the page) until the process is complete
    • It may be better to take the user to a separate page on button click, where they can be asked “Are you sure” before carrying out the processing. This page could also provide warning that continuing may take a while

    ‌

  3. David Platten reporter

    buttons for refreshing standard name links in database now take the user to a separate page to make the implications of clicking the button clear. Refs issue #956

    → <<cset 0825ad5ca9cc>>

  6. David Platten reporter

    Removed standard name refresh buttons from the standard name list page and put them on the standard name settings page with a short description. Refs issue #956

    → <<cset 65a0677bfe0f>>

  7. David Platten reporter

    When I replaced my standardnames table with a new one it caused an issue that has prevented any new standard name mappings from being added.

    Running the following and then putting the contents of sequence-reset.sql into the pgAdmin 4 query area and running the queries has fixed my problem, but I need to find out why it happened:

    python manage.py sqlsequencereset remapp > sequence-reset.sql

  9. David Platten reporter

    Adding checks for IntegrityError when adding a new standard name entry to avoid a server error. This error is thrown if there is an issue with duplicate primary keys in the standard_names database table. This happened to me when I manually updated my standard name table using pgAdmin 4. The solution was to execute 'python manage.py sqlsequencereset remapp' and then use the SQL output to update the OpenREM database. This needs to go into the documentation for the standard name mapping, but I suspect no one but me will encounter the issue. Refs issue #956

    → <<cset 91058978e273>>

  11. Log in to comment
Assignee
Type
enhancement
Priority
minor
Status
resolved
Component
Interface
Milestone
1.1.0
Votes
0
Watchers
1
Jira: the preferred issue tracker for Bitbucket. Join the team!