UCB CSpace Deployment priorities - Jan 2012

Owned by Chris Hoffman
Last updated: Jan 05, 2012Version comment

This page is mainly capturing requirements that are not in Jira currently.

This priorities document brings together tasks for UCB deployments including those that are more closely related to development (and which used to be captured on a separate document).

Priorities key:  "**" = highest. "*" = high. none = moderate. "-" = low. Tasks with strikethrough formatting are completed.

Jira filters

Past week in UCB deployments

  • Resolved and closed tasks in UCB deployment projects and CSpace with IMLS label

This week in UCB deployments

  • Tasks with status In Progress on UCB deployments and CSpace with IMLS label. 
  • People need to click Start Work button for tasks In Progress

Current release UCB deployments not in progress

  • For current release, tasks with status open or reopened for UCB deployments plus CSpace project with IMLS label

CSpace-IMLS tasks not in progress

  • To find things like Place Authority (UCB IMLS label) not in progress. Looks across all versions.

Priority tasks that require dev team assistance

  • * Citation authority: Design and schema complete.  Chris to add to Jira.
  • * Object relationships (hierarchical and non-hierarchical): Design drafted.  Chris to send out for review.
  • * 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
  • * Image loading performance: Patrick to check with Richard to see if there are any expected changes in 1.12.
  • * 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).
  • Import service refactoring (larger loads and performance. On an 8GB VM with tweaked memory settings, we can only load 2750 catalog records with full schema). Jira created.

PAHMA priority tasks (not in jira)

  • PAHMA: Upgrade customizations to 2.0 (Ray)
  • PAHMA: Incorporate Place Authority (TBD)
  • PAHMA: Import media records (PAHMA has more than 1.5TB of content to import or link to)
  • PAHMA: Crates and mobile containers.  (new fields on storage locations plus some intelligence tied to movements)

UCJEPS priority tasks

  • UCJEPS: exchanges (TBD)
  • UCJEPS: e-loans (digital image requests) (TBD)
  • UCJEPS: Incorporate Place Authority (TBD)

HAVRC priority tasks

  • HAVRC: Move current 1.12 tasks to 2.0 (Chris)
  • HAVRC batch process: DAM-ECM workflows

Botanical Garden priority tasks

  • * Bot Garden: Upgrade services for 2.0 (TBD)
  • * Bot Garden: Upgrade app layer for 2.0 (TBD)
  • * Bot Garden: Upgrade UI for 2.0 (TBD)
  • * Bot Garden data: ETL work on taxonomy, specimens (Lam)

Other deployment tasks

  • * MVZ fit-gap and planning (Chris, Lam)
  • * Essig fit-gap (Chris, Joyce) and prototype (1.8 prototype running on ucjeps.collectionspace.org)
  • * UCMP fit-gap (Chris, Joyce)
  • * Release management: Tagging, branching, etc. (Glen and Ray)
  • * Mapping and Place-related: John D to lead task teams on Place Authority, mapping (via Berkeley Mapper), and georeferencing
  • * Design work on invoking BerkeleyMapper from CSpace.  (Amy. Jira created.)
  • Prototyping and dev work on invoking BerkeleyMapper from CSpace.
  • Design work on invoking georeferencing services from CSpace

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

  • 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.
  • Create role-based screens (e.g., limited data entry screens for students and volunteers) (TBD)
  • 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)
  • Create New enhancements: Limit the fields that get duplicated when "Create New From Record" is clicked.  was Sticky Fields: 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)