Code4Lib - User contributions [en]

NECode4lib 2015 Home

2015-04-03T16:20:47Z

AndrewBattista: /* Presentations */

Please join us Friday, May 29, at Boston, MA for the NECode4Lib 2015 conference. This informal conference will feature short lightning talks, longer presentations, and breakout discussion sessions covering technology in libraries, archives and museums in the New England.

===Location===
NECode4Lib meeting will be hosted by MIT.

'''When''' - Friday, May 29th

'''Where''' - MIT, [https://whereis.mit.edu/?go=34 Building 34], room 401A (Grier Room A).

'''Registration Cost''' - Free!

'''Registration Link''' - http://necode4lib2015.eventbrite.com

'''Planning Committee''' - Matt Bernhardt (matt.j.bernhardt@gmail.com), Jeremy Prevost (jprevost@mit.edu), Joe Montibello (joseph.montibello@dartmouth.edu), Matt Sherman (matt.r.sherman@gmail.com), Abigail Baines (abaines@hampshire.edu), Jennifer Eustis (Jennifer.Eustis@lib.uconn.edu), Sharon Clapp (sclapp@ccsu.edu), Andromeda Yelton (andromeda.yelton@gmail.com), David Mayo (pobocks@gmail.com), Maura Carbone (mauraa@brandeis.edu), Christina Harlow (cmh2166@columbia.edu)

===Logistics===
====Transportation====
* MIT can be reached by car, train, or bus.
* If you are going to drive all the way to campus, MIT's parking information can be found here: http://web.mit.edu/facilities/transportation/parking/visitors/public_parking.html
* Another popular option is to take the MBTA red line to campus, and get off at the Kendall/MIT stop. From there, it is a relatively short walk to building 34. On the map link above, the Kendall/MIT stop is just outside building E38. Parking is also available at the terminal stations on the red line - the easiest to reach if you are coming from outside Boston is probably Alewife in Arlington.
* If you're arriving via bus, there are a number of lines that run by campus. Consult the MBTA website (or Google Maps) for more information.
* We are also looking into helping arrange carpooling. More information to come.

====Hotels====
* If you're looking for a hotel room the night before / after, there are two hotels near campus - the [http://www.kendallhotel.com/ Kendall Hotel] and [http://www.marriott.com/hotels/travel/boscb-boston-marriott-cambridge/ Marriott Hotel], both on Main Street. There is no block of rooms, however, so please make whatever arrangements make sense for you.

====Code of Conduct====
NECode4Lib is dedicated to a harassment-free conference experience for everyone. We are using the Code4Lib 2015 Conference Code of Conduct that can be found at: http://code4lib.org/content/2015-code-conduct

==Programming Sign-up==

Share what you are working on or talk about a topic you are interested in! We would also love to ideas for some roundtable discussions. Add your name and a description below.

If you do not have a Wiki account, you can Contact Ryan Wick (ryanwick@gmail.com) with your preferred username to set up a Code4Lib wiki account. Or, if you prefer to not have an account or muck about in the wiki yourself, you may contact Jeremy Prevost (jprevost@mit.edu) to have your Presentation/Lightning Talk/Discussion Topic added below for you.

===Presentations===
15-20 minutes talks.
# [http://static.digitalcommonwealth.org/talks/2015_code4libNE/Metadata.pdf Metadata Enrichment and Maps] (Boston Public Library)
# Usability, Digital Content Strategy & LibGuides (Sharon Clapp, Central Connecticut State University)
# Using Omeka to Receive Data from Researchers and Author Metadata (Stephen Balogh and Andrew Battista, New York University)

===Lightning Talks===
A Lightning Talk is a fast-paced, 5-minute talk on the topic of your choice.
# [http://static.digitalcommonwealth.org/talks/2015_code4libNE/VLR.pdf Virtual Local Repositories] (Boston Public Library)
# Using a script to reclassify a video collection (Steve McDonald / Tufts University)

===Discussion Topics===
List some topics you are interested in talking to others during breakout time.
# 3D Printing and the Law: A raucous uninformed melee where opinionated librarians discuss a tropic they do not understand because it has not been settled yet (Edward Iglesias, Central Connecticut State University)
#

==Schedule==

===Friday, May 29===
To be announced

==Registration==

You can register here: http://necode4lib2015.eventbrite.com

'''Registration is free.''' We have tables and chairs for about 60 people. If you signed up and are unable to attend please contact us, so that we can make room for others.

==Mailing list==

NECode4Lib has low-traffic [https://groups.google.com/forum/#!forum/code4lib-ne NECode4Lib Google Group]. Consider subscribing.

2015 Preconference Proposals

2014-11-02T21:20:50Z

AndrewBattista: /* A hand's on introduction to GeoBlacklight */

== Instructions ==
Thank you for considering proposing a pre-conference! Here are a few details:

* We will be taking pre-conference proposals until '''November 7, 2014'''
* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]
* If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)
* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu
* '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions
* Please use the template for proposals provided in the pre-formatted block below

=== Proposal formatting guidelines: ===

<pre>

=== Preconference Title: ===

One of:
'''"Full Day"'''
'''"Half Day [Morning]"'''
'''"Half Day [Afternoon]"'''

* Facilitator's name, affiliation, and email address
* Second facilitator's name, affiliation, email address, if second speaker

Abstract

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#
#
#

</pre>

== Pre-conference Proposals ==

Post your ideas here!

=== Delivering and Preserving GIS Data ===

'''Half Day [Morning]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista

=== A hand's on introduction to GeoBlacklight ===

'''Half Day [Afternoon]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista

===RailsBridge: Intro to programming in Ruby on Rails===
'''"Half-Day" [morning]'''
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu
* Additional instructors welcome

Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.

RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
#Vicky Steeves
#

=== Replace yourself with a painfully complex bash script...or try Ansible ===
'''Half Day [Morning]'''

* Chad Nelson, chad dot nelson @ lyrasis dot org
* Blake Carver, Blake dot carver @lyrasis dot org

Abstract:

[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
#
#
#

=== Intro to Docker ===
'''Half Day [Whenever]'''

* John Fink, McMaster University, john dot fink at gmail dot com
* Francis Kayiwa, Kayiwa Consulting , francis dot kayiwa at gmail dot com

Abstract:

[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.

''Interested in Attending''

1. Jim Hahn

=== Code Retreat ===
'''Full Day'''

* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu
* Additional facilitators welcome; Especially if you have CodeRetreat experience.

Abstract:

"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]

''Interested in Attending''

=== Presentations workshop ===

'''"Half Day [Afternoon]"''' (but could be expanded based on interest)

* Chris Beer, Stanford University, cabeer@stanford.edu
* Additional facilitators welcome.

This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#Vicky Steeves
#
#

=== Dive into Hydra ===

One of:
'''"Half Day [Afternoon]"'''

* Justin Coyne, Data Curation Experts, justin@curationexperts.com
* Bess Sadler, Stanford University, bess@stanford.edu

Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
#
#

=== code4lib/Write The Docs barcamp ===

One of:
'''"Full Day"''', with options for jumping in for half a day

* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu
* Write the Docs contacts: TBA

Abstract

''Placeholder for now - more information will be available before the proposal deadline''. More information about Write the Docs at http://docs.writethedocs.org/

There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

'''Full day'''
#
#
#

'''Morning'''
#
#
#

'''Afternoon'''
#
#
#

=== Linked Data Workshop ===

One of:
'''"Half Day [morning]"'''

* Karen Estlund, University of Oregon, kestlund@uoregon.edu
* Tom Johnson, DPLA, tom@dp.la

Abstract:

Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Logan Cox
#
#

=== Archivematica for users and developers ===

One of:
'''"Full Day"'''

* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com

Abstract:

This is a workshop intended for both end-users of Archivematica (librarians, archivists, systems administrators) as well as developers who are interested in Archivematica feature development, or use of Archivematica back-end features for integration into other projects.

In the morning, the end-users will meet with Sarah for a hands-on Archivematica training session. We will discuss processing configurations, use cases, and installation/hosting options for Archivematica. We will also demonstrate DIP upload to Archivematica's access system, AtoM. During this time, developers will meet with Justin and other Artefactual developers for a hackaton style session focusing on Archivematica development and integration.

For the afternoon, we plan to bring the two groups together to discuss, share use cases, and have breakout sessions focused on specific topics that arose from the morning and afternoon sessions.

When signing up, please indicate if you are an end-user or a developer.

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#
#
#

=== Fail4Lib 2015 ===
'''Half Day [TBD, probably afternoon]'''

Contacts:
* Andreas Orphanides, akorphan (at) ncsu.edu
* Jason Casden, jmcasden (at) ncsu.edu

Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.

This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)

The schedule may include the following:

* Case studies. Avoid our own mistakes by bearing witness to the failures of others.
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.

''Interested in attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#
#
#

=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===

One of:
'''"Half Day [Morning]"'''

* Terry Brady, Georgetown University Library, twb27@georgetown.edu

Abstract

The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.

* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating counter compliant reports for the Electronic Resources department
* Preparing ingest packages for the Digital Services department
* Validating checksums for the Preservation department

This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.

The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#
#
#

[[Category:Code4Lib2015]]

2015 Preconference Proposals

2014-11-02T21:20:04Z

AndrewBattista: /* Delivering and Preserving GIS Data */

== Instructions ==
Thank you for considering proposing a pre-conference! Here are a few details:

* We will be taking pre-conference proposals until '''November 7, 2014'''
* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]
* If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)
* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu
* '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions
* Please use the template for proposals provided in the pre-formatted block below

=== Proposal formatting guidelines: ===

<pre>

=== Preconference Title: ===

One of:
'''"Full Day"'''
'''"Half Day [Morning]"'''
'''"Half Day [Afternoon]"'''

* Facilitator's name, affiliation, and email address
* Second facilitator's name, affiliation, email address, if second speaker

Abstract

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#
#
#

</pre>

== Pre-conference Proposals ==

Post your ideas here!

=== Delivering and Preserving GIS Data ===

'''Half Day [Morning]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
# Andrew Battista

=== A hand's on introduction to GeoBlacklight ===

'''Half Day [Afternoon]'''

* Darren Hardy, Stanford University, drh@stanford.edu
* Jack Reed, Stanford University, pjreed@stanford.edu

GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop "Delivering and Preserving GIS Data".

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# [[User:Ssimpkin|Sarah Simpkin]]
# Vicky Steeves
#

===RailsBridge: Intro to programming in Ruby on Rails===
'''"Half-Day" [morning]'''
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu
* Additional instructors welcome

Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.

RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
#Vicky Steeves
#

=== Replace yourself with a painfully complex bash script...or try Ansible ===
'''Half Day [Morning]'''

* Chad Nelson, chad dot nelson @ lyrasis dot org
* Blake Carver, Blake dot carver @lyrasis dot org

Abstract:

[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
#
#
#

=== Intro to Docker ===
'''Half Day [Whenever]'''

* John Fink, McMaster University, john dot fink at gmail dot com
* Francis Kayiwa, Kayiwa Consulting , francis dot kayiwa at gmail dot com

Abstract:

[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.

''Interested in Attending''

1. Jim Hahn

=== Code Retreat ===
'''Full Day'''

* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu
* Additional facilitators welcome; Especially if you have CodeRetreat experience.

Abstract:

"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time." [http://coderetreat.org/about About Code Retreat]

''Interested in Attending''

=== Presentations workshop ===

'''"Half Day [Afternoon]"''' (but could be expanded based on interest)

* Chris Beer, Stanford University, cabeer@stanford.edu
* Additional facilitators welcome.

This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#Vicky Steeves
#
#

=== Dive into Hydra ===

One of:
'''"Half Day [Afternoon]"'''

* Justin Coyne, Data Curation Experts, justin@curationexperts.com
* Bess Sadler, Stanford University, bess@stanford.edu

Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend "RailsBridge" prior to this workshop.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Maura Carbone
#
#

=== code4lib/Write The Docs barcamp ===

One of:
'''"Full Day"''', with options for jumping in for half a day

* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu
* Write the Docs contacts: TBA

Abstract

''Placeholder for now - more information will be available before the proposal deadline''. More information about Write the Docs at http://docs.writethedocs.org/

There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

'''Full day'''
#
#
#

'''Morning'''
#
#
#

'''Afternoon'''
#
#
#

=== Linked Data Workshop ===

One of:
'''"Half Day [morning]"'''

* Karen Estlund, University of Oregon, kestlund@uoregon.edu
* Tom Johnson, DPLA, tom@dp.la

Abstract:

Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Logan Cox
#
#

=== Archivematica for users and developers ===

One of:
'''"Full Day"'''

* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com

Abstract:

This is a workshop intended for both end-users of Archivematica (librarians, archivists, systems administrators) as well as developers who are interested in Archivematica feature development, or use of Archivematica back-end features for integration into other projects.

In the morning, the end-users will meet with Sarah for a hands-on Archivematica training session. We will discuss processing configurations, use cases, and installation/hosting options for Archivematica. We will also demonstrate DIP upload to Archivematica's access system, AtoM. During this time, developers will meet with Justin and other Artefactual developers for a hackaton style session focusing on Archivematica development and integration.

For the afternoon, we plan to bring the two groups together to discuss, share use cases, and have breakout sessions focused on specific topics that arose from the morning and afternoon sessions.

When signing up, please indicate if you are an end-user or a developer.

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#
#
#

=== Fail4Lib 2015 ===
'''Half Day [TBD, probably afternoon]'''

Contacts:
* Andreas Orphanides, akorphan (at) ncsu.edu
* Jason Casden, jmcasden (at) ncsu.edu

Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.

This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)

The schedule may include the following:

* Case studies. Avoid our own mistakes by bearing witness to the failures of others.
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.

''Interested in attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#
#
#

=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===

One of:
'''"Half Day [Morning]"'''

* Terry Brady, Georgetown University Library, twb27@georgetown.edu

Abstract

The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.

* Analyzing Marc Records for the Cataloging department
* Transferring ILS invoices for the University Account System for the Acquisitions department
* Delivering patron fines to the Bursar’s office for the Access Service department
* Summarizing student worker timesheet data for the Finance department
* Validating counter compliant reports for the Electronic Resources department
* Preparing ingest packages for the Digital Services department
* Validating checksums for the Preservation department

This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.

The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#
#
#

[[Category:Code4Lib2015]]