https://wiki.code4lib.org/api.php?action=feedcontributions&user=JulietHardesty&feedformat=atomCode4Lib - User contributions [en]2024-03-28T17:45:14ZUser contributionsMediaWiki 1.26.2https://wiki.code4lib.org/index.php?title=2015_Social_Activities&diff=426992015 Social Activities2015-02-10T00:27:57Z<p>JulietHardesty: /* Karaoke, Wednesday or Thursday (February 11 or 12) */</p>
<hr />
<div>The Social Activities Group is working on several events and social opportunities for after conference hours. We will be adding more events as they come along. Watch this page!<br />
<br />
Also, if you find a cool event to go to, and want to share the wealth with others, feel free to add the event to the page. :)<br />
<br />
== Planned Events ==<br />
<br />
=== Newcomer Dinner, Monday, February 9th ===<br />
<br />
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating <strike>discussions about</strike> demonstrations of the many uses of <strike>bacon</strike> <strike>XML</strike> <strike>EZProxy</strike> LibGuides alternatives.<br />
<br />
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!<br />
<br />
'''Plans'''<br />
* When: Monday, February 9th<br />
* Time: 6 PM (ish) or whenever you can get your group together<br />
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]<br />
<br />
''Guidelines:''<br />
*Max of '''6''' per group<br />
**Please, no waitlisting<br />
**Some restaurants can hold multiple groups of six. It is up to you to investigate the venue to see if this is possible.<br />
*ID yourselves so we can get a good mix of new people and veterans in each group<br />
**New folks - n<br />
**c4l vets - v<br />
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')<br />
**Leader duties<br />
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library tech type folks<br />
***Herd folks from hotel to restaurant (know where you're going!)<br />
*See a restaurant that's not listed? Feel free to add one, '''but please make sure that it is open that Monday evening.'''<br />
<br />
'''[https://docs.google.com/document/d/1rqfdRYxCZe7UrelaULzk8jpjavGGi2PGHUN1hPX7aNI/edit?usp=sharing Restaurant list and dinner sign ups posted on Google Docs]'''<br />
<br />
=== LibTechWomen Meetup, Tuesday February 10th ===<br />
<br />
When: Tuesday, February 10th - 5:30pm - 7pm<br />
<br />
Where: The Veggie Grill -- 508 SW Taylor St. (One block from the hotel.) [http://veggiegrill.com/docs/vg-web-menu.pdf Menu is here.]<br />
<br />
An informal meetup for women and their friends in library technology. No need to RSVP. I'll try to make sure there's an announcement ahead of time, and will be in the hotel lobby at 5:15 to point people in the right direction.<br />
<br />
Questions? [mailto:sarahsimpkin@gmail.com Sarah Simpkin]<br />
<br />
=== Craft Brew Drinkup, Tuesday February 10th ===<br />
<br />
When: Tuesday, February 10th - 7pm - 10pm (ish)<br />
<br />
Where: eBay Offices - 1400 SW 5th Ave, Portland, OR 97201<br />
<br />
The Craft Brew Drinkup at Code4lib 2015 is all about sharing and enjoying good beer with fellow conference attendees. The idea is to bring bottles of your favorite beers or non-alcoholic drinks.<br />
<br />
While you're not obligated to bring local brews from wherever you're from, participants are definitely encouraged to bring brews that you think is special and might be somewhat hard for others outside your area to find. Homebrew is especially welcome as are non-alcoholic beverages. Hot water will be provided for those who want to bring tea blends.<br />
<br />
This year, eBay has agreed to host the Code4Lib Drinkup at their offices in downtown Portland, a 6 block walk from the conference hotel. Attendees should expect to bring something to share, either drinks or snacks. Cups will be provided by the host.<br />
<br />
'''Please Note''': The space must be cleaned up and all folks gone no later than 11pm. <br />
<br />
'''[https://www.eventbrite.com/e/code4lib-2015-tickets-14504558525 Space is limited to the first 200 people who register for the event!]'''<br />
<br />
Please sign up on the [[2015 Craft Drinkup|Craft Drinkup wiki page]] to share the brews and bottles you're thinking of bringing along and special requests can be made, but don't expect that your wishes will be granted.<br />
<br />
=== Run4Lib, Monday-Wednesday, Feb 9-11th ===<br />
<br />
When: Monday-Wednesday (February 9th, 10th & 11th) '''leaving at 6:30AM'''<br />
<br />
Where: Meet in Conf Hotel Lobby, see routes below.<br />
<br />
Running Distance: 5k-ish<br />
<br />
Run4Lib is about providing an easy opportunity to get your run on with other runners. We decided to alternate between two routes, both similar in distance. <br />
<br />
'''Mon/Wed route''':[http://www.mapmyrun.com/routes/view/616875918 MapMyRun Run4Lib Mon/Wed Route] <br />
<br />
'''Tues route''':[http://www.mapmyrun.com/routes/view/616883656 MapMyRun Run4Lib Tues Route]<br />
<br />
Questions? : [mailto:wwatkins@stlawu.edu Whitni Watkins]<br />
<br />
=== OCLC Developer House Meetup, Wednesday February 11th ===<br />
<br />
When: Wednesday, Febraury 11th 5:30pm – 7:00pm<br />
<br />
Where: Meet in the hotel lobby at 5:30 and figure out where we want to go (or stay?) for a drink, depending on the will of the group and the whim of the weather.<br />
<br />
An informal meetup for alumni and anyone interested in OCLC’s Developer House event. No need to RSVP. <br />
<br />
Drop me a note if you have any questions: [mailto:hostetls@oclc.org Shelley Hostetler]<br />
<br />
=== Game Night, Wednesday February 11 === <br />
<br />
Games sign up on the [[2015_Game_Night|Game Night page]]<br />
<br /><br />
Where: ballroom/meeting room(s) at the Hilton. <br />
<br /><br />
When: February 11, 6pm<br />
<br />
== Social Map - Places of Interest==<br />
<br />
== Ideas ==<br />
<br />
''Want to see a specific event? Add your own ideas here...''<br />
<br />
=== Karaoke, Wednesday or Thursday (February 11 or 12) ===<br />
<br />
Interested in singing your face off, and/or enjoying others doing the same?<br />
<br />
Sign up below and contact @anarchivist or @mbklein on Twitter or IRC to express your Wednesday/Thursday preference and we can start talking about venues!<br />
<br />
# Michael Klein (@mbklein; either Wednesday or Thursday)<br />
# Mark Matienzo (@anarchivist; either Wednesday or Thursday)<br />
# Whitni Watkins (@nimblelibrarian; Wednesday)<br />
# Julie Hardesty (@jlhardes; mostly Wednesday but Thursday OK too)<br />
<br />
== Local Food ==<br />
* [http://www.foodcartsportland.com/maps/ Portland Food Carts] - Several in Pioneer Courthouse Square (2 blocks away from conference) and a huge pod off SW 10th & Alder. "Pods" are locations with multiple food carts and a good choice for a large group with different dietary needs, preferences, and budgets. Most meals are under $10. [https://www.google.com/maps/d/viewer?msa=0&mid=zBwrQkvFyvi8.k7T1OA_J6anE Pod Map]. It's rare to find a place to sit, so once you've got your meal check your map for the nearest green square in downtown. <br />
<br />
=== Restaurants ===<br />
<br />
=== Donuts ===<br />
* [http://www.bluestardonuts.com/ Blue Star Donuts] - Awesome donuts.<br />
<br />
=== Desserts ===<br />
* [http://euphoriachocolate.com/ Euphoria Chocolate] - Sold by many gift shops, including the Made In Oregon at PDX Airport. Local chocolate, good stuff. <br />
* [http://www.moonstruckchocolate.com/ Moonstruck Chocolate Company] - Local chocolate. Locations off SW 6th & Alder; NW 23rd between Hoyt and Glisan. NW 23rd also has a number of shops, bars, restaurants, and is good for people watching. Accessible by the Portland Streetcar.<br />
<br />
=== Coffee ===<br />
* [http://purringtonscatlounge.com/home/p484/ Purringtons Cat Lounge] - Cat cafe. Reservations required (hour slots, $8/person)<br />
<br />
== Local Drinks ==<br />
<br />
=== Bars ===<br />
<br />
=== Breweries ===<br />
* [http://basecampbrewingco.com/ Base Camp Brewing Co.]<br />
* [http://www.bridgeportbrew.com/home Bridgeport Brewing]<br />
* [http://www.burnsidebrewco.com/ Burnside Brewing Co.]<br />
* [http://www.cascadebrewingbarrelhouse.com/ Cascade Brewing Barrel House]<br />
* [http://www.deschutesbrewery.com/locations/portland Deschutes Brewery and Pub]<br />
* [http://hairofthedog.com/ Hair of the Dog Brewing Co.]<br />
* [http://www.rockbottom.com/ Rock Bottom Restaurant and Brewery]<br />
* [http://www.rogue.com/roguemeetinghalls/ Rogue Distillery and Pub]<br />
* [http://www.d2m.com/Tugwebsite/ Tugboat Brewing Company]<br />
* [http://widmerbrothers.com/ Widmer Brothers Brewing]<br />
<br />
The breweries listed above are a few blocks' walk from [http://trimet.org/index.htm Tri-Met MAX] or the [http://www.portlandstreetcar.org/node/4 Portland Streetcar] lines- which are easily accessible from the host hotel.<br />
<br />
=== Bottle Shops and Taprooms ===<br />
* [http://www.baileystaproom.com/ Bailey's Taproom] (Downtown)<br />
* [http://www.johnsmarketplace.com/ John's] (SW)<br />
* [http://www.belmont-station.com/ Belmont Station] (SE)<br />
* [http://bazipdx.com/ Bazi Bierbrasserie] (SE)<br />
* [http://thebeermongers.com/ Beer Mongers] (SE)<br />
* [http://www.apexbar.com/ APEX Bar] (SE)<br />
* [http://www.saraveza.com/ Saraveza] (N)<br />
<br />
== Portland Events ==<br />
<br />
=== Saturday and Sunday, February 7 and 8 ===<br />
<br />
* [https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;4c26a341.1412 PBCore RDF ontology hackathon]<br />
* [[PBCore RDF Hackathon]]<br />
<br />
=== Monday, February 9 ===<br />
* [http://tickets.orsymphony.org/single/eventDetail.aspx?p=2523 Carmina Burana], 8:00 pm, Arlene Schnitzer Concert Hall<br />
* [http://www.powells.com/events/6382 Nick Hornby in Conversation with Cheryl Strayed], 7:00 pm, Powell's Books at Cedar Hills Crossing<br />
<br />
=== Tuesday, February 10 ===<br />
* [http://www.portland5.com/keller-auditorium/events/carmen Carmen], 7:30 pm, Keller Auditorium<br />
<br />
=== Wednesday, February 11 ===<br />
<br />
* [http://www.portland5.com/arlene-schnitzer-concert-hall/events/nederlands-dans-theater-2 Nederlands Dans Theater at Arlene Schnitzer Concert Hall], 7:30 pm; Already purchased a block of tickets for those who indicated interest early on. Anyone else buying a ticket late in the game and interested in joining us before the show for a bite to eat contact Andy Mardesich <Andy.Mardesich at ucop.edu>.<br />
<br />
=== Thursday, February 12 ===<br />
* [http://www.portland5.com/keller-auditorium/events/carmen Carmen], 7:30 pm, Keller Auditorium<br />
* [http://www.mississippistudios.com/event/724141-catfish-bottlemen-portland/ Catfish and The Bottlemen], 9:00 pm, Mississippi Studios<br />
* [http://thirdangle.org/2014-15-season/mozart-revisted/ Mozart, Revisited], 7:30 pm, Zoomtopia<br />
<br />
=== All days ===<br />
* [http://www.nwfilm.org/festivals/piff/ Portland International Film Festival]<br />
* [http://portlandartmuseum.org/exhibitions/masterworks-portland-el-greco/ Masterworks | Portland: El Greco], Portland Art Museum<br />
<br />
==Getting Around==<br />
<br />
<br />
[[Category:Code4Lib2015]]</div>JulietHardestyhttps://wiki.code4lib.org/index.php?title=2015_Craft_Drinkup&diff=426612015 Craft Drinkup2015-02-07T01:37:25Z<p>JulietHardesty: /* Signup */</p>
<hr />
<div>When: Tuesday, February 10th - 7pm - 10pm (ish)<br />
<br />
Where: eBay Offices - 1400 SW 5th Ave, Portland, OR 97201<br />
<br />
The Craft Brew Drinkup at Code4lib 2015 is all about sharing and enjoying good beer, soda, and other drinks with fellow conference attendees. The idea is to bring bottles of your favorite beers or non-alcoholic drinks.<br />
<br />
While you're not obligated to bring local brews from wherever you're from, participants are definitely encouraged to bring brews that you think is special and might be somewhat hard for others outside your area to find. Homebrew is especially welcome as are non-alcoholic beverages. There will be hot water available for those who want to bring in their tea blends as well!<br />
<br />
This year, eBay has agreed to host the Code4Lib Drinkup at their offices in downtown Portland, a 6 block walk from the conference hotel. Attendees should expect to bring something to share, either drinks or snacks.<br />
<br />
Please Note: The space must be cleaned up and all folks gone no later than 11pm.<br />
<br />
Space is limited to the first 200 people who register.<br />
<br />
== Signup ==<br />
Please sign up below to share the brews and bottles you're thinking of bringing along and make any special requests (but don't expect that your wishes will be granted).<br />
<br />
{| class="wikitable"<br />
|-<br />
! Name !! Bringing !! Wanting<br />
|-<br />
| Esmé Cowles || Cigar City 110K+OT Batch #7 or Marshal Zhukov, Homebrew Imperial Saison || Any saison or sour!<br />
|-<br />
| Francis Kayiwa || (at least the following) Boulevard Quad Bourbon Barrel, Weyebacher Althea || <strike> Scotty Karate </strike> barleywines and any porters<br />
|-<br />
| Becky Yoose || [http://www.sprecherbrewery.com/store/details.php?prodId=164&category=7 N/A Soda from Sprecher Brewery], [http://www.sprecherbrewery.com/store/cw2/assets/product_huge/F_Popcorn_RB-Large.jpg Sprecher Root beer float flavored popcorn], selection of Finnish teas|| N/A drinks :c) Melon soda (not Ramune) greatly appreciated<br />
|-<br />
| Tania Fersenheim || Something from Pretty Things || ...<br />
|-<br />
| Ben Armintor || Stuff from NY that Matienzo & Harlow don't bring || Farmhouse beers, tasty low-ABV beers<br />
|-<br />
| Justin Coyne || Surly Darkness? || ...<br />
|-<br />
| Whitni Watkins|| Non-alcoholic Ginger beer options: at least Reed's & Saranac Lake. Potentially one other local brewed Ginger beer. If you have a request from Upstate NY HMU whitni.watkins at gmail (alcoholic and N/A) || Ginger Beers & Ales specifically: Fentimans, River City, Bundaberg and Blenheim Red Hot<br />
|-<br />
| Sarah Simpkin || Accepting requests for tasty Quebecois beers -- [https://brouehaha.com/en/nos-bieres/ see this list for breweries]. Otherwise will grab a small selection. Contact me at sarahsimpkin at gmail.com :-) || Hefeweizen-y beers appreciated<br />
|- <br />
|Coral Sheldon-Hess || Bourbon-barrel aged assam tea (1oz), Whiskey Cinnamon Snap rooibos tea (~1.5 oz), and Brandy Oolong tea (.5 oz), plus 1-2 reusable brewing devices || Ginger ale, anything bourbony, anything imperial and stoutish<br />
|-<br />
| mx matienzo || Transmitter Brewing B2, De Molen SSS Triple Stout 2011, perhaps a couple southern Upstate NY ciders, ...? || Saisons, sours and gueuzes, weird ciders, other horseblankety stuff<br />
|-<br />
| David Bass || TBT || ...<br />
|-<br />
| Christina Harlow || Probably something from Grimm...? Who knows, stuff from Brooklyn & stuff from Eastern Tenn/Western NC (Highland brewery?) || English bitter type stuff or stouts<br />
|-<br />
| Tom Johnson || Portland/Willamette Valley things you might not find downtown. Heater Allen, Pfriem, The Commons, Block 15, and/or Crux Fermentation. Homebrew (Old Ale brewed in October and racked over the winter).|| ...<br />
|-<br />
| Ranti Junus || Non-alcoholic something and probably some pu-erh tea. || N/A drinks<br />
|-<br />
| Chad Nelson || Weyerbacher Riserva, Dogfish Head Miles Davis Bitches' Brew, Allagash FOUR, Neshaminator || miller lite<br />
|-<br />
| Maura Carbone || Something from Mass or CT or both, not a beer drinker, so I'll see what I find! || N/A drinks or a hard cider or two<br />
|-<br />
| Sandy Rodriguez || Boulevard Tank 7; perhaps something from [http://mothersbrewing.com/craft-beers/our-beers/ Mother's Brewing] || scotch ales, brown ales, stouts, saisons<br />
|-<br />
| Dominic Bordelon || Louisiana beers besides Abita; probably LA 31 and Covington, maybe a Nola or two || ...<br />
|-<br />
| Tara Robertson || Vancouver (BC, Canada) beer || non-alcoholic ginger beer<br />
|-<br />
|-<br />
| Matt Critchlow || I'll try to hunt down some new San Diego offerings (there are many) || homebrew, belgians<br />
|-<br />
| Jeremy Nelson || Left Hand's Wake Up the Dead Imperial Stout or other Colorado Stout/Porter || stouts and porters<br />
|-<br />
|Heather Pitts||Mid-Willamette Valley stuff in growlers/growlettes (depends on what's on tap), some bottles too||sours, stouts, porters, ginger ciders or meads<br />
|-<br />
|Jeremy Floyd||A selection from [http://www.greatbasinbrewingco.com/site/brews/in-bottles/ Great Basin Brewing Co.] in Northern Nevada||saisons, sours, anything unique<br />
|-<br />
|Misty De Meo||A bottle from Vancouver's [http://artisansakemaker.com/ Artisan SakeMaker]||stouts, porters, any dark beers really<br />
|-<br />
|Jon Earley || From Michigan, [http://foundersbrewing.com/our-beer/dirty-bastard/ Founders Dirty Bastard] and [http://www.greenbushbrewing.com/gb_splash.php?r=http://www.greenbushbrewing.com/beers/anger.htm Greenbush Anger] || ginger ale, anything unique<br />
|-<br />
|Eric Frierson||Austin's own [http://www.beeradvocate.com/beer/profile/383/1062/ Live Oak HefeWeizen], provided TSA doesn't confiscate the growler in my checked luggage||scottish ales, tripels would be nice.<br />
|-<br />
|Andrew Myers||[http://spencerbrewery.com/beer/ Spencer trappist ale], and maybe something from [http://www.aeronautbrewing.com/ the new place down the street]||hops<br />
|-<br />
|Bobbi Fox||home-baked crisp rosemary flatbread crackers (we all need *something* to sop up the beer :-)||porters, meads<br />
|-<br />
|Megan Kudzia || From Michigan, Dark Horse Scotty Karate (hopefully, depends on if I can get it) and/or something else unusual from Dark Horse. And pretzels. || porters, stouts, darkish ales :)<br />
|-<br />
|Julie Hardesty || Rogue Dead Guy Ale (I know, not Indiana but it's tasty) || ales, meads, grogs (arr!)<br />
|-<br />
|}</div>JulietHardestyhttps://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=426382015 Preconference Proposals2015-02-05T13:43:28Z<p>JulietHardesty: /* Code4Arc */</p>
<hr />
<div>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. <br />
<br />
== Preconference Schedule (draft) ==<br />
There may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib. See below for further information on each session.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)<br />
|-<br />
| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (9: Needs: projector, internet connection, and power strips) || Intro to Git & possibly beyond (40: Needs: projector/screen)<br />
|-<br />
| '''Parlor B (30)''' || Code Retreat (18: Needs whiteboard, dry-erase markers, projector) || Code Retreat (15: Needs whiteboard, dry-erase markers, projector) <br />
|-<br />
| '''Parlor C (30)''' || [[code4lib/Write The Docs barcamp]] (8: Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || [[code4lib/Write The Docs barcamp]] (5)<br />
|-<br />
| '''Grand Ballroom''' I (320) || '''CANCELLED''': [UXtravaganza] || Presentations workshop (1: Needs: projector/screen)<br />
|-<br />
| '''Grand Ballroom''' II (200) || Visualizing Library Data (60: Needs: projector) || DPLA API Workshop (34: Bringing their own projector)<br />
|-<br />
| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (1: Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (13: Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)<br />
|-<br />
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (25: Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (5: Needs: Projector)<br />
|-<br />
| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (20: Need projector) || Intro to Docker (52)<br />
|-<br />
| '''Studio (35)''' || Linked Data Workshop (56: Bringing their own projector) || Dive into Hydra (29: Needs: projector/screen; Requests: classroom style seating)<br />
|-<br />
| '''Directors (35)''' || Code4Arc (20: Needs: projector) || Code4Arc (18: Needs: projector)<br />
|-<br />
| '''Council (45)''' || Delivering and Preserving GIS Data (10: Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (19: Needs: projector, outlets; Requests: list of attendees)<br />
|}<br />
<br />
== Pre-conferences ==<br />
===MORNING:===<br />
==== Coding Custom Solutions for Every Department in the Library with File Analyzer ====<br />
Morning, Galleria I<br />
* Terry Brady, Georgetown University Library, twb27@georgetown.edu<br />
<br />
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.<br />
* Analyzing Marc Records for the Cataloging department<br />
* Transferring ILS invoices for the University Account System for the Acquisitions department <br />
* Delivering patron fines to the Bursar’s office for the Access Service department<br />
* Summarizing student worker timesheet data for the Finance department<br />
* Validating counter compliant reports for the Electronic Resources department<br />
* Preparing ingest packages for the Digital Services department<br />
* Validating checksums for the Preservation department<br />
<br />
This hands on workshop will step through the components of the application framework and the process of customizing the application.<br />
<br />
TRAINING OUTLINE<br />
* https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training-Code4Lib-2015<br />
<br />
''Interested in Attending''<br />
# Megan Kudzia<br />
# Julie Swierczek<br />
<br />
====Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable:====<br />
Morning, Parlor A<br />
* Karen A. Coombs, OCLC, coombsk@oclc.org<br />
<br />
Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br />
<br />
We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br />
<br />
''Interested in Attending''<br />
# Peggy Griesinger<br />
# Ray Schwartz<br />
# Josh Wilson<br />
<br />
==== Delivering and Preserving GIS Data ====<br />
Morning, Council<br />
* Darren Hardy, Stanford University, drh@stanford.edu<br />
* Jack Reed, Stanford University, pjreed@stanford.edu<br />
* Eliot Jordan, Princeton University<br />
<br />
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.<br />
<br />
'''[https://stanford.box.com/geohydra-code4lib2015 Slides]'''<br />
<br />
''Interested in Attending''<br />
# [[User:Ssimpkin|Sarah Simpkin]]<br />
# Vicky Steeves<br />
# Andrew Battista<br />
# Peggy Griesinger<br />
<br />
====Linked Data Workshop====<br />
Morning, Studio<br />
* Karen Estlund, University of Oregon, kestlund@uoregon.edu<br />
* Tom Johnson, DPLA, tom@dp.la<br />
<br />
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.<br />
<br />
''Interested in Attending''<br />
# Logan Cox<br />
# Ray Schwartz<br />
# Chris Hallberg<br />
# Derek Merleaux<br />
# Steven Anderson<br />
# Eben English<br />
# Mark Mounts<br />
# Heather Pitts<br />
# Andrew Woods<br />
# Carol Bean<br />
# Naomi Dushay (probably)<br />
# David Lacy<br />
# David Uspal<br />
# David Bass<br />
# Brendan Quinn<br />
# Chrissy Rissmeyer<br />
# Sharon Clapp<br />
# Anjanette Young<br />
# Brooke Sansosti<br />
# Richard Tan<br />
# Catelynne Sahadath<br />
# Mark Breedlove<br />
# Julie Hardesty<br />
<br />
====RailsBridge: Intro to programming in Ruby on Rails====<br />
Morning, Galleria II<br />
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br />
* Laney McGlohon, Stanford University, laneymcg@stanford.edu<br />
* Additional instructors welcome<br />
<br />
''HOME WORK: Please do in advance!! http://docs.railsbridge.org/installfest/''<br />
To help the class run smoothly please complete the install fest before attending the class. If you have problems contact us!<br />
<br />
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.<br />
<br />
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].<br />
<br />
''Interested in Attending''<br />
# Maura Carbone<br />
#Vicky Steeves<br />
# Peggy Griesinger<br />
# Mike Price<br />
# Jean Rainwater<br />
# Coral Sheldon-Hess<br />
# Margaret Heller<br />
# Bohyun Kim<br />
# Mark Jarrell<br />
# Bojana Skarich<br />
# Sarah Bavier<br />
# Christina Salazar<br />
<br />
====Replace yourself with a painfully complex bash script...or try Ansible====<br />
Morning, Galleria III<br />
* Chad Nelson, chad dot nelson @ lyrasis dot org<br />
* Blake Carver, Blake dot carver @lyrasis dot org<br />
<br />
[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.<br />
<br />
''Interested in Attending''<br />
# Ray Schwartz<br />
# Coral Sheldon-Hess<br />
# Kevin S. Clarke<br />
# Joshua Gomez<br />
# Charlie Morris<br />
# Andy Mardesich<br />
# Anna Headley<br />
# Chelsea Lobdell<br />
# Shaun Ellis<br />
# Mark Mounts<br />
# Chris Sharp<br />
# Heidi Frank<br />
# Anjanette Young<br />
<br />
====Visualizing Library Data====<br />
Morning, Grand Ballroom II<br />
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br />
<br />
Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br />
<br />
''Interested in Attending''<br />
# Ashley Blewer!<br />
# Bobbi Fox<br />
# Ray Schwartz<br />
# Ranti Junus<br />
# Eric Phetteplace<br />
# Joshua Gomez<br />
# Charlie Morris<br />
# Andy Mardesich<br />
# Tao Zhao<br />
# Chris Hallberg<br />
# Derek Merleaux<br />
# Bohyun Kim<br />
# Mark Jarrell<br />
# Eben English<br />
# Shaun Ellis<br />
# Sarah Simpkin<br />
# Mark Mounts<br />
# Kathryn Stine<br />
# Steve Meyer<br />
# Matt Critchlow<br />
# Andrew Pasterfield<br />
# Ray Henry<br />
# Bret Davidson<br />
# Naomi Dushay (maybe)<br />
# Eric Frierson<br />
# Matt Bernhardt<br />
# Greg Bem (Morning only)<br />
# Dominic Bordelon<br />
# Jim LeFager<br />
# Sarah Park<br />
# Brian Westra<br />
<br />
===FULL DAY:===<br />
<br />
====Code Retreat====<br />
Full Day, Parlor B<br />
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br />
* Additional facilitators welcome; Especially if you have CodeRetreat experience.<br />
<br />
"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br />
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.<br />
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]<br />
<br />
''Interested in Attending''<br />
# Mike Giarlo<br />
# Charlie Morris<br />
# Devon Smith<br />
# Barbara Hui<br />
# Carol Bean<br />
# Matt Connolly<br />
# James Van Mil<br />
# Glen Horton<br />
# Jon Earley<br />
<br />
====Code4Arc ====<br />
Full Day, Directors<br />
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br />
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br />
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br />
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br />
<br />
What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br />
<br />
Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br />
<br />
The schedule may include the following:<br />
* Panel type conversations about the State of Art in Archives <br />
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br />
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br />
<br />
Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br />
<br />
When signing up, please indicate if you are an end-user or a developer.<br />
<br />
''Interested in Attending''<br />
# Laney McGlohon - developer<br />
# Shaun Ellis<br />
# Ryan Rotter - sysadmin/developer<br />
# Matt LaChance<br />
# Maureen Callahan - archivist, often-times product owner<br />
# Liza Harrell-Edge - end-user<br />
# Jessica Venlet - end-user/archivist (can be there in the afternoon)<br />
# Andrew Berger - "digital" archivist<br />
# Bill Kelm - sysadmin<br />
# Jeremy Floyd - end-user (archivist turned metadata librarian)<br />
# Sara Amato (morning only) - end-user<br />
# Julie Hardesty (afternoon only) - end-user (metadata librarian)<br />
<br />
====[http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp code4lib/Write The Docs barcamp]====<br />
Full day, Parlor C<br />
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br />
* Write the Docs contacts: TBA<br />
<br />
'''Event page where you can find the latest information and... documentation(!) at [http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp]'''<br />
<br />
Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br />
<br />
Remember, like metadata, documentation is a love note to the future.<br />
<br />
More information about Write the Docs at http://conf.writethedocs.org/ There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br />
<br />
''Interested in Attending''<br />
'''Full day'''<br />
# <br />
<br />
'''Morning'''<br />
# Ranti Junus<br />
# Mita Williams<br />
# Whitni Watkins<br />
# Jason Raitz<br />
<br />
'''Afternoon'''<br />
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. <br />
# Chris Sharp<br />
# Julie Swierczek<br />
<br />
===AFTERNOON:===<br />
==== A hands-on introduction to GeoBlacklight ====<br />
Afternoon, Council<br />
* Darren Hardy, Stanford University, drh@stanford.edu<br />
* Jack Reed, Stanford University, pjreed@stanford.edu<br />
<br />
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".<br />
<br />
''Interested in Attending''<br />
# [[User:Ssimpkin|Sarah Simpkin]]<br />
# Vicky Steeves<br />
# Andrew Battista<br />
# Peggy Griesinger<br />
<br />
==== CollectionSpace: Getting it up and running at your museum ====<br />
Afternoon, Galleria II<br />
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br />
* Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org<br />
<br />
This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br />
<br />
Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br />
<br />
''Interested in Attending''<br />
# Terry Brady<br />
# Sharon Clapp<br />
<br />
==== Dive into Hydra ====<br />
Afternoon, Studio<br />
* Justin Coyne, Data Curation Experts, justin@curationexperts.com<br />
* Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
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.<br />
<br />
''Interested in Attending''<br />
# Maura Carbone<br />
# Peggy Griesinger<br />
# Mike Price<br />
# Jean Rainwater<br />
# Sara Amato<br />
# David Bass<br />
# Scott Fisher<br />
# Brian E. Davis<br />
# Sarah Bavier<br />
# Christina Salazar<br />
# Sarah Park<br />
<br />
==== DPLA API Workshop: ====<br />
Afternoon, Grand Ballroom II<br />
* Audrey Altman, DPLA<br />
* Mark Breedlove, DPLA<br />
* Mark Matienzo, DPLA<br />
* Tom Johnson, DPLA<br />
<br />
The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
# Ranti Junus<br />
# Jean Rainwater<br />
# Mita Williams<br />
# Margaret Heller<br />
# Bohyun Kim<br />
# Steven Anderson<br />
# Shaun Ellis<br />
# Sarah Simpkin<br />
# Mark Jarrell<br />
# Heather Pitts<br />
# Kathryn Stine<br />
# Andrew Woods<br />
# Greg Bem<br />
# Brooke Sansosti<br />
# Jim LeFager<br />
# Scott Chamberlain<br />
<br />
==== Fail4Lib 2015 ====<br />
Afternoon, Galleria I<br />
* Andreas Orphanides, akorphan (at) ncsu.edu<br />
* Jason Casden, jmcasden (at) ncsu.edu<br />
<br />
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.<br />
<br />
This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br />
<br />
The schedule may include the following:<br />
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br />
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br />
* 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.<br />
<br />
''Readings''<br />
<br />
'''Case Study 1: The Healthcare.gov rollout'''<br />
<br />
* [http://www.theverge.com/us-world/2013/12/3/5163228/healthcare-gov-obamacare-website-shows-how-government-can-do-tech-better Adrianne Jeffries (The Verge): Thanks a lot, healthcare.gov]<br />
<br />
* [http://www.forbes.com/sites/lorenthompson/2013/12/03/healthcare-gov-diagnosis-the-government-broke-every-rule-of-project-management/ Loren Thompson (Forbes): Healthcare.gov diagnosis: the government broke every rule of project management]<br />
<br />
* Optional, nice summary: [http://npengage.com/nonprofit-technology/lessons-learned-from-the-healthcare-gov-rollout/ Bo Crader (npEngage): Lessons learned from the healthcare.gov rollout]<br />
* Optional, very enterprisey: [http://www.enterprisetech.com/2014/04/04/hyperscale-lessons-healthcare-gov/ Alex Woodie (EnterpriseTech): The hyperscale lessons of healthcare.gov]<br />
<br />
'''Case Study 2: The Challenger disaster'''<br />
<br />
* [http://ethics.tamu.edu/Portals/3/Case%20Studies/Shuttle.pdf Engineering Ethics: The Space Shuttle Challenger disaster (case study instructor's guide)]<br />
** This is designed as an instructor's guide, but the summary material beginning on page 3 stands on its own as a case study report. The instructor's materials on the first couple pages are also worth reading.<br />
<br />
* [http://www.nbcnews.com/id/3077541/ns/technology_and_science-space/t/shuttle-report-blames-nasa-culture/ NBC News: Shuttle report blames NASA culture]<br />
<br />
* Optional, good technical detail: [http://en.wikipedia.org/wiki/Space_Shuttle_Challenger_disaster Wikipedia: Space Shuttle Challenger disaster]<br />
* Optional: [http://science.ksc.nasa.gov/shuttle/missions/51-l/docs/rogers-commission/Appendix-F.txt Richard Feynman: Appendix F: Personal observations on the reliability of the Shuttle (Rogers Commission excerpt)]<br />
<br />
''Interested in attending''<br />
# Ray Schwartz<br />
# Charlie Morris<br />
# Emily Lynema<br />
# Bret Davidson<br />
# Hannah Sommers<br />
<br />
==== Intro to Docker ====<br />
Afternoon, Galleria III<br />
* John Fink, McMaster University, john dot fink at gmail dot com<br />
* Francis Kayiwa, University of Maryland Libraries , fkayiwa at umd dot edu<br />
<br />
[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.<br />
<br />
''Interested in Attending''<br />
# Jim Hahn<br />
# Joshua Gomez<br />
# Bobbi Fox<br />
# Ray Schwartz<br />
# Megan Kudzia<br />
# Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)<br />
# Cary Gordon (uses Docker in production on AWS)<br />
# Eric Phetteplace<br />
# Esther Verreau<br />
# Charlie Morris<br />
# Anna Headley (voting for afternoon, compliments ansible)<br />
# Shaun Ellis<br />
# Mark Mounts<br />
# Matt Critchlow<br />
# Ray Henry<br />
# Eric Frierson<br />
# David Lacy<br />
# David Uspal<br />
# Matt Bernhardt<br />
# Brendan Quinn<br />
# Anjanette Young<br />
# Kevin S. Clarke<br />
<br />
==== Intro to Git & possibly beyond ====<br />
Afternoon, Parlor A<br />
* Erin Fahy, Stanford University, efahy@stanford.edu<br />
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br />
<br />
We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br />
* What is a Distributed Version Control System?<br />
* What's the difference between Git and Github.com?<br />
* How to initialize new Git projects locally and on a remote server/Github<br />
* Cloning/Forking existing projects and keeping up to date<br />
* The wonderful world of Git branches<br />
* Interactive rebasing<br />
* Contributing code to existing projects & what pull requests are<br />
* How to handle merge conflicts<br />
* Overview of workflows and branch best practices<br />
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br />
<br />
''Interested in Attending''<br />
# Jeannie Graham<br />
# Derek Merleaux<br />
# Laurie Reeves<br />
# Bojana Skarich<br />
# Heidi Frank<br />
# Jason Raitz<br />
# Emily Lynema<br />
# Brian E. Davis<br />
# Dominic Bordelon<br />
# Richard Tan<br />
# Catelynne Sahadath<br />
# Brian Westra<br />
<br />
==== Presentations workshop ====<br />
Afternoon, Grand Ballroom I<br />
* Chris Beer, Stanford University, cabeer@stanford.edu<br />
* Additional facilitators welcome.<br />
<br />
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.<br />
<br />
''Interested in Attending''<br />
#Vicky Steeves<br />
<br />
[[Category:Code4Lib2015]]</div>JulietHardestyhttps://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=426372015 Preconference Proposals2015-02-05T13:41:55Z<p>JulietHardesty: /* Linked Data Workshop */</p>
<hr />
<div>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. <br />
<br />
== Preconference Schedule (draft) ==<br />
There may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib. See below for further information on each session.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)<br />
|-<br />
| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (9: Needs: projector, internet connection, and power strips) || Intro to Git & possibly beyond (40: Needs: projector/screen)<br />
|-<br />
| '''Parlor B (30)''' || Code Retreat (18: Needs whiteboard, dry-erase markers, projector) || Code Retreat (15: Needs whiteboard, dry-erase markers, projector) <br />
|-<br />
| '''Parlor C (30)''' || [[code4lib/Write The Docs barcamp]] (8: Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || [[code4lib/Write The Docs barcamp]] (5)<br />
|-<br />
| '''Grand Ballroom''' I (320) || '''CANCELLED''': [UXtravaganza] || Presentations workshop (1: Needs: projector/screen)<br />
|-<br />
| '''Grand Ballroom''' II (200) || Visualizing Library Data (60: Needs: projector) || DPLA API Workshop (34: Bringing their own projector)<br />
|-<br />
| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (1: Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (13: Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)<br />
|-<br />
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (25: Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (5: Needs: Projector)<br />
|-<br />
| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (20: Need projector) || Intro to Docker (52)<br />
|-<br />
| '''Studio (35)''' || Linked Data Workshop (56: Bringing their own projector) || Dive into Hydra (29: Needs: projector/screen; Requests: classroom style seating)<br />
|-<br />
| '''Directors (35)''' || Code4Arc (20: Needs: projector) || Code4Arc (18: Needs: projector)<br />
|-<br />
| '''Council (45)''' || Delivering and Preserving GIS Data (10: Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (19: Needs: projector, outlets; Requests: list of attendees)<br />
|}<br />
<br />
== Pre-conferences ==<br />
===MORNING:===<br />
==== Coding Custom Solutions for Every Department in the Library with File Analyzer ====<br />
Morning, Galleria I<br />
* Terry Brady, Georgetown University Library, twb27@georgetown.edu<br />
<br />
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.<br />
* Analyzing Marc Records for the Cataloging department<br />
* Transferring ILS invoices for the University Account System for the Acquisitions department <br />
* Delivering patron fines to the Bursar’s office for the Access Service department<br />
* Summarizing student worker timesheet data for the Finance department<br />
* Validating counter compliant reports for the Electronic Resources department<br />
* Preparing ingest packages for the Digital Services department<br />
* Validating checksums for the Preservation department<br />
<br />
This hands on workshop will step through the components of the application framework and the process of customizing the application.<br />
<br />
TRAINING OUTLINE<br />
* https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training-Code4Lib-2015<br />
<br />
''Interested in Attending''<br />
# Megan Kudzia<br />
# Julie Swierczek<br />
<br />
====Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable:====<br />
Morning, Parlor A<br />
* Karen A. Coombs, OCLC, coombsk@oclc.org<br />
<br />
Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br />
<br />
We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br />
<br />
''Interested in Attending''<br />
# Peggy Griesinger<br />
# Ray Schwartz<br />
# Josh Wilson<br />
<br />
==== Delivering and Preserving GIS Data ====<br />
Morning, Council<br />
* Darren Hardy, Stanford University, drh@stanford.edu<br />
* Jack Reed, Stanford University, pjreed@stanford.edu<br />
* Eliot Jordan, Princeton University<br />
<br />
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.<br />
<br />
'''[https://stanford.box.com/geohydra-code4lib2015 Slides]'''<br />
<br />
''Interested in Attending''<br />
# [[User:Ssimpkin|Sarah Simpkin]]<br />
# Vicky Steeves<br />
# Andrew Battista<br />
# Peggy Griesinger<br />
<br />
====Linked Data Workshop====<br />
Morning, Studio<br />
* Karen Estlund, University of Oregon, kestlund@uoregon.edu<br />
* Tom Johnson, DPLA, tom@dp.la<br />
<br />
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.<br />
<br />
''Interested in Attending''<br />
# Logan Cox<br />
# Ray Schwartz<br />
# Chris Hallberg<br />
# Derek Merleaux<br />
# Steven Anderson<br />
# Eben English<br />
# Mark Mounts<br />
# Heather Pitts<br />
# Andrew Woods<br />
# Carol Bean<br />
# Naomi Dushay (probably)<br />
# David Lacy<br />
# David Uspal<br />
# David Bass<br />
# Brendan Quinn<br />
# Chrissy Rissmeyer<br />
# Sharon Clapp<br />
# Anjanette Young<br />
# Brooke Sansosti<br />
# Richard Tan<br />
# Catelynne Sahadath<br />
# Mark Breedlove<br />
# Julie Hardesty<br />
<br />
====RailsBridge: Intro to programming in Ruby on Rails====<br />
Morning, Galleria II<br />
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br />
* Laney McGlohon, Stanford University, laneymcg@stanford.edu<br />
* Additional instructors welcome<br />
<br />
''HOME WORK: Please do in advance!! http://docs.railsbridge.org/installfest/''<br />
To help the class run smoothly please complete the install fest before attending the class. If you have problems contact us!<br />
<br />
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.<br />
<br />
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].<br />
<br />
''Interested in Attending''<br />
# Maura Carbone<br />
#Vicky Steeves<br />
# Peggy Griesinger<br />
# Mike Price<br />
# Jean Rainwater<br />
# Coral Sheldon-Hess<br />
# Margaret Heller<br />
# Bohyun Kim<br />
# Mark Jarrell<br />
# Bojana Skarich<br />
# Sarah Bavier<br />
# Christina Salazar<br />
<br />
====Replace yourself with a painfully complex bash script...or try Ansible====<br />
Morning, Galleria III<br />
* Chad Nelson, chad dot nelson @ lyrasis dot org<br />
* Blake Carver, Blake dot carver @lyrasis dot org<br />
<br />
[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.<br />
<br />
''Interested in Attending''<br />
# Ray Schwartz<br />
# Coral Sheldon-Hess<br />
# Kevin S. Clarke<br />
# Joshua Gomez<br />
# Charlie Morris<br />
# Andy Mardesich<br />
# Anna Headley<br />
# Chelsea Lobdell<br />
# Shaun Ellis<br />
# Mark Mounts<br />
# Chris Sharp<br />
# Heidi Frank<br />
# Anjanette Young<br />
<br />
====Visualizing Library Data====<br />
Morning, Grand Ballroom II<br />
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br />
<br />
Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br />
<br />
''Interested in Attending''<br />
# Ashley Blewer!<br />
# Bobbi Fox<br />
# Ray Schwartz<br />
# Ranti Junus<br />
# Eric Phetteplace<br />
# Joshua Gomez<br />
# Charlie Morris<br />
# Andy Mardesich<br />
# Tao Zhao<br />
# Chris Hallberg<br />
# Derek Merleaux<br />
# Bohyun Kim<br />
# Mark Jarrell<br />
# Eben English<br />
# Shaun Ellis<br />
# Sarah Simpkin<br />
# Mark Mounts<br />
# Kathryn Stine<br />
# Steve Meyer<br />
# Matt Critchlow<br />
# Andrew Pasterfield<br />
# Ray Henry<br />
# Bret Davidson<br />
# Naomi Dushay (maybe)<br />
# Eric Frierson<br />
# Matt Bernhardt<br />
# Greg Bem (Morning only)<br />
# Dominic Bordelon<br />
# Jim LeFager<br />
# Sarah Park<br />
# Brian Westra<br />
<br />
===FULL DAY:===<br />
<br />
====Code Retreat====<br />
Full Day, Parlor B<br />
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br />
* Additional facilitators welcome; Especially if you have CodeRetreat experience.<br />
<br />
"Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br />
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.<br />
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]<br />
<br />
''Interested in Attending''<br />
# Mike Giarlo<br />
# Charlie Morris<br />
# Devon Smith<br />
# Barbara Hui<br />
# Carol Bean<br />
# Matt Connolly<br />
# James Van Mil<br />
# Glen Horton<br />
# Jon Earley<br />
<br />
====Code4Arc ====<br />
Full Day, Directors<br />
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br />
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br />
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br />
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br />
<br />
What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br />
<br />
Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br />
<br />
The schedule may include the following:<br />
* Panel type conversations about the State of Art in Archives <br />
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br />
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br />
<br />
Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br />
<br />
When signing up, please indicate if you are an end-user or a developer.<br />
<br />
''Interested in Attending''<br />
# Laney McGlohon - developer<br />
# Shaun Ellis<br />
# Ryan Rotter - sysadmin/developer<br />
# Matt LaChance<br />
# Maureen Callahan - archivist, often-times product owner<br />
# Liza Harrell-Edge - end-user<br />
# Jessica Venlet - end-user/archivist (can be there in the afternoon)<br />
# Andrew Berger - "digital" archivist<br />
# Bill Kelm - sysadmin<br />
# Jeremy Floyd - end-user (archivist turned metadata librarian)<br />
# Sara Amato (morning only) - end-user<br />
<br />
====[http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp code4lib/Write The Docs barcamp]====<br />
Full day, Parlor C<br />
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br />
* Write the Docs contacts: TBA<br />
<br />
'''Event page where you can find the latest information and... documentation(!) at [http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp]'''<br />
<br />
Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br />
<br />
Remember, like metadata, documentation is a love note to the future.<br />
<br />
More information about Write the Docs at http://conf.writethedocs.org/ There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br />
<br />
''Interested in Attending''<br />
'''Full day'''<br />
# <br />
<br />
'''Morning'''<br />
# Ranti Junus<br />
# Mita Williams<br />
# Whitni Watkins<br />
# Jason Raitz<br />
<br />
'''Afternoon'''<br />
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. <br />
# Chris Sharp<br />
# Julie Swierczek<br />
<br />
===AFTERNOON:===<br />
==== A hands-on introduction to GeoBlacklight ====<br />
Afternoon, Council<br />
* Darren Hardy, Stanford University, drh@stanford.edu<br />
* Jack Reed, Stanford University, pjreed@stanford.edu<br />
<br />
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".<br />
<br />
''Interested in Attending''<br />
# [[User:Ssimpkin|Sarah Simpkin]]<br />
# Vicky Steeves<br />
# Andrew Battista<br />
# Peggy Griesinger<br />
<br />
==== CollectionSpace: Getting it up and running at your museum ====<br />
Afternoon, Galleria II<br />
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br />
* Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org<br />
<br />
This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br />
<br />
Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br />
<br />
''Interested in Attending''<br />
# Terry Brady<br />
# Sharon Clapp<br />
<br />
==== Dive into Hydra ====<br />
Afternoon, Studio<br />
* Justin Coyne, Data Curation Experts, justin@curationexperts.com<br />
* Bess Sadler, Stanford University, bess@stanford.edu<br />
<br />
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.<br />
<br />
''Interested in Attending''<br />
# Maura Carbone<br />
# Peggy Griesinger<br />
# Mike Price<br />
# Jean Rainwater<br />
# Sara Amato<br />
# David Bass<br />
# Scott Fisher<br />
# Brian E. Davis<br />
# Sarah Bavier<br />
# Christina Salazar<br />
# Sarah Park<br />
<br />
==== DPLA API Workshop: ====<br />
Afternoon, Grand Ballroom II<br />
* Audrey Altman, DPLA<br />
* Mark Breedlove, DPLA<br />
* Mark Matienzo, DPLA<br />
* Tom Johnson, DPLA<br />
<br />
The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br />
<br />
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br />
# Ranti Junus<br />
# Jean Rainwater<br />
# Mita Williams<br />
# Margaret Heller<br />
# Bohyun Kim<br />
# Steven Anderson<br />
# Shaun Ellis<br />
# Sarah Simpkin<br />
# Mark Jarrell<br />
# Heather Pitts<br />
# Kathryn Stine<br />
# Andrew Woods<br />
# Greg Bem<br />
# Brooke Sansosti<br />
# Jim LeFager<br />
# Scott Chamberlain<br />
<br />
==== Fail4Lib 2015 ====<br />
Afternoon, Galleria I<br />
* Andreas Orphanides, akorphan (at) ncsu.edu<br />
* Jason Casden, jmcasden (at) ncsu.edu<br />
<br />
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.<br />
<br />
This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br />
<br />
The schedule may include the following:<br />
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br />
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br />
* 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.<br />
<br />
''Readings''<br />
<br />
'''Case Study 1: The Healthcare.gov rollout'''<br />
<br />
* [http://www.theverge.com/us-world/2013/12/3/5163228/healthcare-gov-obamacare-website-shows-how-government-can-do-tech-better Adrianne Jeffries (The Verge): Thanks a lot, healthcare.gov]<br />
<br />
* [http://www.forbes.com/sites/lorenthompson/2013/12/03/healthcare-gov-diagnosis-the-government-broke-every-rule-of-project-management/ Loren Thompson (Forbes): Healthcare.gov diagnosis: the government broke every rule of project management]<br />
<br />
* Optional, nice summary: [http://npengage.com/nonprofit-technology/lessons-learned-from-the-healthcare-gov-rollout/ Bo Crader (npEngage): Lessons learned from the healthcare.gov rollout]<br />
* Optional, very enterprisey: [http://www.enterprisetech.com/2014/04/04/hyperscale-lessons-healthcare-gov/ Alex Woodie (EnterpriseTech): The hyperscale lessons of healthcare.gov]<br />
<br />
'''Case Study 2: The Challenger disaster'''<br />
<br />
* [http://ethics.tamu.edu/Portals/3/Case%20Studies/Shuttle.pdf Engineering Ethics: The Space Shuttle Challenger disaster (case study instructor's guide)]<br />
** This is designed as an instructor's guide, but the summary material beginning on page 3 stands on its own as a case study report. The instructor's materials on the first couple pages are also worth reading.<br />
<br />
* [http://www.nbcnews.com/id/3077541/ns/technology_and_science-space/t/shuttle-report-blames-nasa-culture/ NBC News: Shuttle report blames NASA culture]<br />
<br />
* Optional, good technical detail: [http://en.wikipedia.org/wiki/Space_Shuttle_Challenger_disaster Wikipedia: Space Shuttle Challenger disaster]<br />
* Optional: [http://science.ksc.nasa.gov/shuttle/missions/51-l/docs/rogers-commission/Appendix-F.txt Richard Feynman: Appendix F: Personal observations on the reliability of the Shuttle (Rogers Commission excerpt)]<br />
<br />
''Interested in attending''<br />
# Ray Schwartz<br />
# Charlie Morris<br />
# Emily Lynema<br />
# Bret Davidson<br />
# Hannah Sommers<br />
<br />
==== Intro to Docker ====<br />
Afternoon, Galleria III<br />
* John Fink, McMaster University, john dot fink at gmail dot com<br />
* Francis Kayiwa, University of Maryland Libraries , fkayiwa at umd dot edu<br />
<br />
[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.<br />
<br />
''Interested in Attending''<br />
# Jim Hahn<br />
# Joshua Gomez<br />
# Bobbi Fox<br />
# Ray Schwartz<br />
# Megan Kudzia<br />
# Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)<br />
# Cary Gordon (uses Docker in production on AWS)<br />
# Eric Phetteplace<br />
# Esther Verreau<br />
# Charlie Morris<br />
# Anna Headley (voting for afternoon, compliments ansible)<br />
# Shaun Ellis<br />
# Mark Mounts<br />
# Matt Critchlow<br />
# Ray Henry<br />
# Eric Frierson<br />
# David Lacy<br />
# David Uspal<br />
# Matt Bernhardt<br />
# Brendan Quinn<br />
# Anjanette Young<br />
# Kevin S. Clarke<br />
<br />
==== Intro to Git & possibly beyond ====<br />
Afternoon, Parlor A<br />
* Erin Fahy, Stanford University, efahy@stanford.edu<br />
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br />
<br />
We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br />
* What is a Distributed Version Control System?<br />
* What's the difference between Git and Github.com?<br />
* How to initialize new Git projects locally and on a remote server/Github<br />
* Cloning/Forking existing projects and keeping up to date<br />
* The wonderful world of Git branches<br />
* Interactive rebasing<br />
* Contributing code to existing projects & what pull requests are<br />
* How to handle merge conflicts<br />
* Overview of workflows and branch best practices<br />
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br />
<br />
''Interested in Attending''<br />
# Jeannie Graham<br />
# Derek Merleaux<br />
# Laurie Reeves<br />
# Bojana Skarich<br />
# Heidi Frank<br />
# Jason Raitz<br />
# Emily Lynema<br />
# Brian E. Davis<br />
# Dominic Bordelon<br />
# Richard Tan<br />
# Catelynne Sahadath<br />
# Brian Westra<br />
<br />
==== Presentations workshop ====<br />
Afternoon, Grand Ballroom I<br />
* Chris Beer, Stanford University, cabeer@stanford.edu<br />
* Additional facilitators welcome.<br />
<br />
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.<br />
<br />
''Interested in Attending''<br />
#Vicky Steeves<br />
<br />
[[Category:Code4Lib2015]]</div>JulietHardestyhttps://wiki.code4lib.org/index.php?title=PBCore_RDF_Hackathon&diff=42405PBCore RDF Hackathon2015-01-09T17:58:03Z<p>JulietHardesty: /* Participants */</p>
<hr />
<div>SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing<br />
<br>Please also fill out this form: http://goo.gl/forms/nAvL52W9MI<br />
<br><br><br />
'''>>> When, Where, What time?'''<br />
<br>Date: '''Saturday & Sunday, February 7-8, 2015'''<br />
<br>Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)<br />
<br>Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''<br />
<br>hashtag: '''#PBCoreRDF15'''<br />
<br />
== What will be the format of the event? ==<br />
<br />
In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.<br />
<br><br />
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.<br />
=== Saturday, February 7 ===<br />
8:30am – Welcome, introductions<br />
<br>9am - 9:45am - Discuss and determine the domain and scope of the ontology<br />
<br>9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, BIBFRAME, PREMIS) to determine what can be used for PBCore. Snacks and coffee to be served.<br />
<br>Noon - 1pm – Lunch on your own.<br />
<br>1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.<br />
<br>2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.<br />
<br>4:45pm - 5pm - Review and wrap up.<br />
<br />
=== Sunday, February 8 ===<br />
8:30am - Review progress to date; introductions of new participants<br />
<br> 8:45am - noon - Continue working on class hierarchy and properties<br />
<br> noon - 1pm - Lunch on your own<br />
<br> 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?<br />
<br> 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups<br />
<br> 4:30pm - 5pm -- Return to smaller groups, make suggested edits, finalize documentation <br />
<br />
== Summary & Background==<br />
The PBCore RDF Ontology Hackathon is occurring out of a growing need for PBCore users to express their metadata in RDF. A number of PBCore users contribute to and are part of the [http://projecthydra.org/ Project Hydra] community, a collaborative, open source effort to build digital repository software solutions at archives institutions. Hydra is built on a framework that uses Fedora Commons as the repository for storing metadata. Many users are seeking to update their Fedora repositories to the latest version (Fedora 4), which provides a great opportunity to develop an RDF data structure. If PBCore had an RDF ontology, it would be easier for PBCore users to take full advantage of Fedora 4 capabilities in managing data and encourage adoption of Fedora 4.<br />
<br />
<br>We envision building upon existing knowledge bases that are already well established. In particular, we hope to harmonize the EBUCore ontology with PBCore and determine what existing terms from the EBUCore vocabulary can be re-used, and what concepts may be unique to PBCore that would deem the need for additional terms.<br />
<br />
<br>[http://www.pbcore.org PBCore] is a metadata schema for audiovisual materials. Its original development in 2004 was funded by the Corporation for Public Broadcasting, with a goal of creating a metadata standard for public broadcasters to share information about their video and audio assets within and among public media stations. Since its conception, PBCore has been adopted by a growing number of audiovisual archives and organizations that needed a way to describe their archival audiovisual collections. The schema has been reviewed multiple times and is currently in further development via the [http://www.americanarchive.org American Archive of Public Broadcasting] and the [http://amianet.org/ Association of Moving Image Archivists (AMIA)] PBCore Advisory Subcommittee. <br />
<br />
<br>The Schema Team is working on an updated version of PBCore (PBCore 2.1), the changes of which will consist of minor tweaks and bug fixes, and is expected to be released in March 2015. Other Teams on the Subcommittee are working on PBCore outreach, education, documentation, and a new website.<br />
<br />
== Working Groups ==<br />
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.<br />
<br />
=== Intellectual Content Working Group ===<br />
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.<br />
<br />
==== Participants ====<br />
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]<br />
<br />
Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]<br />
<br />
=== Intellectual Property Working Group ===<br />
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles. <br />
<br />
==== Participants ====<br />
Rebecca Guenther, LC and NYU/MIAP, @rguenther52, rguenther52@gmail.com<br />
<br />
Rebecca Fraimow, NDSR and WGBH, [https://twitter.com/rhfraim @rhfraim]<br />
<br />
=== Instantiation Working Group === <br />
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.<br />
<br />
==== Participants ====<br />
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]<br />
<br />
Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]<br />
<br />
=== Essence Track Working Group ===<br />
This group will focus on the essence track part of the knowledge base.<br />
<br />
==== Participants ====<br />
Name, Institution, Twitter handle/email address<br />
<br />
=== Documentation Working Group ===<br />
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the documentation working group.<br />
<br />
==== Participants ====<br />
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]<br />
<br />
Rebecca Fraimow, NDSR and WGBH, [https://twitter.com/rhfraim @rhfraim]<br />
<br />
== Suggested Reading & Preparation ==<br />
* Sign up for a Code4Lib wiki account (if you don't already have an account)<br />
* Everyone should read at least the first chapters of the Allemang book, Semantic Web for the Working Ontologist:<br />
http://www.worldcat.org/title/semantic-web-for-the-working-ontologist-effective-modeling-in-rdfs-and-owl/oclc/733936673<br />
* Everyone should understand the RDF meaning of classes, properties, domain and range before beginning. (cf: http://kcoyle.blogspot.com/2014/11/classes-in-rdf.html)<br />
* Review PBCore Schema: http://pbcore.org/elements/<br />
* Read this awesome Ontology Development 101 publication: http://protege.stanford.edu/publications/ontology_development/ontology101-noy-mcguinness.html<br />
* Read about RDF on the W3C website: http://www.w3.org/RDF/<br />
* Read this article: "Multi-Entity Models of Resource Description in the Semantic Web: A comparison of FRBR, RDA and BIBFRAME." (http://kcoyle.net/LHTv32n4preprint.pdf)<br />
* Review existing ontologies<br />
** EBUCore: http://www.ebu.ch/metadata/ontologies/ebucore/index.html and http://www.ebu.ch/metadata/ontologies/ebucore/ebucore.rdf<br />
** MODS: http://www.loc.gov/standards/mods/modsrdf/<br />
** BIBFRAME: http://www.loc.gov/bibframe/<br />
** DC Terms: http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=terms#<br />
** FOAF: http://www.foaf-project.org/<br />
**PREMIS: http://id.loc.gov/ontologies/premis.html<br />
<br />
== Tips and Advice from the Community == <br />
<br />
==== from Karen Coyle ==== <br />
* Don't lean too heavily on Protege. Protege is very OWL-oriented and can lead one far astray. It's easy to click on check boxes without knowing what they really mean. Do as much development as you can without using Protege, and do your development in RDFS not OWL. Later you can use Protege to check your work, or to complete the code.<br />
<br />
* Develop in ntriples or turtle but NOT rdf/xml. RDF differs from XML in some fundamental ways that are not obvious, and developing in rdf/xml masks these differences and often leads to the development of not very good ontologies.<br />
<br />
==== from Jean-Pierre Evain ====<br />
<br />
* I have personally no issue whatsoever with Protégé or RDF/XML for the type of ontology we seem to be aiming at<br />
<br />
* I agree that OWL is probably not required. But this doesn't prevent using Protégé. Of course one needs to know what is specific to OWL.<br />
<br />
== Need more info? ==<br />
If you have questions or need more information, feel free to contact Casey Davis at casey_davis [at] wgbh [dot] org.</div>JulietHardestyhttps://wiki.code4lib.org/index.php?title=PBCore_RDF_Hackathon&diff=42404PBCore RDF Hackathon2015-01-09T17:50:31Z<p>JulietHardesty: </p>
<hr />
<div>SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing<br />
<br>Please also fill out this form: http://goo.gl/forms/nAvL52W9MI<br />
<br><br><br />
'''>>> When, Where, What time?'''<br />
<br>Date: '''Saturday & Sunday, February 7-8, 2015'''<br />
<br>Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)<br />
<br>Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''<br />
<br>hashtag: '''#PBCoreRDF15'''<br />
<br />
== What will be the format of the event? ==<br />
<br />
In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.<br />
<br><br />
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.<br />
=== Saturday, February 7 ===<br />
8:30am – Welcome, introductions<br />
<br>9am - 9:45am - Discuss and determine the domain and scope of the ontology<br />
<br>9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, BIBFRAME, PREMIS) to determine what can be used for PBCore. Snacks and coffee to be served.<br />
<br>Noon - 1pm – Lunch on your own.<br />
<br>1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.<br />
<br>2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.<br />
<br>4:45pm - 5pm - Review and wrap up.<br />
<br />
=== Sunday, February 8 ===<br />
8:30am - Review progress to date; introductions of new participants<br />
<br> 8:45am - noon - Continue working on class hierarchy and properties<br />
<br> noon - 1pm - Lunch on your own<br />
<br> 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?<br />
<br> 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups<br />
<br> 4:30pm - 5pm -- Return to smaller groups, make suggested edits, finalize documentation <br />
<br />
== Summary & Background==<br />
The PBCore RDF Ontology Hackathon is occurring out of a growing need for PBCore users to express their metadata in RDF. A number of PBCore users contribute to and are part of the [http://projecthydra.org/ Project Hydra] community, a collaborative, open source effort to build digital repository software solutions at archives institutions. Hydra is built on a framework that uses Fedora Commons as the repository for storing metadata. Many users are seeking to update their Fedora repositories to the latest version (Fedora 4), which provides a great opportunity to develop an RDF data structure. If PBCore had an RDF ontology, it would be easier for PBCore users to take full advantage of Fedora 4 capabilities in managing data and encourage adoption of Fedora 4.<br />
<br />
<br>We envision building upon existing knowledge bases that are already well established. In particular, we hope to harmonize the EBUCore ontology with PBCore and determine what existing terms from the EBUCore vocabulary can be re-used, and what concepts may be unique to PBCore that would deem the need for additional terms.<br />
<br />
<br>[http://www.pbcore.org PBCore] is a metadata schema for audiovisual materials. Its original development in 2004 was funded by the Corporation for Public Broadcasting, with a goal of creating a metadata standard for public broadcasters to share information about their video and audio assets within and among public media stations. Since its conception, PBCore has been adopted by a growing number of audiovisual archives and organizations that needed a way to describe their archival audiovisual collections. The schema has been reviewed multiple times and is currently in further development via the [http://www.americanarchive.org American Archive of Public Broadcasting] and the [http://amianet.org/ Association of Moving Image Archivists (AMIA)] PBCore Advisory Subcommittee. <br />
<br />
<br>The Schema Team is working on an updated version of PBCore (PBCore 2.1), the changes of which will consist of minor tweaks and bug fixes, and is expected to be released in March 2015. Other Teams on the Subcommittee are working on PBCore outreach, education, documentation, and a new website.<br />
<br />
== Working Groups ==<br />
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.<br />
<br />
=== Intellectual Content Working Group ===<br />
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.<br />
<br />
==== Participants ====<br />
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]<br />
<br />
Julie Hardesty, [https://twitter.com/jlhardes @jlhardes]<br />
<br />
=== Intellectual Property Working Group ===<br />
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles. <br />
<br />
==== Participants ====<br />
Rebecca Guenther, LC and NYU/MIAP, @rguenther52, rguenther52@gmail.com<br />
<br />
Rebecca Fraimow, NDSR and WGBH, [https://twitter.com/rhfraim @rhfraim]<br />
<br />
=== Instantiation Working Group === <br />
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.<br />
<br />
==== Participants ====<br />
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]<br />
<br />
Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]<br />
<br />
=== Essence Track Working Group ===<br />
This group will focus on the essence track part of the knowledge base.<br />
<br />
==== Participants ====<br />
Name, Institution, Twitter handle/email address<br />
<br />
=== Documentation Working Group ===<br />
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the documentation working group.<br />
<br />
==== Participants ====<br />
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]<br />
<br />
Rebecca Fraimow, NDSR and WGBH, [https://twitter.com/rhfraim @rhfraim]<br />
<br />
== Suggested Reading & Preparation ==<br />
* Sign up for a Code4Lib wiki account (if you don't already have an account)<br />
* Everyone should read at least the first chapters of the Allemang book, Semantic Web for the Working Ontologist:<br />
http://www.worldcat.org/title/semantic-web-for-the-working-ontologist-effective-modeling-in-rdfs-and-owl/oclc/733936673<br />
* Everyone should understand the RDF meaning of classes, properties, domain and range before beginning. (cf: http://kcoyle.blogspot.com/2014/11/classes-in-rdf.html)<br />
* Review PBCore Schema: http://pbcore.org/elements/<br />
* Read this awesome Ontology Development 101 publication: http://protege.stanford.edu/publications/ontology_development/ontology101-noy-mcguinness.html<br />
* Read about RDF on the W3C website: http://www.w3.org/RDF/<br />
* Read this article: "Multi-Entity Models of Resource Description in the Semantic Web: A comparison of FRBR, RDA and BIBFRAME." (http://kcoyle.net/LHTv32n4preprint.pdf)<br />
* Review existing ontologies<br />
** EBUCore: http://www.ebu.ch/metadata/ontologies/ebucore/index.html and http://www.ebu.ch/metadata/ontologies/ebucore/ebucore.rdf<br />
** MODS: http://www.loc.gov/standards/mods/modsrdf/<br />
** BIBFRAME: http://www.loc.gov/bibframe/<br />
** DC Terms: http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=terms#<br />
** FOAF: http://www.foaf-project.org/<br />
**PREMIS: http://id.loc.gov/ontologies/premis.html<br />
<br />
== Tips and Advice from the Community == <br />
<br />
==== from Karen Coyle ==== <br />
* Don't lean too heavily on Protege. Protege is very OWL-oriented and can lead one far astray. It's easy to click on check boxes without knowing what they really mean. Do as much development as you can without using Protege, and do your development in RDFS not OWL. Later you can use Protege to check your work, or to complete the code.<br />
<br />
* Develop in ntriples or turtle but NOT rdf/xml. RDF differs from XML in some fundamental ways that are not obvious, and developing in rdf/xml masks these differences and often leads to the development of not very good ontologies.<br />
<br />
==== from Jean-Pierre Evain ====<br />
<br />
* I have personally no issue whatsoever with Protégé or RDF/XML for the type of ontology we seem to be aiming at<br />
<br />
* I agree that OWL is probably not required. But this doesn't prevent using Protégé. Of course one needs to know what is specific to OWL.<br />
<br />
== Need more info? ==<br />
If you have questions or need more information, feel free to contact Casey Davis at casey_davis [at] wgbh [dot] org.</div>JulietHardestyhttps://wiki.code4lib.org/index.php?title=PBCore_RDF_Hackathon&diff=42395PBCore RDF Hackathon2015-01-07T18:33:41Z<p>JulietHardesty: /* Intellectual Content Working Group */</p>
<hr />
<div>SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing<br />
<br>Please also fill out this form: http://goo.gl/forms/nAvL52W9MI<br />
<br><br><br />
'''>>> When, Where, What time?'''<br />
<br>Date: '''Saturday & Sunday, February 7-8, 2015'''<br />
<br>Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)<br />
<br>Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''<br />
<br>hashtag: '''#PBCoreRDF15'''<br />
<br />
== What will be the format of the event? ==<br />
<br />
In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.<br />
<br><br />
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.<br />
=== Saturday, February 7 ===<br />
8:30am – Welcome, introductions<br />
<br>9am - 9:45am - Discuss and determine the domain and scope of the ontology<br />
<br>9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, BIBFRAME, PREMIS) to determine what can be used for PBCore. Snacks and coffee to be served.<br />
<br>Noon - 1pm – Lunch on your own.<br />
<br>1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.<br />
<br>2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.<br />
<br>4:45pm - 5pm - Review and wrap up.<br />
<br />
=== Sunday, February 8 ===<br />
8:30am - Review progress to date; introductions of new participants<br />
<br> 8:45am - noon - Continue working on class hierarchy and properties<br />
<br> noon - 1pm - Lunch on your own<br />
<br> 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?<br />
<br> 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups<br />
<br> 4:30pm - 5pm -- Return to smaller groups, make suggested edits, finalize documentation <br />
<br />
== Summary & Background==<br />
The PBCore RDF Ontology Hackathon is occurring out of a growing need for PBCore users to express their metadata in RDF. A number of PBCore users contribute to and are part of the [http://projecthydra.org/ Project Hydra] community, a collaborative, open source effort to build digital repository software solutions at archives institutions. Hydra is built on a framework that uses Fedora Commons as the repository for storing metadata. Many users are seeking to update their Fedora repositories to the latest version (Fedora 4), which provides a great opportunity to develop an RDF data structure. If PBCore had an RDF ontology, it would be easier for PBCore users to take full advantage of Fedora 4 capabilities in managing data and encourage adoption of Fedora 4.<br />
<br />
<br>We envision building upon existing knowledge bases that are already well established. In particular, we hope to harmonize the EBUCore ontology with PBCore and determine what existing terms from the EBUCore vocabulary can be re-used, and what concepts may be unique to PBCore that would deem the need for additional terms.<br />
<br />
<br>[http://www.pbcore.org PBCore] is a metadata schema for audiovisual materials. Its original development in 2004 was funded by the Corporation for Public Broadcasting, with a goal of creating a metadata standard for public broadcasters to share information about their video and audio assets within and among public media stations. Since its conception, PBCore has been adopted by a growing number of audiovisual archives and organizations that needed a way to describe their archival audiovisual collections. The schema has been reviewed multiple times and is currently in further development via the [http://www.americanarchive.org American Archive of Public Broadcasting] and the [http://amianet.org/ Association of Moving Image Archivists (AMIA)] PBCore Advisory Subcommittee. <br />
<br />
<br>The Schema Team is working on an updated version of PBCore (PBCore 2.1), the changes of which will consist of minor tweaks and bug fixes, and is expected to be released in March 2015. Other Teams on the Subcommittee are working on PBCore outreach, education, documentation, and a new website.<br />
<br />
== Working Groups ==<br />
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.<br />
<br />
=== Intellectual Content Working Group ===<br />
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.<br />
<br />
==== Participants ====<br />
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]<br />
<br />
Julie Hardesty, [https://twitter.com/jlhardes @jlhardes]<br />
<br />
=== Intellectual Property Working Group ===<br />
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles. <br />
<br />
==== Participants ====<br />
Rebecca Guenther, LC and NYU/MIAP, @rguenther52, rguenther52@gmail.com<br />
<br />
=== Instantiation Working Group === <br />
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.<br />
<br />
==== Participants ====<br />
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]<br />
<br />
Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]<br />
<br />
=== Essence Track Working Group ===<br />
This group will focus on the essence track part of the knowledge base.<br />
<br />
==== Participants ====<br />
Name, Institution, Twitter handle/email address<br />
<br />
=== Documentation Working Group ===<br />
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the documentation working group.<br />
<br />
==== Participants ====<br />
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]<br />
<br />
== Suggested Reading & Preparation ==<br />
* Sign up for a Code4Lib wiki account (if you don't already have an account)<br />
* Everyone should read at least the first chapters of the Allemang book, Semantic Web for the Working Ontologist:<br />
http://www.worldcat.org/title/semantic-web-for-the-working-ontologist-effective-modeling-in-rdfs-and-owl/oclc/73393667<br />
* Everyone should understand the RDF meaning of classes, properties, domain and range before beginning. (cf: http://kcoyle.blogspot.com/2014/11/classes-in-rdf.html)<br />
* Review PBCore Schema: http://pbcore.org/elements/<br />
* Read this awesome Ontology Development 101 publication: http://protege.stanford.edu/publications/ontology_development/ontology101-noy-mcguinness.html<br />
* Read about RDF on the W3C website: http://www.w3.org/RDF/<br />
* Read this article: "Multi-Entity Models of Resource Description in the Semantic Web: A comparison of FRBR, RDA and BIBFRAME." (http://kcoyle.net/LHTv32n4preprint.pdf)<br />
* Review existing ontologies<br />
** EBUCore: http://www.ebu.ch/metadata/ontologies/ebucore/index.html and http://www.ebu.ch/metadata/ontologies/ebucore/ebucore.rdf<br />
** MODS: http://www.loc.gov/standards/mods/modsrdf/<br />
** BIBFRAME: http://www.loc.gov/bibframe/<br />
** DC Terms: http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=terms#<br />
** FOAF: http://www.foaf-project.org/<br />
**PREMIS: http://id.loc.gov/ontologies/premis.html<br />
<br />
== Tips and Advice from the Community == <br />
<br />
==== from Karen Coyle ==== <br />
* Don't lean too heavily on Protege. Protege is very OWL-oriented and can lead one far astray. It's easy to click on check boxes without knowing what they really mean. Do as much development as you can without using Protege, and do your development in RDFS not OWL. Later you can use Protege to check your work, or to complete the code.<br />
<br />
* Develop in ntriples or turtle but NOT rdf/xml. RDF differs from XML in some fundamental ways that are not obvious, and developing in rdf/xml masks these differences and often leads to the development of not very good ontologies.<br />
<br />
==== from Jean-Pierre Evain ====<br />
<br />
* I have personally no issue whatsoever with Protégé or RDF/XML for the type of ontology we seem to be aiming at<br />
<br />
* I agree that OWL is probably not required. But this doesn't prevent using Protégé. Of course one needs to know what is specific to OWL.<br />
<br />
== Need more info? ==<br />
If you have questions or need more information, feel free to contact Casey Davis at casey_davis [at] wgbh [dot] org.</div>JulietHardestyhttps://wiki.code4lib.org/index.php?title=PBCore_RDF_Hackathon&diff=42394PBCore RDF Hackathon2015-01-07T18:32:50Z<p>JulietHardesty: /* Participants */</p>
<hr />
<div>SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing<br />
<br>Please also fill out this form: http://goo.gl/forms/nAvL52W9MI<br />
<br><br><br />
'''>>> When, Where, What time?'''<br />
<br>Date: '''Saturday & Sunday, February 7-8, 2015'''<br />
<br>Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)<br />
<br>Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''<br />
<br>hashtag: '''#PBCoreRDF15'''<br />
<br />
== What will be the format of the event? ==<br />
<br />
In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.<br />
<br><br />
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.<br />
=== Saturday, February 7 ===<br />
8:30am – Welcome, introductions<br />
<br>9am - 9:45am - Discuss and determine the domain and scope of the ontology<br />
<br>9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, BIBFRAME, PREMIS) to determine what can be used for PBCore. Snacks and coffee to be served.<br />
<br>Noon - 1pm – Lunch on your own.<br />
<br>1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.<br />
<br>2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.<br />
<br>4:45pm - 5pm - Review and wrap up.<br />
<br />
=== Sunday, February 8 ===<br />
8:30am - Review progress to date; introductions of new participants<br />
<br> 8:45am - noon - Continue working on class hierarchy and properties<br />
<br> noon - 1pm - Lunch on your own<br />
<br> 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?<br />
<br> 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups<br />
<br> 4:30pm - 5pm -- Return to smaller groups, make suggested edits, finalize documentation <br />
<br />
== Summary & Background==<br />
The PBCore RDF Ontology Hackathon is occurring out of a growing need for PBCore users to express their metadata in RDF. A number of PBCore users contribute to and are part of the [http://projecthydra.org/ Project Hydra] community, a collaborative, open source effort to build digital repository software solutions at archives institutions. Hydra is built on a framework that uses Fedora Commons as the repository for storing metadata. Many users are seeking to update their Fedora repositories to the latest version (Fedora 4), which provides a great opportunity to develop an RDF data structure. If PBCore had an RDF ontology, it would be easier for PBCore users to take full advantage of Fedora 4 capabilities in managing data and encourage adoption of Fedora 4.<br />
<br />
<br>We envision building upon existing knowledge bases that are already well established. In particular, we hope to harmonize the EBUCore ontology with PBCore and determine what existing terms from the EBUCore vocabulary can be re-used, and what concepts may be unique to PBCore that would deem the need for additional terms.<br />
<br />
<br>[http://www.pbcore.org PBCore] is a metadata schema for audiovisual materials. Its original development in 2004 was funded by the Corporation for Public Broadcasting, with a goal of creating a metadata standard for public broadcasters to share information about their video and audio assets within and among public media stations. Since its conception, PBCore has been adopted by a growing number of audiovisual archives and organizations that needed a way to describe their archival audiovisual collections. The schema has been reviewed multiple times and is currently in further development via the [http://www.americanarchive.org American Archive of Public Broadcasting] and the [http://amianet.org/ Association of Moving Image Archivists (AMIA)] PBCore Advisory Subcommittee. <br />
<br />
<br>The Schema Team is working on an updated version of PBCore (PBCore 2.1), the changes of which will consist of minor tweaks and bug fixes, and is expected to be released in March 2015. Other Teams on the Subcommittee are working on PBCore outreach, education, documentation, and a new website.<br />
<br />
== Working Groups ==<br />
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.<br />
<br />
=== Intellectual Content Working Group ===<br />
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.<br />
<br />
==== Participants ====<br />
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]<br />
<br />
=== Intellectual Property Working Group ===<br />
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles. <br />
<br />
==== Participants ====<br />
Rebecca Guenther, LC and NYU/MIAP, @rguenther52, rguenther52@gmail.com<br />
<br />
=== Instantiation Working Group === <br />
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.<br />
<br />
==== Participants ====<br />
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]<br />
<br />
Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]<br />
<br />
=== Essence Track Working Group ===<br />
This group will focus on the essence track part of the knowledge base.<br />
<br />
==== Participants ====<br />
Name, Institution, Twitter handle/email address<br />
<br />
=== Documentation Working Group ===<br />
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the documentation working group.<br />
<br />
==== Participants ====<br />
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]<br />
<br />
== Suggested Reading & Preparation ==<br />
* Sign up for a Code4Lib wiki account (if you don't already have an account)<br />
* Everyone should read at least the first chapters of the Allemang book, Semantic Web for the Working Ontologist:<br />
http://www.worldcat.org/title/semantic-web-for-the-working-ontologist-effective-modeling-in-rdfs-and-owl/oclc/73393667<br />
* Everyone should understand the RDF meaning of classes, properties, domain and range before beginning. (cf: http://kcoyle.blogspot.com/2014/11/classes-in-rdf.html)<br />
* Review PBCore Schema: http://pbcore.org/elements/<br />
* Read this awesome Ontology Development 101 publication: http://protege.stanford.edu/publications/ontology_development/ontology101-noy-mcguinness.html<br />
* Read about RDF on the W3C website: http://www.w3.org/RDF/<br />
* Read this article: "Multi-Entity Models of Resource Description in the Semantic Web: A comparison of FRBR, RDA and BIBFRAME." (http://kcoyle.net/LHTv32n4preprint.pdf)<br />
* Review existing ontologies<br />
** EBUCore: http://www.ebu.ch/metadata/ontologies/ebucore/index.html and http://www.ebu.ch/metadata/ontologies/ebucore/ebucore.rdf<br />
** MODS: http://www.loc.gov/standards/mods/modsrdf/<br />
** BIBFRAME: http://www.loc.gov/bibframe/<br />
** DC Terms: http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=terms#<br />
** FOAF: http://www.foaf-project.org/<br />
**PREMIS: http://id.loc.gov/ontologies/premis.html<br />
<br />
== Tips and Advice from the Community == <br />
<br />
==== from Karen Coyle ==== <br />
* Don't lean too heavily on Protege. Protege is very OWL-oriented and can lead one far astray. It's easy to click on check boxes without knowing what they really mean. Do as much development as you can without using Protege, and do your development in RDFS not OWL. Later you can use Protege to check your work, or to complete the code.<br />
<br />
* Develop in ntriples or turtle but NOT rdf/xml. RDF differs from XML in some fundamental ways that are not obvious, and developing in rdf/xml masks these differences and often leads to the development of not very good ontologies.<br />
<br />
==== from Jean-Pierre Evain ====<br />
<br />
* I have personally no issue whatsoever with Protégé or RDF/XML for the type of ontology we seem to be aiming at<br />
<br />
* I agree that OWL is probably not required. But this doesn't prevent using Protégé. Of course one needs to know what is specific to OWL.<br />
<br />
== Need more info? ==<br />
If you have questions or need more information, feel free to contact Casey Davis at casey_davis [at] wgbh [dot] org.</div>JulietHardestyhttps://wiki.code4lib.org/index.php?title=PBCore_RDF_Hackathon&diff=42393PBCore RDF Hackathon2015-01-07T18:30:57Z<p>JulietHardesty: </p>
<hr />
<div>SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing<br />
<br>Please also fill out this form: http://goo.gl/forms/nAvL52W9MI<br />
<br><br><br />
'''>>> When, Where, What time?'''<br />
<br>Date: '''Saturday & Sunday, February 7-8, 2015'''<br />
<br>Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)<br />
<br>Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''<br />
<br>hashtag: '''#PBCoreRDF15'''<br />
<br />
== What will be the format of the event? ==<br />
<br />
In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.<br />
<br><br />
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.<br />
=== Saturday, February 7 ===<br />
8:30am – Welcome, introductions<br />
<br>9am - 9:45am - Discuss and determine the domain and scope of the ontology<br />
<br>9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, BIBFRAME, PREMIS) to determine what can be used for PBCore. Snacks and coffee to be served.<br />
<br>Noon - 1pm – Lunch on your own.<br />
<br>1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.<br />
<br>2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.<br />
<br>4:45pm - 5pm - Review and wrap up.<br />
<br />
=== Sunday, February 8 ===<br />
8:30am - Review progress to date; introductions of new participants<br />
<br> 8:45am - noon - Continue working on class hierarchy and properties<br />
<br> noon - 1pm - Lunch on your own<br />
<br> 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?<br />
<br> 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups<br />
<br> 4:30pm - 5pm -- Return to smaller groups, make suggested edits, finalize documentation <br />
<br />
== Summary & Background==<br />
The PBCore RDF Ontology Hackathon is occurring out of a growing need for PBCore users to express their metadata in RDF. A number of PBCore users contribute to and are part of the [http://projecthydra.org/ Project Hydra] community, a collaborative, open source effort to build digital repository software solutions at archives institutions. Hydra is built on a framework that uses Fedora Commons as the repository for storing metadata. Many users are seeking to update their Fedora repositories to the latest version (Fedora 4), which provides a great opportunity to develop an RDF data structure. If PBCore had an RDF ontology, it would be easier for PBCore users to take full advantage of Fedora 4 capabilities in managing data and encourage adoption of Fedora 4.<br />
<br />
<br>We envision building upon existing knowledge bases that are already well established. In particular, we hope to harmonize the EBUCore ontology with PBCore and determine what existing terms from the EBUCore vocabulary can be re-used, and what concepts may be unique to PBCore that would deem the need for additional terms.<br />
<br />
<br>[http://www.pbcore.org PBCore] is a metadata schema for audiovisual materials. Its original development in 2004 was funded by the Corporation for Public Broadcasting, with a goal of creating a metadata standard for public broadcasters to share information about their video and audio assets within and among public media stations. Since its conception, PBCore has been adopted by a growing number of audiovisual archives and organizations that needed a way to describe their archival audiovisual collections. The schema has been reviewed multiple times and is currently in further development via the [http://www.americanarchive.org American Archive of Public Broadcasting] and the [http://amianet.org/ Association of Moving Image Archivists (AMIA)] PBCore Advisory Subcommittee. <br />
<br />
<br>The Schema Team is working on an updated version of PBCore (PBCore 2.1), the changes of which will consist of minor tweaks and bug fixes, and is expected to be released in March 2015. Other Teams on the Subcommittee are working on PBCore outreach, education, documentation, and a new website.<br />
<br />
== Working Groups ==<br />
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.<br />
<br />
=== Intellectual Content Working Group ===<br />
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.<br />
<br />
==== Participants ====<br />
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]<br />
<br />
=== Intellectual Property Working Group ===<br />
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles. <br />
<br />
==== Participants ====<br />
Rebecca Guenther, LC and NYU/MIAP, @rguenther52, rguenther52@gmail.com<br />
<br />
=== Instantiation Working Group === <br />
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.<br />
<br />
==== Participants ====<br />
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]<br />
Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]<br />
<br />
=== Essence Track Working Group ===<br />
This group will focus on the essence track part of the knowledge base.<br />
<br />
==== Participants ====<br />
Name, Institution, Twitter handle/email address<br />
<br />
=== Documentation Working Group ===<br />
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the documentation working group.<br />
<br />
==== Participants ====<br />
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]<br />
<br />
== Suggested Reading & Preparation ==<br />
* Sign up for a Code4Lib wiki account (if you don't already have an account)<br />
* Everyone should read at least the first chapters of the Allemang book, Semantic Web for the Working Ontologist:<br />
http://www.worldcat.org/title/semantic-web-for-the-working-ontologist-effective-modeling-in-rdfs-and-owl/oclc/73393667<br />
* Everyone should understand the RDF meaning of classes, properties, domain and range before beginning. (cf: http://kcoyle.blogspot.com/2014/11/classes-in-rdf.html)<br />
* Review PBCore Schema: http://pbcore.org/elements/<br />
* Read this awesome Ontology Development 101 publication: http://protege.stanford.edu/publications/ontology_development/ontology101-noy-mcguinness.html<br />
* Read about RDF on the W3C website: http://www.w3.org/RDF/<br />
* Read this article: "Multi-Entity Models of Resource Description in the Semantic Web: A comparison of FRBR, RDA and BIBFRAME." (http://kcoyle.net/LHTv32n4preprint.pdf)<br />
* Review existing ontologies<br />
** EBUCore: http://www.ebu.ch/metadata/ontologies/ebucore/index.html and http://www.ebu.ch/metadata/ontologies/ebucore/ebucore.rdf<br />
** MODS: http://www.loc.gov/standards/mods/modsrdf/<br />
** BIBFRAME: http://www.loc.gov/bibframe/<br />
** DC Terms: http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=terms#<br />
** FOAF: http://www.foaf-project.org/<br />
**PREMIS: http://id.loc.gov/ontologies/premis.html<br />
<br />
== Tips and Advice from the Community == <br />
<br />
==== from Karen Coyle ==== <br />
* Don't lean too heavily on Protege. Protege is very OWL-oriented and can lead one far astray. It's easy to click on check boxes without knowing what they really mean. Do as much development as you can without using Protege, and do your development in RDFS not OWL. Later you can use Protege to check your work, or to complete the code.<br />
<br />
* Develop in ntriples or turtle but NOT rdf/xml. RDF differs from XML in some fundamental ways that are not obvious, and developing in rdf/xml masks these differences and often leads to the development of not very good ontologies.<br />
<br />
==== from Jean-Pierre Evain ====<br />
<br />
* I have personally no issue whatsoever with Protégé or RDF/XML for the type of ontology we seem to be aiming at<br />
<br />
* I agree that OWL is probably not required. But this doesn't prevent using Protégé. Of course one needs to know what is specific to OWL.<br />
<br />
== Need more info? ==<br />
If you have questions or need more information, feel free to contact Casey Davis at casey_davis [at] wgbh [dot] org.</div>JulietHardesty