expansion - divide up notes section
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Gratian |
New
|
Medium
|
Unassigned | ||
Bug Description
see also: (context explained below)
https:/
https:/
https:/
bat said
"If you find yourself frequently using the notes facility in particular ways -- for example, noting the origin of awards or marking a particular name as the person's preferred name -- let me know that too and I may make it an explicit column in the database.
We've done something very similar with the medication management software I work on in my mundane job. Originally the software contained nothing more than "name of medication" and "notes"; gradually we've added more columns (time, date, frequency of administration, etc) based on how our users were filling in the "notes" column. The result is software that evolves in the way the users _want_, not just the way they _think they want_. "
A number of recurring types of notes can currently be identified in the notes section.
1) name validation information - notes on the source of the person's names (mundane & sca main, sca alternate), recorded mispellings (so they can be searched for during an audit of old data sources), etc This also includes notes on name and heraldry registrations. which ties to request:
https:/
Note that even if heraldric registrations were added, there will still be plenty of notes regarding unregistered names, preferred names, etc.
3) award validation data - notes on the source of the award and it's veracity. I'd prefer this tied to each award, as this would save a lot of typing in the notes section and make sure it was filled in for each award. See
https:/
Also general notes regarding missing awards - eg if a friend says he thinks someone has an award, it's too vaugue a comment to enter the award, but it is worth noting as something to follow up. Even a resolved claim (friend claimed he had an GT - person confirmed definately does not) is worth noting as it's likely to reoccur.
4)contact details
5)group validation data - notes on the person's home group and how directly linked to the person the source is
6) currently rare (but only due to slack data keeping - there should be more) stuff that royals should know such as "will not accept awards"
see https:/
6) Other stuff including general chatter, or that I may have forgotten.
I feel that the general data validation fields are drowning out infrequent but important notes such as "will not accept awards" "deceased" etc. While I'd prefer to see the awards validation and heraldry and royal notes removed to seperate fields as described above, there will still be a lot of info. Perhaps the simplest initial division would be to create a data validation notes field, and see what was left behind. Creation of a data validation notes field could be done before or after creation of any of the other new fields proposed in other feature suggestions linked to.
| Changed in gratian: | |
| importance: | Undecided → Medium |
| Teffania (teffania) wrote | #1 |
Please note, curently the grouped notes field is aiming to use internal divisions like this:
[royal notes]
note text here - eg refuses awards, preferred title (most will never be attributes - the sort of things that require sentence explainations)
[general validation]
note text here - generally about source of names & group, name & device registration, contact email (canon use only), perculiarities of name, deceased, any other useful info
[award validation]
note text here - name of award then source of award, and occasionally notes regarding dubiously doccumented awards
[end]
Not all notes have been upgraded to this format, and some will be mispelt too (validation is tricky!), but this might make some automated transfer of the bulk of data easier.