- Plan to stitch the documentation together to reduce overlaps and improve organization. Current editorial team: Lydia Tang (Visual, everything), Alexandra Orchard (Navigation), Betsy Baldwin (Visual, Organization of Menus), Lynn Moulton (Data Entry), Joanne Archer (Customization), Caitlin Wells (Customization), and Devon Proudfoot (Permissions). Currently needing at least one person from the Data Entry/Edit and Time-Saving Devices teams. Additional volunteers are welcome!
- Plan to ask teams to proof-read various sections of the report in the future.
- Ideally finish up documentation by Tuesday. And send out a draft to the group to proofread the draft overall report by a page count. (Teams assigned set page numbers.)
- Volunteers needed!
|
| Customization/Functionality/Other Topics
| | - View document: https://drive.google.com/drive/folders/0B1sCz9Bz_GBkZDJsTlQ2WkFxRFE
- Several Jira tickets requested some ways to customize the view of the data entry to hide fields that are not relevant. As well as customize the labels or order of fields and save into templates. Recommend checkbox to display
- Good to use templates to save these. And apply those to different types of records (accessions, resources, digital objects, etc.)
- Allow users to choose which fields are most important.
- Users are currently able to choose the order of display for notes. Recommend doing this for everything.
- Search and browse display. Two ways to go about improving search and browse results. 1) Increase the fields viewable, or 2) allow users to set preferences. Adding these can be prolematic since there can be multiple dates, so that would need to be figured out. Many accessions/resources have various extents.
- repository branding. brand distinctive repositories within the ASpace interface. Branding this on the staff backend (vs PUI – visual team looked at it from this perspective)
- Teminology: Subjects (suggest Access Points instead)
- Background jobs: No one really knows what this is unless you've been using ASpace. Renaming ideas: Tools, Actions, Functions, etc. Can think about this as a group. Includes Print to PDF (generate pdf?) etc other terminology
- Feature request for spell check! Prob don't want to get into the agents field and skip proper names.
- Version control. Have the ability to control display version. Not entirely sure what that would mean. What aspects of version control would be helpful.
- Collection mgmt module. This might have to be addressed in the future once new modules are introduced (e.g. assessments)
|