Versions Compared

Old Version 26

changes.mady.by.user Patrick Schmitz (Unlicensed)

Saved on

compared with

New Version 27

changes.mady.by.user Patrick Schmitz (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Agenda: Thursday, February 9th (Start time: 9:00am)

Morning:

8:30-9:00: Breakfast

9:00-9:15: Recap and Agenda review

...

We'll canvas the group to choose from among the following list of use-cases. Most of them will illustrate general principles, but each of them has distinct technical issues.

  • Build a custom procedure (e.g., Claim/NAGPRA Claim)
  • Build a custom authority (e.g.

...

How to create procedures and authorities (we know that you will want to create them so, we'll spend some time creating them together to help you get the hang of it)

  • , Place)
  • Customize a procedure or authority
    • Rename field or authority
    • Add a field to a local or domain schema
    • Apply another schema (from a template) to your record
    • Add a field to a repeating field group (can not be done now without replacing the whole group -- what could we do to change this in the system?)
    • Blue sky: Fundamentally change the data model (e.g., to display information from a related record on the main panel or right panel)
  • Add UI widget or capability (following discussions in the pre-meeting on Tuesday)
    • Add link/button that examines a field that is a URL (e.g., link to image in another system) and open browser window)
    • Add link/button that talks to an external web service (e.g., sends locality info to Berkeley Mapper and draws a map; sends locality text info to a georeferencing service, gets back locality data, stores data in system)
    • Modify/extend report invocation widget to also invoke batch processes
    • Modify report/batch widget to display a dialog requesting parameters for invocation
    • Integrate data from related record on page

Related Discussion and Documentation

...

  • The existing workflows for making contributions
  • Gaps or weak areas in the existing workflows and process
  • Facilitating cooperation and preventing duplication of effort
  • Variants or different classes of contributions. E.g.,
    • a new procedure vs. a new template,
    • UI translations,
    • documentation and translations thereof
    • etc.
  • Structure of the community repository
  • Guidelines for adopters of contributions (especially templates)

Evening: Drinks and/or dinner?

Possibilities (assuming the predicted good weather):

Agenda: Friday, February 10th (Start time: 9:00am)

Morning

Continued from Thursday: Community code contribution process (discuss development of features, functions, procedures, authorities that any early adopter is considering taking on in 2012 - to make sure that efforts are not being duplicated)

Note: As part of the IMLS National Leadership Grant, these features/functions are currently being developed, have been developed, or were proposed to be developed by a museum involved in the grant.  

Museum of the Moving Image

  • interface for publishing collections on-line
  • procedures for condition checking and technical assessment

University of California, Berkeley

  • management for taxonomic, place, and concept term authorities
  • Native American Graves Protection and Repatriation Act (NAGPRA) management
  • batch processing examples
  • design and planning to extending collection objects and media objects to support hierarchic structures

Walker Art Center

  • API for using RFID to manage collections movement
  • procedure for managing insurance assessments and valuations

Afternoon

Others?

Evening: Drinks and/or dinner?

Possibilities (assuming the predicted good weather):

Agenda: Friday, February 10th (Start time: 9:00am)

8:30-9:00: Breakfast

9:00-12:00: Discussion of community contribution process (contiunued)

Continued from Thursday: Community code contribution process (discuss development of features, functions, procedures, authorities that any early adopter is considering taking on in 2012 - to make sure that efforts are not being duplicated)

12:00-12:45: Lunch (brought in)

12:45-4:45: Other issues that you would like to discuss (Meeting attendees: Please add your issues here)

4:45-5:00: Wrap up, next steps

Attendees

CSpace core development team
Patrick Schmitz, (UCB) CSpace Technical Lead and Meeting Leader
Rick Jaffe, (UCB) CSpace User Interface Engineer
Chris Martin (CARET) Application Layer Engineer
Richard Millet (UCB) CSpace Services Development Lead
Aron Roberts (UCB) CSpace Services Engineer
Yura Zenevich (OCAD) User Interface Engineer
Antranig Basman (Independent) User Interface Engineer

...