These are a set of priorities for estimating. Work will be scheduled later. (TBC- to be contributed; TBCL = general, less review, lightweight)
- Citation Authority: new functionality, TBC, low hanging. 4-5 labor days (services, app, and UI) First sprint.
- Improve database performance (reports, queries and term completion): in process, local (TBC) First sprint.
- Improve UI performance (page loading): in process, project
- Add Current Storage Location to Cataloging record and maintain automatically: new functionality, probably local, NTBC
- Design work already started on deployment team but need to select implementation (nuxeo event or UI-based?)
- 2-3 days?
- App-to-app bridge for web applications (public search portals, special-purpose applications like those built for PAHMA):
- Provide no-auth access to images and metadata (services): new, local, TBCL
- Provide user authentication wrapper outside of CSpace to talk to services: new, local, TBCL
- Search using criteria from different record types:
- could be hard or messy (if not use NXQL for query)
- One potential solution/workaround discussed by Michael and Chris is the addition of a universal-ish "Show related objects" button in the sidebar.
- Such a button would take the entire set of related cataloging records and display them as the result of an advanced search.
- This button, when combined with Ray's "add to record" button (and advanced search's ability to view up to 500 records), would give users a handy workaround to not being able to search across different record types.
- For example:
- User wishes to make group of objects claimed for repatriation in a specific NAGPRA claim (so conservators can examine those objects).
- Search for the NAGPRA claim record
- View NAGPRA claim record and see 104 related catalog records.
- Click the "show related objects" button to view the 104 catalog records as if they were the result of an advanced search
- Click the "add to record" button to add them to a pre-created group ("Objects included in CL 2012.4")
- Conservators can view group record to see claimed objects
- User wishes to easily browse all objects lent to a specific institution.
- A search for loan records for loans to that specific institution yields 2 loans
- View first loan and see 8 related catalog records.
- Click the "show related objects" button to view the 8 catalog records as if they were the result of an advanced search
- Click the "add to record" button to add them to a pre-created group ("Objects lent to Institution X")
- Return to the loan search results
- View second loan and see 15 catalog records.
- Click the "show related objects" button to view the 15 catalog records as if they were the result of an advanced search
- Click the "add to record" button to add them to the same group ("Objects lent to Institution X")
- Navigate to the group record
- Click the "show related objects" button to view all 23 catalog records ?(am assuming no duplications here) as if they were the result of an advanced search.
- User may now do whatever she wishes with these 23 catalog records.
- What would be even better is to also have the "show related objects" button on the advanced search results page:
- User wishes to easily browse all objects accessioned in the last 3 years.
- A search for accession records for accessions in the last 3 years yields 23 accession records
- Click the "show related objects" button directly on the advanced search page to view all 564 catalog records related to these 23 accession records, as if they were the result of an advanced search
- User may now do whatever she wishes with these 564 catalog records.
- Original use cases
- Allow advanced searches to to include objects related to certain procedure records. For instance, find all African objects lent between 1991 and 2000. Or find all objects donated by Albert L. Bender. People will want to make groups of these objects (e.g., allow non-NAGPRA staff who don't have access to the NAGPRA claims records to know what is being claimed so that they'll know which objects they need conserve, photograph, manage, etc. for the claim).
- I'd like to be able to search for all objects included in a particular loan.
- I'd like to be able to search for all objects related to a particular accession.
- I'd like to be able to search for all objects involved in a particular NAGPRA claim.
- I'd like to be able to search for all objects in a particular group.
- I'd like to be able to search for all objects with related media.
- I'd like to be able to search for all objects inventoried or moved by a particular person.
- I'd like to be able to search for all objects currently stored at a location whose fitness is noted as "unsuitable".
- And some "advanced" use cases, nice to be able to do someday but not required now
- I'd like to be able to search for all objects with no related media.
- I'd like to be able to search for all objects whose largest related image is less than 600 x 800 pixels.
- Delphi integration:
- v1: Delphi continues to work the way it does now for PAHMA. We just map to extract data from Postgres instead of SQL server: maintenance/adaptation (ETL, approx 17 columns or clusters, to create a CSV data source), and upload new images, local
- v2: Turn into a service that can be run and configured.
- vX: Do ontologies for other museums
- Make certain fields read-only for some roles (or permission groups) (or role-based templates)
- Assuming we are only talking about CSpace UI (not web apps or batch process)
- How does this work when people have multiple roles. Assume take most permissive role.
- Create groups of fields (e.g., financially sensitive) and build permissions around those instead of for every field. Build logic around that (might tie to search enhancements as well). All fields start in default field permission group. Decorate certain fields so they fall in specific permission group. Can this be administered through config? Adding UI would be lots of work (implications for not adding on the fly). XMLmerge would decorate the individual fields to make them read-only. Will require UI/Toronto help to do. Possible alternative approach based on services config of field groups and special permissions for these field groups not enforced by Spring but used by app layer (could be extended to work on search as well -- volunteers can't search for terms they shouldn't be able to). Either way, this is a lot of work to do.
- Allow attachment of PDFs and Word files to MH records (available in 3.0?)
- Validate that this is in current functionality
- Rotate images button: new, local, TBC
- Some UI
- Refresh situation so we see the rotated images
- What to do if only externally ingested image
- Would only work for stored images
- Might not be too bad to invoke ImageMagick
- Assume: Only for images, or up user not to do this on PDFs.
- Search to relate: option to use advanced search: Local, TBC, needs some local design and Toronto help
- What does UI look like? From Search to Relate or by starting on Advanced Search (which Ray has done with his Add to Record function)
- Allow and use designation of an image as the primary image (designated image shows first in thumbnail browser)
- Relations service: Does it have an order attribute already? Need to maintain order throughout
- Assume however primary is indicated on Media Handling. Might be able to do this now to change the order by statement on the services. Investigate. Local, TBC, (low hanging)
- Add columns to search results (on cataloging, add object counts and current locations, two or three fields)
- Ray has built a workaround for vocabularies
- There are some fundamental challenges here, but there are workarounds
- Need clear use cases (record types, add on the fly?,
- Batch image upload/association (using filename or rendition number): new, local, TBCL
- Separate web app or external batch process
- Is there overhead to doing it locally, requiring uploading images to server?
- How much error checking involved