Move 'not-patient-indicators' to the database with web interface

Issue #510 resolved
Ed McDonagh
created an issue

Not patient indicators are currently hard-coded. Commits related to issue #503 have moved this to settings, it needs to be moved to the database with a suitable web interface for configuring it.

Comments (68)

  1. Ed McDonagh reporter

    Completed the view of indicators page, linked to django admin interface to edit them. Removed all other models from admin interface for now - need to make sure this is ok. Haven't linked db fields into import checks yet. Refs #510

    → <<cset 109f34034a67>>

  2. Luuk

    I just had a look and agree with David. Tthe Django interface is clear enough to keep it that way. And of course it is prettier if you add your own form, but I don't think it is a necessity.

  3. Tim de Wit

    I agree as well... however, wouldn't it be better to use explicit regexp or wildcards for matching? That might solve the problem of test studies matching a real patient (at least there's more control for the admin-user on the matching part)?

  4. Ed McDonagh reporter

    Good point @Tim de Wit. Allowing regular expressions scares me a little - for trying to document how to use it if for no other reason!

    Maybe using fnmatch would be a good idea though - that would allow for wildcard matching that most people are familiar with.


  5. Tim de Wit

    Looks great! For testing replicating behaviour of release 0.7.4 administrator rights are required but I trust you implemented it correctly.
    Is that what we want though? "Opt-in" instead of "opt-out" by default? I could imagine some people might overlook this during an upgrade so perhaps behavior should stay the same by default and configurable for those who took the effort to actually read the changelog? :)

  6. Ed McDonagh reporter

    @Tim de Wit thanks for prompting me to look at what it looks like without admin rights, and apologies for not giving you any! Wasn't my intention, and fixed now.

    I have added a username of demo demotesting too to enable us to see whait it looks like as view only.

    I think I'd rather have opt-out by default, but I think that would mean adding in data migrations which I had shied away from so as to not make the upgrade any more difficult, but now you've made me look at the instructions it doesn't look so hard...

  7. Ed McDonagh reporter

    Looks like a data migration would turn a simple migration into a complex one with scary merges because we can't know what migrations precede it, and it would depend on what I'm hoping will be an auto migration.

    I have an idea though for some messages to pop up when an admin logs in that can be implemented or cleared as the admin wishes...

  8. Log in to comment