6
edits
Changes
Added tiny amount of notes to Tools for Instruction break out session
Institutions that are live w/Examples
*Colorado Alliance of Research Libraries[https://www.coalliance.org/software/digital-repository/members]
**Hosts Islandora 6 repositories on Drupal 6; migrating to Drupal 7
*Florida State University ([http://fsu.digital.flvc.org])
*Grinnell [http://digital.grinnell.edu/drupal/]
Question about new installation: additional resources aside from documentation
Additional resources:
*Islandora Google Group[https://groups.google.com/forum/#!forum/islandora]* series of cookbooks with Chef for one-click installation of Islandora[https://github.com/LibraryChef/islandora]** Could use Vagrant and virtual box* New release of Islandora about to come out - expected soon
* Lyrasis is asked to review the documentation and will do sanity checks on the documentation
* Should see improvements to documentation soon
Hosted solutions available to purchase:
* Lyrasis[https://www.lyrasis.org/LYRASIS%20Digital/Pages/Repository.aspx]* DiscoveryGarden[http://discoverygarden.ca/solutions_ir.php]* Cherry Hill Co. (coming soon) [http://chillco.com]
What's the learning curve with Drupal - easier/harder than Hydra?
* Drupal 7 is easier to learn than Drupal 6
* Recommend the Using Drupal / O'Reilly Book [http://www.worldcat.org/title/using-drupal/oclc/233931612]
** Useful to understand theming / design
* Drupal may be more widely-held skill set than Ruby on Rails (in which Hydra is based)
Setup difficulty?
* Documentation for setting up Solr / Gsearch - some confusion between v. 6 & 7documentation
* Would be better for things to be more grouped together
==BIBFRAME==
Notes are based off the Tweets made by the group during the discussion:
'''Questions'''
*What will workflows will look like after Linked Data and BIBFRAME are actually pushed out?
*How to best use controlled vocabularies, including various/local controlled vocabularies, in linked data work?
*Will the protectiveness of quality by catalogers become thing of past?
'''Pros'''
*Good thing about RDF, semantic metadata structure is that is creates a good skeleton that can last through system changes.
*Talked about OpenRefine, Freebase, Linked Data/Semantic Web examples
*Shout out for the Open Metadata Registry - http://metadataregistry.org/
*RDFa allows multiple property values inline- more details than http://schema.org , starts to approach MARC richness
'''Concerns'''
*Wariness of simplicity (particularly of Dublin Core) due to the possibility of overloading elements, thus blocking interoperability with other schemas.
*There is the possible issue of every library creating their own ontologies, thus reinventing the wheel.
*Discussion of how long-term cataloging employees will handle this linked data 'revolution', how to best oversee these changes with catalogers dragging their feet.
==Archivespace==
Participants:
* Mike Hagedon; interests: [http://code.library.arizona.edu/gots Guide on the Side], LTI, LMS integration, subject/course guides
* Michael Berkowski; interests [http://libdata.sourceforge.net/ LibData library subject/course guide authoring], open source
* Christina Salazar;see Mike Hagedon, plus or minus Guide on the Side (not that there's anything wrong with it, but CSUCI cannot use it)
*
(Horrible) Notes from session:First: the group and the conversation was very diverse so here tis for what it's worth:We know we need to automate some of the information literacy tasksSome of us talked about how their institution was using Guide on the SideThere was also a bit of conversation about *other* types of IL instruction tools (like clickers for voting/in class participation,(board) games, mobile/e-mail app that allows for voting)And a conversation about how libraries are now pressured to tie in IL (or any instruction) to retention and how we can track those outcomes without losing privacy ==Code4lib Conference Documentation== We discussed the ways in which the lack of historical data make proposing to host the conference difficult. Code4libbers must convince their employer to take on financial responsibility. This does not mean the host pays. In fact, each conference has had a surplus. But a corporate institution is needed to sign the contracts with the venues and services used by the conference. Employers need convincing that the event will not be a huge cost nor a burden on the business office. To convince the administrators, a historical record of past conferences would be immensely helpful. We discussed several data points that would be useful. Some of these include*expected and final budgets* total attendance* hotel room reservation block size and % of expected size actually used* food costs, food expectations and % of food actually consumed* etc. We plan to begin storing these kinds of data on the code4lib wiki for future planners to use. Some other documentation that we also plan to add to the wiki:* Conference Planning Committee Post-mortem (Raleigh group already started this trend with the "Lessons Learned" post)* explanation of what it's like to work with a 3rd party event planner (Concentra), such as:** how money flows between attendees, sponsors, host, awardees, and concentra** what are the benefits of working with a 3rd party planner?* examples of MOUs between multiple host institutions Some action items:* finish documenting this year's conference (Tim et al.)* attempt to collect historical budgets if they still exist (Josh & Rosy)* organize existing data on the wiki (?) ==VuFind Update==Sorry for the delay We had a lovely gathering of VuFind veterans with a few new comers stopping by to hear what VuFind is all about. New comer and VuFind developer Chris Hallberg headed the meeting, a strong term for sitting there and listening to all the exciting news from our awesome collaborators. We started with some spoilers from [http://code4lib.org/conference/2014/bauder Julia Bauder's Visualization Talk], a feature of VuFind in active development. Then we went over the short-term plans for VuFind, looking at our GitHub's pull requests, heard an update from Tom on data normalization. John Sarnowski of the ResCarta Foundation came by to see how VuFind has change since he looked at it a few years ago as the front of his project. Looking forward to a possible collaboration here. Joe talked about his excitement over console tools and his frustration with licensing, hoping to see these in the VuFind core soon! We heard about the OLE timeline and wrapped with Julia talking about her success with ebsco. Thanks for coming by! See you all in Portland!
