Group Meeting May 19, 2015

1. Creative Commons License for our Morningside History project site
Near the start of our process, we discussed Creative Commons license options and settled on a CC-BY 3.0 US License. This is featured on the front page of our Developing Librarian process / blog site, which states in the bottom margin “This work is licensed under a CC-BY 3.0 US License.”

In our meeting today we discussed licensing and terms of use issues for our Morningside Heights Digital History project site. Unlike our process / blog site, our project site contains a substantial variety of different types of content: for example, original exhibit text written by team authors, images used with permission of institutions, etc.

Various things emerged clearly in the discussion:

*We need two kinds of license, or terms of use statements–one covering our original content and one covering images or documents that we are using with permission or through public domain.
We have authority to determine reuse conditions under a CC license for our original content. For images or documents we did not create, however, we need an appropriate statement in which responsibility for seeking reuse permissions, where needed, is left with the user.

*The default when no CC license statement is included is that originally authored materials are covered under ordinary copyright. We decided, however, that we should select and apply a specific CC license to the original content on our project site. The CC licenses
all share in common attribution, or crediting of author, as a basic element. There were varying opinions about whether or not we should select a CC license that adds ND (no derivatives) and/or NC (no commercial use) onto the basic CC BY license.

In the course of our discussion, we found it very helpful to consider
Omeka showcase
which provides links to a variety of Omeka sites and their statements of terms of use conditions.

Action Item:
Bob Scott and John Tofanelli will draft and send to the group for approval a terms of use statement for the project site. Once the group has approved that statement, Bob and John will submit it to Rina Panatalony, Director of our Copyright Advisory Office for review.

2. Libraries Information Technology Office (LITO) guidelines
Our Morningside History project site will be moving to a Columbia University Libraries (CUL) server before it launches publicly this June. We therefore need to bring it into conformity with standards applicable to all sites housed on CUL servers. We looked at Columbia Univerity Libraries’ “Visual Identity & Website Guidelines,” which is the key document. Alex will bring our site into conformity with these guidelines in terms of incorporating Columbia banner, etc.

Dr Strangedevelop, or how I learned to love the team

A French librarian graduating from Enssib (the French National Library School), training and interning at Columbia University Libraries for three months, from February to the beginning of May 2015, I was lucky enough to be given the opportunity to join the Developing Librarian Project and to become part of the developing team.

This experience has been very rewarding for a number of reasons and will reverberate on my practices and on the way I see librarianship and the role of libraries and librarians now and in years to come. What facets of the experience proved to be prominent for me? Many aspects are involved in this project, the goal of which is to reskill ourselves to support evolving modes of scholarship in the humanities (see the article published by Nikka Bakkalbasi, Damon Jaggars and Barbara Rockenbach in Library Management (Volume 36, Issue 3), entitled Re-skilling for the digital humanities: measuring skills, engagement, and learning). I would like to focus on the day-to-day experience: what does it feel like to be a developing librarian on a daily basis and to set out on this journey? In this respect, the few aspects of the Developing Librarian Project that especially stand out in my view are a special stance on research and scholarship produced by librarians as a team, the development of technical skills on the go, and the team building experience.

Getting involved in A Digital History of Morningside Heights implies, of course, a fair amount of research and scholarship. I took over from Mary Cargill and chose to deal with the Leake and Watts Orphan House, the remains of which can still be seen appending the Cathedral of St John the Divine. It seemed interesting to focus on various aspects: first, the creation of the house itself, which stemmed from a strange will, the architecture, at the same time typical and strangely unrecognized, the rural feel surrounding the building that was considered as so pleasant, and the welcoming policies and living conditions of the orphan residents.

What is left of the Leake and Watts Orphan House on the Morningside Plateau, April 2015

What is left of the Leake and Watts Orphan House on the Morningside Plateau, April 2015

Focusing on the Leake and Watts Orphan Asylum, which was set up on the Morningside Heights Plateau in 1843, implied turning to 19th century newspapers to retrieve pictures and to understand how the mission of the Orphan House was perceived by the contemporaries. It also meant turning to material like censuses or, strangely enough, travel guides. Finding this material is, of course, a matter of thorough research through the databases. However, working in a team together focusing on different items with different approaches creates a seminal serendipity: going through a database for one’s own research, one stumbles on material that pertains to another item in the project that the team member has not noticed because their sources and approaches are different. Travel guides in the 1850s happen to mention the Leake and Watts Orphan House among other orphanages and along with the Bloomingdale Asylum as places to visit, for instance, an unexpected mention that came up through research but also through exchanges with the other team members using this resource. The bimonthly Morningside Heights meetings enabling every member to present their items are a means of creating a unity in the whole project, while respecting each and every member’s chosen angle: a common object is designed, which is not only the product of a community but which also creates a sense of community just through the way the library staff can appropriate the history of Columbia itself.

Contributing to the digital history of Morningside Heights implies reskilling oneself and developing technical skills that can be learned from online tuition (html, css), but that also have to be practiced and mastered on the go, day after day. If online lessons are useful, progress comes from learning tips from your coworker in workshops targeted at building up the final Omeka website. It all amounts to learning by doing and to appropriating the tool step by step, and, what’s more, to appropriating it together and for a common purpose.

More than from learning from an online learning platform, a sensible use of the tool results from building up the html and the css together, through trial and error. What comes as a surprise is that even the less advanced can contribute to building the final product. Answering questions also enables the respondents in the team to make sure that they master a set aspect of coding. To me, the main asset of this learning process is the way it contributes to building team spirit. Team spirit does not just come from any project carried out together: it stems from the sense of purpose that the learning process eventually acquires in this case.

Becoming a developing librarian for a while also amounted for me to developing into a librarian proper and to contributing to a team intent on rethinking libraries as constantly evolving libraries.

Group Meeting, May 5, 2015

1) Development Team Update
The Development Team showed our group the new home page for our Morningside Heights Digital History project site. This new page incorporates an historical map for Morningside Heights with its original colors restored (and slightly heightened for emphasis and clarity). The page surrounding the map was also revised to be in a color scheme that complemented the map. These color scheme revisions originated in decisions made in our Design Team. The revised color scheme represents a departure from our earlier plan of determining a desired color scheme for home page and altering the map coloring to fit that scheme.

2) Transitioning to CUL Server, Current Status and Issues
There were four outstanding questions which LDPD had addressed to our group. They needed to have these questions answered prior to transitioning our Project site onto a server administered by Columbia Libraries. We reached consensus for most of these questions. For example, we do want the project site cataloged. After considering the commitment involved in migrating the site again and again as needed, we agreed that we would: a.) keep it alive until a migration was needed and b.) make sure that it gets preserved as a frozen site. The Development Team was charged with discussing issues for which questions remained.

3) Summer Schedule
Various options for a summer schedule were discussed. It was decided, however, to table this discussion until we have understood more about what will be involved in Phase 2 of project. Phase 1 of the project, the Morningside History website, is still slated to be launched in June 2015.

4) Phase 2
The group considered that substantial time and effort had been required for Phase 1 of The Developing Librarian–the construction of the Morningside History project site. For phase 2 we agreed that we would retain the emphasis on developing and enhancing digital skills but abandon the idea of all contributing to a single digital project. Instead, we will work on individual digital projects of our own choosing. We will still dedicate group time to labs and meetings and we will educate one another about our projects.

Action item: each member should send a description of his or her individual Phase 2 project to Barbara. The Developing Librarian blog will still be actively maintained to chart our progress in Phase 2.

5) Friday open labs
Barbara has sent out invitations to the group for a series of Friday open labs in May and early June. These are optional lab sessions in which group members can work together in finishing up work needed to be done prior to project site launch in June.

Fair Use Week

This week marks Fair Use Week in the library world. Fair Use affects all of us as librarians and scholars, but especially in the context of this project, as we are delving into researching various landmarks and buildings in Morningside Heights. Some of us are fortunate in that the published documents and images of our institutions pre-date 1923 and fall squarely into the public domain, while others (myself included), have to understand what constitutes fair use when it comes to newspaper articles, photographs, and other items published in 1930 or later. As such, I appreciate all of the freely available resources on Fair Use, so I’m sharing two that have been really helpful to me:

caa-fair-use-cover  infgoraphic_image



Public domain resources

Here’s a list of some of the resources we’ve learned about over the past several months.  This list will grow over time, so come back!  Feel free to add additional resources in the comments, too.

Other useful resources:

Group Meeting — January 29

New Appointments
John and I met with Alex to discuss new appointments for Design Team members as the work of this group is winding down. Anice will move to the Editorial Team. Sarah will fully focus on Development Team. Karen was away — we will consult with her on new post shortly. Due to scheduling conflicts, we discussed a new role for Nick. He will assist with staying on top of discussion regarding Omeka.

Presentation of Design
Alex presented the work of the Design Team. The team has been hard at work creating our “front page.” See previous post that outlines the process. Overall, the group was delighted with the map, logo, and title. We did not agree on the color palette. Some felt the colors too strong (mix of red and yellow). There was also concern about changing the color of the map. John noted that we are using a historical map for a history research project and we should stay true to the original color palette. There was group consensus to ask Design Team to come back with a subtler color palette.

Development Team
Because of the inclement weather and the rare closing of the university, Development Team had to postpone the migration to the newer version of Omeka. The migration was completed on February 9. We have received the go ahead to begin working on the site. We are still working out backup procedures so best advice – everyone should keep backups of the text for exhibit pages in Microsoft Word or Google Drive.

Schedule for Duration of Phase One
We will continue to meet every two weeks alternating between presentation/updates and a workshop model to provide time for all members of the group to work on their exhibits. We believe that providing time to workshop together will encourage collaborative learning.

Post Holiday, Project Team Meets, and What We Learned About Omeka

At our last group meeting on December 16, 2014, we agreed to a February 2, 2015 launch for the project. This provided what we thought would be adequate time to develop our exhibits. Before, during, and after the holidays there was a lot of activity in our Omeka site – uploading items and exhibits, reviewing options for different layouts, and discovering new questions about our metadata. The work in Omeka was helping us to identify new issues for review. Many of us were finding real benefit in working in pairs.

Unfortunately, through all this good work, we had an unwelcome discovery – a most serious bug with Omeka 2.01. We learned that if you delete one exhibit in this version of Omeka, the content of the remaining exhibits will be deleted. Recently added exhibits were gone – hours of work effort were lost.

The Project Management team had planned to meet on January 21 to draft the agenda for our next group meeting, map out our schedule for the spring semester, and to define the close of Phase One. We added the Omeka issue for further discussion.

Here is what we discussed and decided.

Launch Date: We agreed to extend our launch date to June 9. All exhibits will be completed by June 2 allowing time for editorial review.

Omeka: The Development Team is scheduled to meet on January 27 and will work to complete an upgrade to Omeka 2.02. We have requested a freeze on all activities in Omeka until the upgrade is completed. This unfortunate discovery about Omeka has taught us a few things. There is useful information to be found online through forums, discussion boards, etc. – Nick was able to pinpoint the mysterious disappearance of our exhibits by searching online. We are all reminded that backup is essential. The Development Team will routinely begin backing up our content every two weeks.

Phase One: Our project launch scheduled for June 9 will bring Phase One to a close. We will continue to meet every two weeks until launch alternating between active workshops and presentations and updates. We think the workshops will provide great opportunity for collaborative learning and the necessary time for all of us to work on our exhibits.

Phase Two: Phase Two will begin in the fall. We will continue our regular meetings and move on to new learning objectives.