UCB requirements October 2011

Owned by Chris Hoffman
Last updated: Oct 26, 2011Version comment
3 min read

Note: The following user stories are in draft form and are only roughly prioritized.  They represent several high priority areas based on discussions with PAHMA, UCJEPS, and HAVRC.  These are being described so that local development teams can work on design and ask questions.

Highest priority requirements that need action

  • Place authority: Work underway.  Patrick to check with Aron and Rick.  Parent task is CSPACE-4391
  • Concept authority: Schema adjustments and UI design nearly done and will be posted by Friday, Oct 28.
  • Image loading performance: Patrick to check with Richard to see if there are any expected changes in 1.12.
  • Citation authority:  Schema and UI done.  Chris to assign in Jira.
  • Data migration: Multi-value XML data. Xmlmerge lab session scheduled for Wednesday.
  • Data migration: Performance of import service. Chris to ask Yuteh to send Michael 5K records to load into his localhost to see if this could be a local config issue. Glen to check java heap settings?
  • Production upgrade of UCJEPS 1.8 to 1.12.  How do we migrate content (data and images)?
  • Batch processing: Glen needs more time on this task, and we might need to add a resource.
  • Hierarchical relationships between Object records: Chris to mockup wireframe and define semantics.
  • Non-hierarchical relationships between Object records: Chris to mockup wireframe and define semantics.
  • Non-hierarchical relationships between authority terms (e.g., synonymy) (ALL) See the wireframe that includes the Related Terms (or sometimes it is called Other Related Terms") repeatable field group on several wireframes on the /wiki/spaces/collectionspace/pages/666274420
  • Report administration user interface. Not sure of status.
  • Bulk import of media files (could this be done as a batch processing job?): Patrick to talk with Richard about approaches.
  • Advanced Search (PAHMA): User can paste in a set of object numbers or specify a range of object numbers to be found in an advanced search (PAHMA).  Or... create a batch process that will read a list of object numbers (in a file or window, whichever is easiest), and create a group/saved set.
  • Media Handling: Actionable link to a URL for an asset in another system.  See CSPACE-4415 (still assigned to v1.x).  CSpace not expected to pass authn credentials; user will authenticate if needed.  Ideally, this field would be repeatable and have associated attributes to be determined (e.g., date, type, note). As a result , the Image Record would not need to have an Image File uploaded. However, an Image Record that does have an Image File could use this field to identify where other versions of this image are deposited (e.g., CollectionSpace could have a JPEG while a repository has the TIFF).
  • Run CSpace over https: Patrick to investigate.

These are also important and are coming up soon to various degrees

  • Crates and mobile containers (new fields on storage locations plus some intelligence tied to movements)
  • UI for invoking batch process
  • Public web site: According to MMI, they are building this.  Will it be generalized so that others can use it?
  • Advanced search: Allow operators: >, <, , >=, <+, not equals, range (between).
  • Collecting event authority: Can it be based on Concept Authority? Probably not given place and calendar requirements.
  • Attach PDF, Excel, Word, anything -- no viewing needed, just a simple attachment model
  • Subloans
  • Customizing field groups by adding new fields: According to SMK, this will be done by 2.0
  • Specimen treatments and botanical propagation
  • Media viewing: Pan and zoom (User can view large images in a pan-and-zoom image viewer like tilepic, zoomify, GoogleMaps, or IIPImage)
  • Sticky Fields (UCJEPS): Based on the record we are editing, create a new record that retains some of the values on the current record (e.g., keep last-used scientific name on UCJEPS media handling). Could this be done via batch processing?  It would need to be invoked from the current record.
  • Delphi integration (PAHMA)

Other requirements to monitor

  • Authority bug (links to records in custom authorities not working): Some work is underway on this problem though timing of the fix is unclear (see Jiras CSPACE-3580 fixed in v1.12, CSPACE-3578 fixed in v1.8, 3579 in v1.13, 3588 fixed in v1.12)
  • Hierarchies in Organization authority - Scheduled for 1.13 (CSPACE-3737)
  • Change password - Users need a way to change their password. Is current approach (change password from main login screen really the only way?)
  • Structured dates - Need to be able to use these in repeating fields and repeating field groups. (Scheduled for 1.13)
  • Search across hierarchical and other relationships. (Depends on Nuxeo upgrade)
  • Search across structured dates - can be based on actual dates (early, late) and qualifiers. (Depends on Nuxeo upgrade)