Pre-implementer meeting - Yura and UCB team 7-8 February 2012

The goal of the pre-implementer meeting is to build more knowledge about the UI across the team.  Key questions: If we have people with strong HTML, CSS, and JavaScript skills, how can they more quickly contribute to the development of the rich CollectionSpace UI?  A broader understanding of Infusion and of CSpace-specific UI will help a lot. We will use some specific requirements to ground the discussion.  In addition, UCB deployers want to talk about the widgets from other libraries and generally how to approach situations where one needs to extend or troubleshoot an existing UI capability (e.g., structured dates).

This meeting will help inform the agenda for the larger group meeting (February 9-10)

Tuesday morning, February 7

9-9:30am: Standup

(Adobe Connect)

9:30am - noon (Conference Room 101A):
Overview:

Quick sketch of the layer cake. What parts of the UI framework are Infusion? Which are CSpace-specific?  What are the dependencies?

Walkthrough: Procedural record page load and save

What loads in what order?

Particularly:

  • CSpaceInfusion.js
  • PageBuilder.js
  • RecordEditor.js
  • Requests and responses to and from app layer; incl. AJAX
  • Mapping from URL to template
  • Bootstrapping
  • Tomcat
  • Payloads (UISpec and UISchema)
  • Events
  • Configuration
  • Validation

Tuesday lunch

Tuesday afternoon 1-5 (Conference Room 110)

Continue walkthrough if needed, but switch over to examples as soon as possible.

Examples of things we want to be able to do in the UI. Based on discussion, some of these will be explored further in the meetings later in the week.

  • Add link or button that examines a field that is a URL (e.g., link to image in another system) and opens that link in a separate browser window.  See http://issues.collectionspace.org/browse/CSPACE-4415
  • Add link or button that works with an external web service (e.g., sends locality info to Berkeley Mapper and draws a map; sends locality text to a georeferencing service, receives locality data back from the service, and stores data in system)
  • Modify report widget to invoke batch processes
  • Modify report-batch widget to display a dialog requesting parameters for job
  • In authorities, derive the displayName field from other information on record; set on save.
  • Integrate data from related record on page (e.g., to display information from a related record on the main panel or right panel)
  • On Cataloging, add a link or button to attach image (creating the media handling and relations_common records)
  • On Cataloging, display image thumbnail if related media handling record exists
  • Clicking on an image thumbnail opens image in a pan-and-zoom viewer, also allowing for image rotations.
  • Add a radiobutton to Create New to create records in different instances of Concept authority (e.g., we will have Default, Materials, Techniques, and Cultures instances of the Concept Authority for PAHMA).
  • Demands.js
  • Testing - start process by writing test first.
  • Specific strategies for troubleshooting UI problems

Tuesday evening - Take Yura to dinner

Wednesday morning: UCB with Yura and Chris M.

9:00-11:30

Structured dates in repeating groups: Let's work together on http://issues.collectionspace.org/browse/CSPACE-4779

Structured dates display issues: Let's work together on http://issues.collectionspace.org/browse/CSPACE-4787

Adding fields to field groups: Let's work together on design issues and approach related to http://issues.collectionspace.org/browse/CSPACE-3894

Noon-ish Full implementer meetings begin