Configure whether RAD and ISAD area headings are displayed to unauthenticated users
|Assignee:||Dan Gillean||% Done:|
|Target version:||Release 2.1.0|
|Google Code Legacy ID:||atom-1950||Tested version:|
Based on SK development list, this item is based on the assumption that at least some area headings are not meaningful for non-archivists. This issue is part of the upcoming usability testing.
Part of current SK development.
#6 Updated by Tim Hutchinson over 8 years ago
Dan, I'm now at the point of nailing down the requirements for the three or four issues USask is able to work on this fall. From earlier e-mail correspondence, I think we agreed to add this screen to the existing "visible elements" page of the settings rather than a separate page. However, I would appreciate your feedback on the details.
There are really two options:
- add two collapsible tabs, "ISAD template - area headings" and "RAD template - area headings"; then rename the existing tabs "ISAD template - elements" and "RAD template - elements"
- add the area headings to the existing tabs, but with headings to offset the area headings (at least Area headings: to follow the list of elements
I'm leaning towards option one as being a bit cleaner. Any thoughts?
#7 Updated by Dan Gillean over 8 years ago
Great to see that this is still underway! I agree with you, I think that option one will be clearer to end users. Keeping them in two distinct but related sections will more clearly indicate that one part has to do with the visibility of the headings in each information area, while the other has to do with the actual elements of the information areas themselves.
Let us know how the work with the 2.x branch goes, and feel free to put your developers in touch with us via the user forum if any questions arise!
#10 Updated by Redmine Admin over 8 years ago
Tim (and Steve),
This is incredibly exciting! Jesus is wrapped up in client work at the moment, but we will do everything we can to look at these pull requests soon. I'm eager to take a look myself! Once again, thank you for all your careful planning, and hard work. Congratulations!
#13 Updated by Dan Gillean over 8 years ago
- Assignee changed from Tim Hutchinson to Dan Gillean
Don't worry, I haven't forgotten about this! I have in fact done some initial testing, and haven't yet encountered any problems, which is very encouraging. Jesus was also very pleased with how methodical and careful Steve was with the code - thank you. I expect to verify it soon, based on my initial testing, but I wanted to have a chance to do another pass, and test the ISAD integration a bit more thoroughly. Expect more updates soon!
#16 Updated by Dan Gillean over 8 years ago
- Status changed from QA/Review to Verified
Tim (and Steve),
I've done some more testing on this - today I tested it on a description where different levels were set to use different display standards, and everything worked as expected, both when logged in and out. This has also been sitting in our development environment without any noticeable regressions elsewhere for some time - and I imagine the same is probably true on your end. It looks great! I haven't found a bug yet, so I will verify it - we still have time before the 2.1 release in case anything pops up, but I know Jesus was happy with the code, and I'm not expecting problems, based on the tests i've done.
#17 Updated by Tim Hutchinson over 8 years ago
Thanks, Dan. Personally I think any archivist using more than one descriptive standard in the same description should be shot at dawn, but good for you for thinking of that extreme case :) Thanks to both you and Jesus for getting this merged and verified in good time.