Code4Lib - User contributions [en]

2023 Conference Volunteers

2023-03-08T14:51:13Z

HectorCorrea:

= Code4Lib 2023 Conference Volunteers =

Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2023_Conference_Committees|conference planning committees]].

== Community Support Volunteers ==

See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.

== Concierge/Local Guides ==
Available after sessions to direct people to evening activities and local points of interest, etc.

If you're local to the area (or know it very well), you can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.

* ''Your Name Here''

Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag

== Conference Logistics & Registration ==
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.

Onsite Volunteer Committee Coordinator: Hardy Pottinger

8am - 9am Wednesday, day one:
* Hardy Pottinger
* ''Your Name Here''

8am - 9am Thursday, day two:
* Hardy Pottinger
* Hector Correa

== Social Events ==

Onsite Volunteer Committee Coordinator:

Wednesday, Day One:
* ''Your Name Here''

Thursday, Day Two:
* 7am Run/Walk organizer: Eric Hellman
* 11pm Game Night Cleanup: ''Your Name Here''
* 11pm Game Night Cleanup: ''Your Name Here''

== Social Networking ==

Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)

Onsite Volunteer Committee Coordinator:

Tuesday, Preconference Day:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day One:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Day Two:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Friday, Day Three:
* AM volunteer: ''Your Name Here''

== Mic-minders ==

Ask questions on mic on behalf of community (because of distance, mic aversion, etc). Asking questions on behalf of remote attendees passed to the slack channel: #code4libcon

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Wednesday, Day One:
* AM volunteer: Maccabee Levine
* AM volunteer: ''Your Name Here''
* PM volunteer: Hector Correa
* PM volunteer: ''Your Name Here''

Thursday, Day Two:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Friday, Day Three:
* AM volunteer: Maccabee Levine
* AM volunteer: ''Your Name Here''

== Livestream Assistants (Onsite) ==

Livestream assistants will help the livestream technicians in the presentation room, troubleshooting video and audio connections at the podium, and monitoring the encoding computer. Two people are needed for each shift. You are welcome to sign up for multiple shifts!

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Wednesday, Day One:
* AM Volunteer: ''Your Name Here''
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Thursday, Day Two:
* AM Volunteer: ''Your Name Here''
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Friday, Day Three:
* AM Volunteer: ''Your Name Here''
* AM Volunteer: ''Your Name Here''

== Livestream QA (Remote) ==
Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).

To report a problem (even if you're not an "official" volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Wednesday, Day One:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Friday, Day Three:
* AM Volunteer: ''Your Name Here''

== IRC/Slack (Technical) ==
Access: Look into technology/procedures to make connecting to, and maintaining a connection to, IRC/Slack less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people. Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

Onsite Volunteer Committee Coordinator:

* Before the conference: ''Your Name Here''
* During the conference: ''Your Name Here''

==MCs==

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Wednesday, Day One:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: Eric Hellman

Thursday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: Hardy Pottinger

Friday, Day Three:
* AM Volunteer: ''Your Name Here''

== Session Timers ==
Assist the AV crew with running the talk timer. They will have a digital sign so this volunteer functions mostly as a backup who is prepared in case the system fails or someone goes over time without noticing the signage.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Wednesday, Day One:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Thursday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Friday, Day Three:
* AM Volunteer: ''Your Name Here''

== The Whatever Crew ==
Volunteers who are willing to help with various tasks as needed during the conference.

* ''Your Name Here''
* ''Your Name Here''
* ''Your Name Here''

future potential volunteers:

* ''Your Name Here''

podium tech help:

* ''Your Name Here''

[[Category: Code4Lib2023]]

2023 Conference Volunteers

2023-03-07T14:45:06Z

HectorCorrea: /* Mic-minders */

= Code4Lib 2023 Conference Volunteers =

Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2023_Conference_Committees|conference planning committees]].

== Community Support Volunteers ==

See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.

== Concierge/Local Guides ==
Available after sessions to direct people to evening activities and local points of interest, etc.

If you're local to the area (or know it very well), you can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.

* ''Your Name Here''

Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag

== Conference Logistics & Registration ==
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

8am - 9am Wednesday, day one:
* Hardy Pottinger
* ''Your Name Here''

8am - 9am Thursday, day two:
* Hardy Pottinger
* ''Your Name Here''

== Social Events ==

Onsite Volunteer Committee Coordinator:

Wednesday, Day One:
* ''Your Name Here''

Thursday, Day Two:
* 11pm Game Night Cleanup: ''Your Name Here''
* 11pm Game Night Cleanup: ''Your Name Here''

== Social Networking ==

Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)

Onsite Volunteer Committee Coordinator:

Tuesday, Preconference Day:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day One:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Day Two:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Friday, Day Three:
* AM volunteer: ''Your Name Here''

== Mic-minders ==

Ask questions on mic on behalf of community (because of distance, mic aversion, etc). Asking questions on behalf of remote attendees passed to the slack channel: #code4libcon

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Wednesday, Day One:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: Hector Correa
* PM volunteer: ''Your Name Here''

Thursday, Day Two:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Friday, Day Three:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''

== Livestream Assistants (Onsite) ==

Livestream assistants will help the livestream technicians in the presentation room, troubleshooting video and audio connections at the podium, and monitoring the encoding computer. Two people are needed for each shift. You are welcome to sign up for multiple shifts!

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Wednesday, Day One:
* AM Volunteer: ''Your Name Here''
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Thursday, Day Two:
* AM Volunteer: ''Your Name Here''
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Friday, Day Three:
* AM Volunteer: ''Your Name Here''
* AM Volunteer: ''Your Name Here''

== Livestream QA (Remote) ==
Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).

To report a problem (even if you're not an "official" volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Wednesday, Day One:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Friday, Day Three:
* AM Volunteer: ''Your Name Here''

== IRC/Slack (Technical) ==
Access: Look into technology/procedures to make connecting to, and maintaining a connection to, IRC/Slack less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people. Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

Onsite Volunteer Committee Coordinator:

* Before the conference: ''Your Name Here''
* During the conference: ''Your Name Here''

==MCs==

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Wednesday, Day One:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Thursday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: Hardy Pottinger

Friday, Day Three:
* AM Volunteer: ''Your Name Here''

== Session Timers ==
Assist the AV crew with running the talk timer. They will have a digital sign so this volunteer functions mostly as a backup who is prepared in case the system fails or someone goes over time without noticing the signage.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Wednesday, Day One:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Thursday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Friday, Day Three:
* AM Volunteer: ''Your Name Here''

== The Whatever Crew ==
Volunteers who are willing to help with various tasks as needed during the conference.

* ''Your Name Here''
* ''Your Name Here''
* ''Your Name Here''

future potential volunteers:

* ''Your Name Here''

podium tech help:

* ''Your Name Here''

[[Category: Code4Lib2023]]

2023 Conference Volunteers

2023-03-07T14:32:52Z

HectorCorrea: Changed hashtag to #c4l23 since to follow the convention of previous years and is already in use in Mastodon

= Code4Lib 2023 Conference Volunteers =

'''DRAFT/Work in Progress'''

Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2023_Conference_Committees|conference planning committees]].

== Community Support Volunteers ==

See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.

== Concierge/Local Guides ==
Available after sessions to direct people to evening activities and local points of interest, etc.

If you're local to the area (or know it very well), you can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.

* ''Your Name Here''

Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag

== Conference Logistics & Registration ==
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

8am - 9am Wednesday, day one:
* Hardy Pottinger
* ''Your Name Here''

8am - 9am Thursday, day two:
* Hardy Pottinger
* ''Your Name Here''

== Social Events ==

Onsite Volunteer Committee Coordinator:

Wednesday, Day One:
* ''Your Name Here''

Thursday, Day Two:
* 11pm Game Night Cleanup: ''Your Name Here''
* 11pm Game Night Cleanup: ''Your Name Here''

== Social Networking ==

Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)

Onsite Volunteer Committee Coordinator:

Tuesday, Preconference Day:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day One:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Day Two:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Friday, Day Three:
* AM volunteer: ''Your Name Here''

== Mic-minders ==

Ask questions on mic on behalf of community (because of distance, mic aversion, etc). Asking questions on behalf of remote attendees passed to the slack channel: #code4libcon

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Wednesday, Day One:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Day Two:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Friday, Day Three:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''

== Livestream Assistants (Onsite) ==

Livestream assistants will help the livestream technicians in the presentation room, troubleshooting video and audio connections at the podium, and monitoring the encoding computer. Two people are needed for each shift. You are welcome to sign up for multiple shifts!

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Wednesday, Day One:
* AM Volunteer: ''Your Name Here''
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Thursday, Day Two:
* AM Volunteer: ''Your Name Here''
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Friday, Day Three:
* AM Volunteer: ''Your Name Here''
* AM Volunteer: ''Your Name Here''

== Livestream QA (Remote) ==
Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).

To report a problem (even if you're not an "official" volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Wednesday, Day One:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Friday, Day Three:
* AM Volunteer: ''Your Name Here''

== IRC/Slack (Technical) ==
Access: Look into technology/procedures to make connecting to, and maintaining a connection to, IRC/Slack less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people. Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

Onsite Volunteer Committee Coordinator:

* Before the conference: ''Your Name Here''
* During the conference: ''Your Name Here''

==MCs==

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Wednesday, Day One:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Thursday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: Hardy Pottinger

Friday, Day Three:
* AM Volunteer: ''Your Name Here''

== Session Timers ==
Assist the AV crew with running the talk timer. They will have a digital sign so this volunteer functions mostly as a backup who is prepared in case the system fails or someone goes over time without noticing the signage.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Wednesday, Day One:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Thursday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Friday, Day Three:
* AM Volunteer: ''Your Name Here''

== The Whatever Crew ==
Volunteers who are willing to help with various tasks as needed during the conference.

* ''Your Name Here''
* ''Your Name Here''
* ''Your Name Here''

future potential volunteers:

* ''Your Name Here''

podium tech help:

* ''Your Name Here''

[[Category: Code4Lib2023]]

Working with MARC

2020-03-12T21:02:35Z

HectorCorrea: Added a couple of libraries

MARC stands for Machine Readable Cataloging, and many folks in the code4lib community find themselves working with MARC records at some point. This page is meant to be a round-up of the tools for working with MARC. If you want a general introduction to the standard, [http://en.wikipedia.org/wiki/MARC_standards the Wikipedia article] is a good place to start. MARC data is usually expressed either in ISO 2709 ("binary") form or MARCXML form.

__TOC__

== Reference information ==

* [http://www.loc.gov/marc/ Library of Congress MARC Standards Pages] (covers MARC21; formerly USMARC)
* [http://www.bl.uk/bibliographic/ukmarc.html British Library UKMARC Pages]
* [http://archive.ifla.org/VI/3/p1996-1/sec-uni.htm IFLA UNIMARC Pages]
* [http://www.oclc.org/content/bibformats/en.html OCLC MARC Pages]

== Desktop tools ==

* [http://marcedit.reeset.net/ MarcEdit]

* [http://csharpmarc.net/ C# MARC Editor]: is a simple and light weight MARC Editor for Windows

* [http://www.auto-graphics.com/download/SHOWMARC.EXE Showmarc]: is a DOS program that will show all the MARC fields used and how many times each is used.

* [http://rossjohnson.homemail.com.au/MARCRTP/ MARC Record Translation Program] (MARC RTP) is a command line utility that shows fields and subfields used in a collection of MARC records and then converts, and selectively imports, into databases built with general-purpose applications.

* The [http://www.loc.gov/marc/marc-functional-analysis/tool.html FRBR Display Tool] takes a file of MARC records and creats XML and HTML files arranged using the Functional Requirements for Bibliographic Records principles.

* [http://mysite.du.edu/~ttyler/freeware/marcxgen.htm MarcXGen] is a Marc URL extractor and HTML generator. Useful for link checking MARC records.

* [http://www.loc.gov/marc/makrbrkr.html MARCMaker and MARCBreaker] are DOS programs by the Library of Congress for converting MARC records to a text format and back.

* [http://www.bl.uk/bibliographic/usemarcon.html USEMARCON] is a multi-platform rule-based MARC record manipulation program. It is a command-line utility but there is also a GUI for it.

== Getting Marc Indexed for Search Engines ==

=== MARC in Solr ===

* SolrMarc https://github.com/solrmarc/solrmarc

* Solr http://lucene.apache.org/solr

* Catmandu http://librecat.org (provides also loading into ElasticSearch, MongoDB and others)

=== MARC in Zebra ===

* Getting Started with Zebra http://wiki.code4lib.org/index.php/Getting_Started_with_Zebra

* Zebra http://www.indexdata.com/zebra

== MARC Programming Libraries ==

{| class="wikitable sortable"
|-valign="top"
! Project !! Language !! class="unsortable" | Links !! class="unsortable" | Notes
|-valign="top"
| MARC4J || Java || http://marc4j.tigris.org/ ||
|-valign="top"
| javamarc || Java || http://github.com/billdueber/javamarc || Fork of MARC4J
|-valign="top"
| MARC/Perl || Perl || http://marcpm.sf.net || Umbrella project; see also [http://search.cpan.org/search?query=marc&mode=all CPAN]
|-valign="top"
| pymarc || Python || http://github.com/edsu/pymarc/ ||
|-valign="top"
| File_MARC || PHP || http://pear.php.net/package/File_MARC/ || PEAR package; sanctioned fork of PHP-MARC
|-valign="top"
| PHP-MARC || PHP || http://www.emilda.org/index.php?q=php-marc || Abandoned(?); served as basis for File_MARC
|-valign="top"
| ruby-marc || Ruby || http://rubyforge.org/projects/marc/ http://wiki.code4lib.org/index.php/Ruby-marc ||
|-valign="top"
| enhanced-marc || Ruby || http://github.com/rsinger/enhanced-marc || Convenience methods for ruby-marc
|-valign="top"
| marc21 || Scheme || http://code.google.com/p/marc21 ||
|-valign="top"
| marcerl || Erlang || svn://pubserv.oclc.org/marcerl|| Very alpha code
|-valign="top"
| Scala-MARC || Scala || http://github.com/achelous/Scala-MARC ||
|-valign="top"
| MARC Library (SobekCM) || C# || http://sourceforge.net/projects/marclibrary/ || Implemented in .NET 4.0 with LINQ and streams with Z39.50 support
|-valign="top"
| CSharp MARC || C# || http://csharpmarc.net || Based upon File_MARC Pear packaged for PHP, but restyled for use in .NET
|-valign="top"
| MARC.NET || C# || http://github.com/willkurt/MARC.NET || basic start, not thoroughly 'real world' tested
|-valign="top"
| marc_record.js || JavaScript || http://www.pusc.it/bib/mel/marc_record.js (dead link) || Part of [http://www.pusc.it/bib/mel/ MARC Editor Lite] (dead link)
|-valign="top"
| marcjs || JavaScript (node) || https://github.com/fredericd/marcjs ||
|-valign="top"
| USEMARCON || C++ || http://www.nationallibrary.fi/libraries/format/usemarcon.html || A rule-based MARC record conversion library
|-valign="top"
| clj-marc || Clojure || http://github.com/phochste/clj-marc || Basic MARC21 and Aleph500 sequential export parser
|-valign="top"
| MARC4J.Net || C# || https://github.com/mxurshid/MARC4J.Net || https://www.nuget.org/packages/MARC4J.Net
|-valian="top"
| marc4js || JavaScript (Node.js) || https://github.com/jiaola/marc4js || Read/transform/write records with Node stream api. Handles MARC8 and UTF8.
|-valign="top"
| marcli || Go || https://github.com/hectorcorrea/marcli || Command line to parse MARC files
|-valign="top"
| fml || Go || https://github.com/MITLibraries/fml || MARC 21 library for Go
|}

A feed of commit messages and release announcements from many of the projects listed above can be found at http://pipes.yahoo.com/gmcharlt/marctoolchanges.

== Utilities and Frameworks ==
{| class="wikitable sortable"
|-valign="top"
! Project !! Language !! class="unsortable" | Links !! class="unsortable" | Notes
|-valign="top"
| MarcXimiL || Python || http://marcximil.sourceforge.net/ || Bibliographic Similarity Analysis Framework
|-valign="top"
| Catmandu || Perl || http://librecat.org || An ETL-framework to extract, transform and load MARC (and other formats) from/to various databases, indexes
|}

== Getting Sample Data ==

One common question is where to get sample MARC records for testing or playing around with. If you work at a library, chances are good that you can get some records out of your ILS (go ask your systems librarian if you don't know how to do this yourself). If you don't work in a library, you can get [http://www.archive.org/details/ol_data MARC bibliographic records from the Internet Archive].

You can also get [http://www.hathitrust.org/data MARCXML data for titles in HathiTrust through OAI-PMH].

There is a nascent movement within the code4lib community to establish a test set of problematic MARC records, especially records that are representative of the kinds of weirdness that is encountered in real libraries. It is hoped that this could eventually become a test corpus against which to run various MARC processing implementations. For more information, watch [http://www.archive.org/details/MARCTHULU Simon Spero's excellent talk from Code4LibCon 2010].

MARC records for authority data are more common. The [http://www.getty.edu/research/conducting_research/vocabularies/download.html Getty Vocabularies] makes both the The Art & Architecture Thesaurus (AAT) and The Union List of Artist Names (ULAN) freely available. The [http://www.library.northwestern.edu/public/gsafd/ Guidelines On Subject Access To Individual Works Of Fiction, Drama, Etc.] records are available from Northwestern University. The [http://www.nlm.nih.gov/mesh/filelist.html Medical Subject Headings (MeSH)] are available in many formats, one of them being MARC.

== Reporting on How MARC Has Been Used ==

[http://experimental.worldcat.org/marcusage/ MARC Usage in WorldCat] - A site that reports on how MARC has been used within the 300 million record WorldCat database

2020 Keynote Speakers Nominations

2019-10-30T19:40:51Z

HectorCorrea: Added Coraline

Please include a description and any relevant links and try to keep the list in alphabetical order.

The criteria for nominating a candidate to act as keynote are below:
*Speaker’s name (First Name, Last Name)
*Brief description of individual (250-word max)
*Pertinent links (Maximum of 3)
*Contact information of candidate (email address)

''We strongly encourage you to nominate speakers who are local to the Pittsburgh area. If you would prefer to submit a nomination anonymously, please send your nominee(s) to Clara Turp at: [mailto:clara.turp@mcgill.ca clara.turp@mcgill.ca].''

Please follow the formatting guidelines:

<pre>

== Nominee's Name ==

Description of no more than 250 words.

[[Link(s) with contact information for nominee]]

</pre>

__TOC__

==Jane Doe (example)==

Jane works at ________, doing _______.

Some pertinent history/biography/[https://example.com hyperlinks] that elucidates why Jane would be a good keynote speaker.

==Lea Kissner==

Lea formerly built the privacy engineering team at Google (where she specifically valued building a diverse team to capture all sorts of threat models) and is now the Chief Privacy Officer at Humu and cofounder of the [https://www.usenix.org/conference/pepr19/ USENIX Conference on Privacy Engineering Practice and Respect]. She's whip-smart, candid, and funny.

[https://twitter.com/leakissner Twitter]

== James Mickens ==

James Mickens is a computer science professor and researcher currently at Harvard University and formerly of Microsoft Research. A well-travelled conference speaker, James has given keynotes and presentations from Oslo to Sidney, with hilarious titles such as "Life is Terrible: Let's Talk About the Web," and "Life As A Developer: My Code Does Not Work Because I Am A Victim Of Complex Societal Factors That Are Beyond My Control." James' presentation style reveals a breadth of experience in technology that few possess, and a zany and brilliant sense of humor.

[https://mickens.seas.harvard.edu/ James Mickens at Harvard University ]

[https://twitter.com/notjamesmickens Twitter]

[https://www.youtube.com/watch?v=7Nj9ZjwOdFQ NDC Sydney Keynote]

(I am currently auditing Prof. Mickens' class at Harvard -- can confirm he is like this all the time -- would be willing to speak to him personally. --andromeda)

==Karen Sandler==

"Karen Sandler is the executive director of the Software Freedom Conservancy, former executive director of the GNOME Foundation, an attorney, and former general counsel of the Software Freedom Law Center." (per [https://en.wikipedia.org/wiki/Karen_Sandler wikipedia]) She's known for advocacy on copyleft and other copyright issues as well as on free software more generally; notably, e.g., because proprietary software means she cannot audit the implantable medical device that keeps her alive ([https://www.youtube.com/watch?v=GcWlD2Y6HNM OSCON talk]). The [https://sfconservancy.org/about/ Software Freedom Conservancy] is a fiscal sponsor, copyright holder & advocate, etc. for open source software projects. Sandler also co-organizes Outreachy, a paid internship program that particularly encourages people from underrepresented genders and races to contribute to FOSS, and was formerly on the advisory board of the Ada Initiative. She teaches entertainment law at Columbia from a copyright-rebel perspective.

kms47@columbia.edu

==Leo Lo ==

Leo Lo is the Associate University Librarian for learning and undergraduate services at Penn State University Libraries. Leo is a talented presenter, creative thinker and offers very interesting ideas relating to organizational research and development, appreciative inquiry, fostering collaborative works and communications including one's strengths and gifts to the organization. He would make an excellent speaker for Code4Lib when connecting to bigger frameworks within our communities/workflows.

More on [https://news.psu.edu/story/553306/2019/01/08/academics/lo-named-libraries-wide-associate-dean-learning-undergraduate Penn State News], [https://www.linkedin.com/in/leoslo/ Linked In], [https://digitalcommons.odu.edu/do/search/?q=author_lname%3A%22Lo%22%20author_fname%3A%22Leo%22&start=0&context=7048263&facet= ODU digital commons]

== Chuck Pell ==

"A confessed 'congenital geek,' Chuck is inventor, artist, scientist and expressive raconteur. As a practitioner of Design Coup d'œil (the habit of seeing overarching structural issues at a glance), Chuck seeks the essential core of any system, whether science, art, or technology. He is most at home in novel situations, figuring things out on the fly. These tendencies have led Chuck to garner experience in surgical robotics, functional morphology, biomechanics, fluid dynamics, miniature robotics, autonomous underwater vehicles, ballistics, maritime communications, entertainment effects, teaching, design (graphic, exhibit and industrial) and filmmaking. Never at rest, he’s had 100 shows of his paintings and sculpture, with dozens of papers published in biology, engineering and patents issued or pending. Having raised millions for research and now on his third startup, Chuck has the nagging suspicion he’s become a serial entrepreneur." (excerpted from [https://www.tedmed.com/speakers/show?id=6472 Chuck's TEDMED bio])

Chuck Pell is a sculptor, roboticist, Emmy-winning television host, and force of nature. His philosophies towards creativity and invention include: uncover hidden assumptions, pursue surprise, and "fail early and often, when it's cheap." His passionate approach to real-world problem solving has a lot to offer the world of GLAM-tech; combined with an avowed love of technology, libraries, and knowledge generally, he is sure to bring a wealth of insight and creativity to the Code4Lib community. Chuck is 1/4 of the way to an [https://en.wikipedia.org/wiki/List_of_people_who_have_won_Academy,_Emmy,_Grammy,_and_Tony_Awards EGOT] and is the consulting scientist for an asteroid mining company.

* See [https://www.tedmed.com/talks/show?id=6987&videoId=6776 Chuck's TEDMED talk on the future of surgery] (cw: contains brief footage and schematics of surgical procedures)
* [https://www.xplorationstation.com/show/Xploration-Earth-2050 Xploration Earth 2050]

Contact Chuck via [https://physcient.com/contact-us/ Physcient, Inc.]

== Kate Deibel ==
Kate Deibel, PhD, is one of the leading advocates for accessibility in the Code4Lib community and libraries in general. Aside from the fun and informative talks and workshops she has given at Code4Lib, she is also known for her activity on Slack and the mailing list where she ardently calls out issues of diversity and inclusion. By challenging the assumptions that we make about accessibility and inclusion and our patrons' experiences with library technology, Kate's work pushes us to be more empathetic, realistic, and creative when we design library systems.

Kate Deibel is currently the Inclusion & Accessibility Librarian at Syracuse University. She earned her PhD in computer science and engineering at the University of Washington in 2011 with a multidisciplinary study of the social and technological factors that hinder adoption of reading technologies among adults with dyslexia, and while working as a web applications specialist at the University of Washington Libraries she focused on ensuring that technologies are effective tools for both library patrons and staff.

*[https://twitter.com/metageeky Kate on Twitter]

*[https://americanlibrariesmagazine.org/blogs/the-scoop/always-use-microphone/ Article on her presentation at ALA Midwinter 2019 on the future of accessibility in libraries]

*Slides from her Midwinter 2019 talk for the Symposium on the Future of Libraries: [https://www.dropbox.com/s/3suokvqtaqlb8aq/deibel-ala-mw-future-disability.pptx?dl=0 Pushing on the Frontier: Disability Access and the Future of Libraries]

== Alison Macrina ==

From LibraryFreedom.org: "Along with founding the Library Freedom Project, Alison is a librarian, internet activist, and a core contributor to The Tor Project. Alison is passionate about fighting surveillance and connecting privacy issues to other struggles for justice. She believes that a world without pervasive surveillance is possible." Library Freedom is a unique, progressive venture in the privacy sphere, putting on training workshops for libraries and librarians as well as advocating for political change.

<blockquote>"DHS (Department of Homeland Security) fought to stop libraries from using privacy technology, but @LibraryFreedom beat them. Librarians are badass." — Edward Snowden</blockquote>

* [https://twitter.com/LibraryFreedom @LibraryFreedom]
* [https://libraryfreedom.org LibraryFreedom.org]

== Matt Zumwalt ==
Currently the Program Manager at Protocol Labs, Matt is one of the most dedicated technologists who sees our current flaws and has shown a strong track record of helping to push the boundaries of how we store and access digital resources. Matt has given multiple Code4lib presentations previously, one of which being the memorable Code4lib 2017 presentation in the context of endangered data sets. Among many professional interests, currently working on IPFS (Inter-Planetary File System), Matt is helping to engineer a novel method of interacting with ethically distributed, peer-to-peer (P2P) resources, in which libraries are another lender in P2P borrowing chain. Matt is one of the most moving speakers. It would be an honor to have Matt Zumwalt as a keynote speaker.

Borrowing from Matt's webpage: "Previously I founded a consulting firm called MediaShelf, created Ruby libraries called active-fedora and om and served as the technical lead for the Hydra Project, which began as a collaboration with Stanford, Univerisity of Virginia, Univerisity of Hull and DuraSpace but has grown to be a large open-source software initiative with over 40 partner institutions and broad adoption among Libraries, Archives and Museums."
*[https://protocol.ai/team/ Protocol Labs]
*[https://flyingzumwalt.com/ Matt Zumwalt]

== Alison Langmead ==
Alison Langmead holds a joint faculty appointment between the Dietrich School of Arts and Sciences and the School of Computing and Information at the University of Pittsburgh. She teaches and researches in the field of the digital humanities, focusing especially on applying digital methods mindfully within the context of visual and material culture studies.
For the Department of Art History and Architecture, Alison serves as the Director of the Visual Media Workshop (VMW). The mission of the VMW is to develop and encourage the creation of innovative methods for producing, disseminating, and preserving the academic work using digital technologies as a fundamental component of our scholarly toolkit. To achieve these objectives, she directs a technologically-focused environment of collaboration and creativity where students and faculty from a number of departments across the University come together to work on projects that apply digital methods and techniques with focus and intention.
For the School of Computing and Information (SCI), Alison researches the relationship between the historical practice of information management and digital computing, both as a historical narrative and also as a complex, changing process in contemporary America. This research, plus all of the theories, concepts, and models that she teaches at SCI, are put into daily practice in her work directing the VMW.

*[https://www.haa.pitt.edu/people/alison-langmead University of Pittsburgh site]
*[https://dl.acm.org/citation.cfm?doid=3093338.3093368 "Extracting Meaningful Data from Decomposing Bodies," one of her many publications showing her interest in the intersection of cultural studies and computing]
*[https://forum2019.diglib.org/speakers/alison-langmead/ The Digital Library Federation's 2019 conference website for her keynote announcement]

== Eric Lidji ==
Eric Lidji is the Director of the Rauh Jewish History Program and Archives at the Heinz History Center in Pittsburgh, Pennsylvania. Since the 2018 Tree of Life synagogue shooting in Pittsburgh's Squirrel Hill neighborhood, he has been collecting both physical items and digital content related to the attack for the Center. His work has been featured in The New York Times, The Atlantic, and he is a regular contributor to the Pittsburgh Jewish Chronicle. He has presented on the Tree of Life archive in the Pittsburgh area, and he would be a great reminder of how our work can have powerful effects.

*[https://www.heinzhistorycenter.org/collections/rauh-jewish-history-program-and-archives/tree-of-life-response/ Heinz History Center link, email contact]
*[https://www.theatlantic.com/politics/archive/2019/10/archivist-squirrel-hill/600637/ Article in The Atlantic]
*[https://www.nytimes.com/2019/10/26/us/Synagogue-shooting-pittsburgh-memorials.html Article in The New York Times]

== Coraline Ada Ehmke ==

From her website: "I am an internationally acclaimed speaker, writer, open source advocate, and developer with over 25 years of experience in software development. I work diligently to promote diversity and inclusivity in open source and the tech industry as a whole. I was recognized for my work with a Ruby Hero award in 2016. I am best known as the creator of the Contributor Covenant, the most popular open source code of conduct in the world, with over 40,000 adoptions including Linux, Golang, JRuby, Swift, F#, and Rails and the entire open source portfolios of companies like Apple, Microsoft, Google, and Intel."

* https://where.coraline.codes/
* https://twitter.com/coralineada/

2019 Keynote Speakers Nominations

2018-10-09T16:54:07Z

HectorCorrea: Added Safiya U. Noble

Nominations for invited speakers/keynotes for Code4Lib 2019 in San José, CA will run until '''October 22, 2018'''.

Please include a description and any relevant links and try to keep the list in alphabetical order.

The criteria for nominating a candidate to act as keynote are below:
*Speaker’s name (First Name, Last Name)
*Brief description of individual (250-word max)
*Pertinent links (Maximum of 3)
*Contact information of candidate (email address)

''We strongly encourage you to nominate speakers who are local to the San José area. If you would prefer to submit a nomination anonymously, please send your nominee(s) to Clara Turp at: [mailto:clara.turp@mcgill.ca clara.turp@mcgill.ca].''

Please follow the formatting guidelines:

<pre>

== Nominee's Name ==

Description of no more than 250 words.

[[Link(s) with contact information for nominee]]

</pre>

__TOC__

==Jane Doe (example)==

Jane works at ________, doing _______.

Some pertinent history/biography/[https://example.com hyperlinks] that elucidates why Jane would be a good keynote speaker.

==Tara Robertson ==

Tara works at Mozilla as the Diversity & Inclusion Strategic Partner. She is tasked with ensuring one of the darlings of the technology industry to be more inclusive, diverse and open. Tara has been championing open communities, open source, open access, and open education prior to her affiliation with Mozilla for over a decade. As the Code4lib community continues to wrestle with these very issues, it is a timely opportunity to invite her to speak to us since we are on the left coast this year.

More on [https://tararobertson.ca Tara].

[https://tararobertson.ca/2016/lita-keynote/ Not all information wants to be free,] LITA Closing Keynote, 2016.

==Mark Matienzo==

Mark works at Stanford as the Collaboration & Interoperability Architect for Digital Library Systems and Services.

Mark has worked at the intersection of technology, libraries, and systems for over a decade, serving as a technologist, advocate, and facilitator for cross-institutional projects. Prior to joining Stanford, Mark worked as an archivist, technologist, and strategist specializing in born-digital materials and metadata management, at institutions including the Digital Public Library of America, Yale University Library, The New York Public Library, and the American Institute of Physics. Mark would be an excellent keynote speaker because their long track record of involvement in cross-disciplinary and intra-institutional initiatives has given them a unique exposure to projects that touch on all aspects of library systems and tools. In addition, they are an outspoken advocate on a wide range of issues including labor, the environment, and leadership in libraries.

More on [https://matienzo.org/ Mark].

==Raj Jayadev==

Raj Jayadev is the cofounder of [https://www.siliconvalleydebug.org/ Silicon Valley De-Bug], a community organizing, advocacy, and multimedia storytelling organization based in San José, California. Since its inception in 2001, Silicon Valley De-Bug has been a platform for Silicon Valley's diverse communities to impact the political, cultural, and social landscape of the region, while also becoming a nationally recognized model for community-based justice work. For nearly fifteen years, the organization has been a platform for the least heard of Silicon Valley — youth, immigrants, low-income workers, the incarcerated — to impact the the political, cultural, and social landscape of the region. Through De-Bug, Jayadev and is colleagues also started a family organizing model called the [https://acjusticeproject.org/ Albert Cobarrubias Justice Project] – a methodology for families and communities to impact the outcome of cases of their loved ones and change the landscape of power in the courts. They call the approach [https://www.participatorydefense.org/ "participatory defense"] and are now implementing the model nationally. Jayadev is a [https://www.macfound.org/fellows/1014/ 2018 MacArthur Foundation Fellow] and has been an [https://www.ashoka.org/en/fellow/raj-jayadev Ashoka Fellow] and a Rosenberg Foundation Leading Edge Fellow. All three recognitions are to support De-Bug’s innovative social justice work both locally and nationally. His writing and work has appeared and been profiled in media outlets such as the New York Times, Time.com, and National Public Radio.

More about [https://aapip.org/our-stories/conversation-with-25-leaders-in-action-raj-jayadev Raj] ([https://acjusticeproject.org/about/contact-us/ contact info]).

==Karla Monterroso==

Karla Monterroso is the CEO of [http://www.code2040.org/ Code2040], a community of Black and Latinx technologists and their allies who are diversifying tech to create a more equitable, inclusive, and prosperous economy. Through high-impact direct service programs, robust in-person and online community engagement, and dynamic storytelling and knowledge sharing, Code2040 empowers and mobilizes diversity champions across the industry. She believes Code2040 sits in the perfect intersection of a skills- and network-building opportunity for Black and Latinx tech talent and a systems-change opportunity for a critical segment of the country's economy. Karla has focused much of her career growing the people and program functions of rapidly scaling social enterprises driving youth advocacy and leadership. Since joining Code2040 in 2014, she has grown the number of students served from 25 to 4,000, ushered in several new successful programs, and stewarded critical organizational development practices and policies around values and racial equity. Her success and insights on racial justice and equity have landed her in publications such as Fast Company, NPR, Bloomberg, and more.

More about [https://twitter.com/karlitaliliana Karla].

==Rick Prelinger==

Rick Prelinger is an archivist, writer, filmmaker, and librarian. He is currently [http://film.ucsc.edu/faculty/rick_prelinger Professor of Film & Digital Media] at University of California, Santa Cruz. His archival work currently focuses on collecting, recontextualizing, and exhibiting home movies and amateur films, and is a renowned speaker on preservation, archives, and material culture in the anthropocene. In 1982, he founded [https://en.wikipedia.org/wiki/Prelinger_Archives Prelinger Archives], a collection of industrial, advertising, educational and amateur films that was acquired by the Library of Congress in 2002. With Megan Prelinger, he is the co-founder of [http://www.prelingerlibrary.org/home/ Prelinger Library], an appropriation-friendly private research library open to the public in downtown San Francisco. Prelinger has also partnered with the Internet Archive (of which he is a board member) to make 2,100 films available online for free viewing, downloading and reuse. His archival feature Panorama Ephemera (2004) played in venues around the world. Prelinger has recently made several film programs that he categorizes as “historical interventions,” called Lost Landscapes of San Francisco (7 annual parts) and Lost Landscapes of Detroit (3 annual parts).

More about [http://prelinger.com/ Rick].

==Safiya U. Noble==

From her website: "Dr. Safiya Umoja Noble is an Assistant Professor at the University of Southern California (USC) Annenberg School of Communication, and is the author of a best-selling book on racist and sexist algorithmic bias in commercial search engines, entitled Algorithms of Oppression: How Search Engines Reinforce Racism. [...] Previously, she was an assistant professor in the Department of Information Studies in the Graduate School of Education and Information Studies at UCLA where she held appointments in the Departments of African American Studies, Gender Studies, and Education."

More about [https://safiyaunoble.com/ Safiya].

[[Category:Code4Lib2019]]

[[Category:Code4Lib2019]]

2015 Lightning Talks

2015-02-11T23:10:16Z

HectorCorrea: Added link to RDF slides

==Lightning Talks==
<big>'''Lightning talk signup will begin after the opening session, on a (physical) sign up board. As spots fill, we'll add them here for convenient reference.'''</big>

==Tuesday 14:30 PM to 15:30 PM==
# Automated Entity Extractions to Relate Library Resources - Kyle Banerjee
# ResCarta Recap
# [https://drive.google.com/file/d/0B6S516ceOR1nalpHOGFJdFVnclk/view?usp=sharing Information Design Thoughts] - Dre
# Vufind & Worldcat Discovery API - Karen Coombs
# [http://ronallo.com/presentations/ Video Accessibility on the Web] - Jason Ronallo
# [https://docs.google.com/presentation/d/11vBKfYbGzp5_gyksPqK1WKLvMVO_aMk03x2PvK1p_u8/view?usp=sharing ILS and Payment Systems] - Josh Weisman
# Fedora 4 Migration - Adam Wead
# [https://gist.github.com/cbeer/4082dd15b62090f94b98 LDPath] - Chris Beer
# [https://drive.google.com/file/d/0B5jVboA5eH6ATHhSRnZCczhvLVE/view?usp=sharing Self-Deposit of Scientific Data] - Darren Hardy
# [http://matienzo.org/c4l15-lightning-talk Bread (How Baking Bread Made Me a Better Programmer)] - Mx Matienzo

==Wednesday 11:00 AM to 12:00 PM==
# [http://bit.ly/rightspres rights metadata] esmé cowles
# [https://speakerdeck.com/nabeta/2014-2015-activities-of-code4lib-japan 2014-2015 Activities around code4lib Japan] - Kosuke Tanabe
# [https://docs.google.com/presentation/d/1oJtzHWcIie-vLCpU-c_T6GaUCkWrPp0E9QDYqXiiH3M/edit?usp=sharing Arduino as a Learning Platform] - Dominic Bordelon
# [http://ablwr.github.io/c4l_preforma/#/ PreForma (Preservation Formats Project)] - Ashley Blewer
# [http://www.slideshare.net/WGBH_Archives/pbcore-rdf-ontology-hackathon-code4lib-2015 PBEBUCore] - Casey E. Davis
# [https://gist.github.com/hectorcorrea/c49dc287581d2856a12e RDF for relational database developers] - Hector Correa
# [http://intro2libsys.info/code4lib-2015 Building a BIBFRAME catalog] - Jeremy Nelson
# [http://www.mukurtu.org Mukurtu CMS] - Alex Merrill
# Drupal, git, and sanity - Charlie M.
# How do we improve as developers? - Trey Terrell

==Thursday 9:30 AM to 10:15 AM ==

# [https://github.com/OpenGeoMetadata/metadatarepository OpenGeoMetadata] : Let's share our geo metadata
# IIIF Image Drupal module
# Clustering moving image works - Kelley McGrath
# Islandora Fedora 4 proof of concept - Danny Lamb
# Measure the future - Jason Griffey
# Low hanging fruit of accessibility - Kate Deibel
# Planning for the data schlep - Adam Constabaris
# Archiving the silenced - Natasha Nunn
# The Great Migration: Fedora 4 - Andrew Woods

[[Category:Code4Lib2015]]