Travel information and reimbursement forms
Out-of-town attendees will stay at the Hotel Shattuck Plaza, 2086 Allston Way, Berkeley, CA 94704. If you haven't already, please let Megan know your arrival and departure dates so she can make reservations. Individual reservation numbers will be sent under separate cover.
- Airport information
- Reimbursement forms
- MMI Reimbursement Form
- If you have never been paid as an individual by MMI before, please fill out either a W-9 (US Citizens) or W-8BEN (Non-US).
Meeting location information
This agenda is subject to (considerable) change. It will settle by early next week.
Agenda: Wednesday, February 8th (Start time: 1:00pm)
1:00 to 2:30: Intro and discussion of current implementations, methods, and tools
Tell us about your deployment (a chance for big-picture introductions and context). Include how you do development, and the specific pain points in your development process.
Answer these questions as part of your intro (this will help guide the emphasis for the next few days):
- Have you done simple UI customization, like changing a label, or hiding a field?
- Have you done more ambitious UI customization, like changing layout of a record editor, or changing theme for whole UI?
- Have you built a new UI widget, or changed the behavior of an existing one?
- Have you done any schema extensions? Simple (few scalar fields) or complex (new, complex schema structures, repeating groups, etc.)?
- Have you added a new procedure or authority?
- What other types of customization have you done?
Related Discussion and Documentation
Museum of the Moving Image (20 mins)
Statens Museum for Kunst (20 mins)
Walker Art Center (20 mins)
History of Art Visual Resources Collection (10 mins)
Phoebe A. Hearst Museum of Anthropology (10 mins)
University and Jepson Herbaria (10 mins)
2:30-3:15: Core development team on development process, development tools, source code repos, etc.
30 minutes of presentation and discussion, and 15 minutes of questions.
Topics:
- How central team uses and manages development tools
- How we use repos (SVN and GitHub), for core development.
- How UCB is managing source code for local work
- Models for implementers to manage their local code, and planning for code contributions
3:15-3:25: Bio break (brief!)
3:25-5:00: Strategies for local and community extensions
This will inform the discussion of how we do specific extensions, to be covered over the next few days.
Topics:
- Comparing notes on how you have approached extensions
- What's coming with regard to the IMLS community of practice templates.
Goals (takeaways that are critical to completion of IMLS grant) include the following. Note that this session is an introduction to these topics - we will not complete all this in 90 minutes! We'll discuss this over the next few days, and will revisit these goals in subsequent sessions.
- A documented approach and set of clear steps for the mechanics of how to assemble the set of extensions that a museum would want to use to build their tenant.
- A framework/model and documentation for:
- where templates and extensions live
- how templates are discovered and accessed
- how templates are integrated into local development
- how templates are documented and maintained.
- governance models for templates
Related Discussion and Documentation
Community code contribution process (walk thru of the process to contribute code back to CSpace using examples from UCB)
Related Discussion and Documentation
Discussion and Process Around External Code Contribution
Code Contribution Draft Workflows
/wiki/spaces/collectionspace/pages/666276095
/wiki/spaces/collectionspace/pages/666275266
Agenda: Thursday, February 9th (Start time: 9:00am)
Morning:
We'll do some walkthroughs of customization and extension talks and use-cases
(Below will be updated)
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)
Related Discussion and Documentation
CSpace + Localization (this conversation is on-going and needs a collective conversation to bring it to the next level)
Related Discussion and Documentation
(Before or after lunch) David Greenbaum on sustainability and foundation
Afternoon:
More on community contribution models and practices
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)
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
Other issues that you would like to discuss (Meeting attendees: Please add your issues here)
- Configuration
- Using the common REST APIs
- data import and ETL
- http://issues.collectionspace.org/browse/CSPACE-3894 (adding/removing fields to groups)
- ...
Wrap up
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
Museum of the Moving Image
Jesse Martinez, lead deployment engineer
Statens Museum for Kunst
Christopher Pott, lead deployment engineer
University of California, Berkeley Implementation Team
Chris Hoffman,Informatics Services Manager
Yuteh Cheng, UCB Implementation Engineer
John Deck, UCB Implementation Engineer
Glen Jackson, UCB Implementation Engineer
John Keller, UCB Implementation Engineer
Ray Lee, UCB Implementation Engineer
John Lowe, UCB Implementation Engineer
Lam Voong, UCB Implementation Engineer
Amy Wieliczka, UCB Implementation Engineer
Walker Art Center
Chris Thompson, co-deployment engineer
Nate Solas, co-deployment engineer