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

Allow multi-select for Display Name updates

Issue #378 resolved
Ed McDonagh created an issue

Allow multi-select via a tick box or shift/ctrl click to update multiple entries simultaneously to be one Display Name.

Use cases:

  1. Single modality that changes details often (department name for example)
  2. Join multiple sources into a single entity, eg "Imported"

Comments (15)

  2. David Platten

    Further work on enabling the update of multiple display names at once. Created a new view, which will eventually replace the original one. The multiple pks are now passed to the update page. Need to make the update page cope with multiple values being sent. References issue #378

    → <<cset 9489880d972f>>

  3. David Platten

    Updated code so that multiple systems can have their display name changed to a new, common value all at once. I haven't removed the original methods in views.py or the lines in urls.py that were used by the old display name updating code yet. References and fixes issue #378

    → <<cset 943038cc358d>>

  4. David Platten

    Removed unneeded url references and a view. Added JavaScript to ensure that if the user clicks on a checkbox that it toggles. References issue #378

    → <<cset 208edaa75f15>>

  7. David Platten

    @edmcdonagh, I'm not sure that how I've implemented this is the best way. Some users may wish to update the display name of multiple system to a new set of different display names (not all the same one). I could make the "update display name" page show each system that you've chosen, with an input box for each of the systems (containing it's current display name). If a user wants to update the name of each individually then they can. However, if you want to update all of them to the same name then you could use a special input box at the bottom of the list. Entering text in here would cause all of the display name input boxes on the page to be updated to whatever you type.

    Any thoughts?

  8. Ed McDonagh reporter

    Hi @dplatten. I have had a play with this on my system, and it does exactly what I was hoping for.

    Regarding your suggestion about changing a subset of systems to a variety of names; I'm not sure I can see the advantages over what you have already created. It would be marginally quicker I guess when going through a lot of changes, but only really if there are lots of changes to individual systems (if any two are the same, you'd want the other behaviour).

    So I'd like to take it as it is. What do you think?

  11. Ed McDonagh reporter

    Further work on enabling the update of multiple display names at once. Created a new view, which will eventually replace the original one. The multiple pks are now passed to the update page. Need to make the update page cope with multiple values being sent. References issue #378

    → <<cset 9489880d972f>>

  12. Ed McDonagh reporter

    Updated code so that multiple systems can have their display name changed to a new, common value all at once. I haven't removed the original methods in views.py or the lines in urls.py that were used by the old display name updating code yet. References and fixes issue #378

    → <<cset 943038cc358d>>

  13. Ed McDonagh reporter

    Removed unneeded url references and a view. Added JavaScript to ensure that if the user clicks on a checkbox that it toggles. References issue #378

    → <<cset 208edaa75f15>>

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