[CODE4LIB] mashcat

[Eric Lease Morgan]

The following Mashcat event seems more than apropos to our group:

  We are excited to announce that the second face-to-face Mashcat
  event in North America will be held on January 24th, 2017, in
  downtown Atlanta, Georgia, USA. We invite you to save the date.
  We will be sending out a call for session proposals and opening
  up registration in the late summer and early fall.

  Not sure what Mashcat is? “Mashcat” was originally an event in
  the UK in 2012 aimed at bringing together people working on the
  IT systems side of libraries with those working in cataloguing
  and metadata. Four years later, Mashcat is a loose group of
  metadata specialists, cataloguers, developers and anyone else
  with an interest in how metadata in and around libraries can be
  created, manipulated, used and re-used by computers and software.
  The aim is to work together and bridge the communications gap
  that has sometimes gotten in the way of building the best tools
  we possibly can to manage library data. Among our accomplishments
  in 2016 was holding the first North American face-to-face event
  in Boston in January and running webinars. If you’re unable to
  attend a face-to-face meeting, we will be holding at least one
  more webinar in 2016.

  http://bit.ly/29FuUuY

Actually, the mass-editing of cataloging (MARC) data is something that is 
particularly interesting to me these days. Hand-crafted metadata records are 
nice, but increasingly unscalable.

—
Eric Lease Morgan

[CODE4LIB] Save the date: Mashcat meeting in Atlanta, Georgia, 24 January 2017

[Emily Williams]

We are excited to announce that the second face-to-face Mashcat event in North 
America will be held on January 24th, 2017, in downtown Atlanta, Georgia, USA. 
We invite you to save the date.  We will be sending out a call for session 
proposals and opening up registration in the late summer and early fall.

Not sure what Mashcat is? "Mashcat" was originally an event in the UK in 2012 
aimed at bringing together people working on the IT systems side of libraries 
with those working in cataloguing and metadata. Four years later, Mashcat is a 
loose group of metadata specialists, cataloguers, developers and anyone else 
with an interest in how metadata in and around libraries can be created, 
manipulated, used and re-used by computers and software. The aim is to work 
together and bridge the communications gap that has sometimes gotten in the way 
of building the best tools we possibly can to manage library data. Among our 
accomplishments in 2016 was holding the first North American face-to-face event 
in Boston in January and running webinars.  If you're unable to attend a 
face-to-face meeting, we will be holding at least one more webinar in 2016.

To learn more about Mashcat, visit http://mashcat.info.

Thanks for considering, and we hope to see you in January.

[CODE4LIB] Register for Library Carpentry at the University of Toronto July 28-29 - code4lib Toronto

[Kim Pham]

Hi Everyone,

**Just a reminder to sign up for the Library Carpentry workshop, there are only 
5 spots left!**

**We are also looking for helper mentors. If you want volunteer during the 
workshop, please sign up here: 
https://docs.google.com/spreadsheets/d/1SBZjOBu6liHgmvkR6oziX66-2GE09qPrUUGv2rW-ayA/edit
 **

About the workshop:

Code4lib Toronto is offering a 2-day introductory software workshop for 
information professionals (including librarians, archivists, museum curators, 
or information technicians) on July 28-29, 2016, at the University of Toronto 
Robarts Library (St. George campus). 

This 2-day workshop will cover a tools and skills that will help participants 
learn how to refine and clean up large volumes of data (OpenRefine); introduce 
automation and queries into workflows through programming (Regular Expressions, 
XQuery / XML); integrate software (APIs with Python); and perform web scraping 
with Scrapy (Python). 

While you do not need to have any previous knowledge of the tools presented at 
the workshop, we recommend that attendees have some exposure / familiarity with 
the following concepts: programming logic, boolean expressions, XML.

Lunch and snacks during the breaks will be provided.

For more information about the workshop and registration, please visit our 
website:
https://code4libtoronto.github.io/2016-07-28-librarycarpentry/

For more information about code4lib Toronto, visit:
http://www.meetup.com/code4libtoronto/

Thanks,

Kim


Kim Pham
Digital Scholarship Unit, Digital Projects & Technologies Librarian | Liaison 
Librarian,
Department Physical & Environmental Sciences (Physics)

UNIVERSITY OF TORONTO SCARBOROUGH
AC 270 | 1265 Military Trail, Toronto, Ontario, M1C 1A4
416-287-7491
https://utsc.library.utoronto.ca/

Re: [CODE4LIB] date fields

[Jonathan Rochkind]

> but since there is really no standard field for such a value, anything I
choose is all but arbitrary. I’ll use some 9xx field, just to make things
easy. I can always (and easily) change it later.

More like there are SEVERAL standard fields for such a value.

You can certainly put it in one of the existing standard fields, you just
have to actually follow the (often byzantine legacy) rules for such entry.
For instance, the date you want may very well already be in the fixed field
008, and you could certainly add it if it weren't. But the rules and
practices for 008 are confusing -- in part, because the actual real world
universe of "what is the date of this thing" is itself complex in the real
world of actually cataloged things, including serials and series,
manuscripts, reprints and fascimiles, old things where we aren't sure of
the exact dates, etc.  And in part just because the MARC standard is kind
of old and creaky, especially with regard to fixed fields like 008 being
designed to cram maximum amount of information in minimum bytes, beyond any
reasonable economy actually needed today.

I just learned about the 264 from Karen Miller's post (thanks Karen), I
dunno about that one, but it looks like it might be applicable too.

Standards, why have just one when you can have a dozen?

On Tue, Jul 12, 2016 at 10:12 AM, Eric Lease Morgan  wrote:

> On Jul 11, 2016, at 4:32 PM, Kyle Banerjee 
> wrote:
>
> >>
> https://github.com/traject/traject/blob/e98fe35f504a2a519412cd28fdd97dc514b603c6/lib/traject/macros/marc21_semantics.rb#L299-L379
> >
> > Is the idea that this new field would be stored as MARC in the system
> (the
> > ILS?).
> >
> > If so, the 9xx solution already suggested is probably the way to go if
> the
> > 008 route suggested earlier won't work for you. Otherwise, you run a risk
> > that some form of record maintenance will blow out all your changes.
> >
> > The actual use case you have in mind makes a big difference in what paths
> > make sense, so more detail might be helpful.
>
>
> Thank you, one & all, for the input & feedback. After thinking about it
> for a while, I believe I will save my normalized dates in a local (9xx)
> field of some sort.
>
> My use case? As a part of the "Catholic Portal", I aggregate many
> different types of metadata and essentially create a union catalog of rare
> and infrequently held materials of a Catholic nature. [1] In an effort to
> measure “rarity” I've counted and tabulated the frequency of a given title
> in WorldCat. I now want to measure the age of the materials in the
> collection. To do that I need to normalize dates and evaluate them. Ideally
> I would save the normalized dates back in MARC and give the MARC back to
> Portal members libraries, but since there is really no standard field for
> such a value, anything I choose is all but arbitrary. I’ll use some 9xx
> field, just to make things easy. I can always (and easily) change it later.
>
> [1] "Catholic Portal” - http://www.catholicresearch.net
>
> —
> Eric Lease Morgan
>

Re: [CODE4LIB] date fields

[Eric Lease Morgan]

On Jul 11, 2016, at 4:32 PM, Kyle Banerjee  wrote:

>> https://github.com/traject/traject/blob/e98fe35f504a2a519412cd28fdd97dc514b603c6/lib/traject/macros/marc21_semantics.rb#L299-L379
> 
> Is the idea that this new field would be stored as MARC in the system (the
> ILS?).
> 
> If so, the 9xx solution already suggested is probably the way to go if the
> 008 route suggested earlier won't work for you. Otherwise, you run a risk
> that some form of record maintenance will blow out all your changes.
> 
> The actual use case you have in mind makes a big difference in what paths
> make sense, so more detail might be helpful.


Thank you, one & all, for the input & feedback. After thinking about it for a 
while, I believe I will save my normalized dates in a local (9xx) field of some 
sort.

My use case? As a part of the "Catholic Portal", I aggregate many different 
types of metadata and essentially create a union catalog of rare and 
infrequently held materials of a Catholic nature. [1] In an effort to measure 
“rarity” I've counted and tabulated the frequency of a given title in WorldCat. 
I now want to measure the age of the materials in the collection. To do that I 
need to normalize dates and evaluate them. Ideally I would save the normalized 
dates back in MARC and give the MARC back to Portal members libraries, but 
since there is really no standard field for such a value, anything I choose is 
all but arbitrary. I’ll use some 9xx field, just to make things easy. I can 
always (and easily) change it later.

[1] "Catholic Portal” - http://www.catholicresearch.net

—
Eric Lease Morgan

Re: [CODE4LIB] date fields

[Karen Miller]

And don't forgot to check the MARC 264$c as well. That's the field that we use 
with RDA and you'll find it in newer records.

Karen

Karen D. Miller
Monographic Cataloger/Metadata Specialist
Northwestern University Libraries
Northwestern University
1970 Campus Drive
Evanston, IL 60208
www.library.northwestern.edu
k-mill...@northwestern.edu
874.467.3462


-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Trail, 
Nate
Sent: Monday, July 11, 2016 2:24 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] date fields

Don't forget that it might be duplicative of the 260 but the 008 has "machine 
readable" date info that may be less specific than the 260 but more uniformly 
entered (or that's the only place there is a date associated with 
publication/release).
Nate

==
Nate Trail
LS/ABA/NDMSO
Library of Congress
n...@loc.gov



-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Joy 
Nelson
Sent: Monday, July 11, 2016 3:19 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] date fields

Hi Eric-
Are you planning on storing the 'normalized' dates for ever in the MARC?
i.e. leave the c1900 in the 260$c and have 1900 in another place?

I think what you do depends on your ILS and tools.  My first reaction would be 
to stash the date in an unused subfield in the 260.  If your system allows you 
to add 'non standard' subfields, you could use 260$z to stash it.

But, then I start to think that might rankle some catalogers to have 'non 
standard' date data in the 260 (or 264).  I would probably then look at using 
one of the local use tags.  901-907, 910, or 945-949.  You could be the date in 
$a and even a brief description in a second subfield.
901$a1900$bnormalized date for project XYZ -initials/date

-Joy

On Mon, Jul 11, 2016 at 12:51 PM, Eric Lease Morgan  wrote:

> I’m looking for date fields.
>
> Or more specifically, I have been given a pile o’ MARC records, and I 
> will be extracting for analysis the values of dates from MARC 260$c.
> From the resulting set of values — which will include all sorts of 
> string values ([1900], c1900, 190?, 19—, 1900, etc.) — I plan to 
> normalize things to integers like 1900. I then want to save/store 
> these normalized values back to my local set of MARC records. I will 
> then re-read the data to create things like timelines, to answer 
> questions like “How old is old?”, or to “simply” look for trends in the data.
>
> What field would y’all suggest I use to store my normalized date content?
>
> —
> Eric Morgan
>



--
Joy Nelson
Director of Migrations

ByWater Solutions 
 Support and Consulting for Open Source Software
Office: Fort Worth, TX
Phone/Fax (888)900-8944
What is Koha? 

[CODE4LIB] Job: Digital Repository Coordinator at University of the Pacific

[jobs]

Digital Repository Coordinator
University of the Pacific
Stockton

The Digital Repository Coordinator oversees the growth and management of
Scholarly Commons, a University of the Pacific digital repository based in
University Libraries, including development and oversight of workflows.
Curated repository content includes scholarly and creative works,
publications, presentations, and reports contributed by faculty, students,
staff, and administrative units. In addition, a University Libraries
publishing program utilizes the repository platform to publish journals,
conference proceedings, monographs, open educational resources, and other
curated content. The position also interprets, creates, and implements
copyright law compliance protocols. The Digital Repository Coordinator reports
to the Information & Educational Technology Services Director in the Stockton
Campus Library.

  
Essential Functions

1. Designs and oversees strategic and operational plans for the University
Libraries digital repository.

2. Formulates, documents, and implements workflows and creates, interprets,
and assesses quality control policies and procedures for the digital
repository.

3. Develops and oversees a publishing program for e-journals, conference
proceedings, electronic books, open educational resources, and other digital
content created by the University of the Pacific community.

4. Develops and implements complex copyright clearance and permissions
checking workflows on publications created by faculty, students, and staff or
affiliates of University of the Pacific, including distribution rights held by
authors, editors, and publishers.

5. Promotes the digital repository to the University community through
presentations, social media, annual reports, and other outreach and
educational strategies (such as status reports, content solicitations, and
usage reports) to increases visibility and impact of university research and
scholarship.

6. Facilitates interoperability with other systems, working collaboratively
with library faculty and staff, faculty and staff from other university
departments and offices, and external service providers.

7. Provides training and education to university faculty, students, and staff
in using digital repository software, open access, and scholarly
communications issues.

8. Serves as the primary point of contact with the repository software
provider to customize and configure repository and troubleshoot technical
issues.

9. Creates policies and designs controls for metadata describing curated
content in the digital repository, and (as needed) uploads new content to the
digital repository.

10. Provides readership reports to support evaluation, promotion and tenure,
external reviews, and accreditation.

11. Provides information and assistance to repository contributors and users

  
Minimum Qualifications

Education/Work Experience/Certifications:

Graduate degree in library science, information science, or other related
field

Two years of relevant professional experience in library, museum, archives, or
other cultural organization

  
Skills/Knowledge and Expertise:

  * Strong knowledge of public access requirements from granting agencies, 
United States and international copyright law, and copyright policies of 
academic publishers.
  * Independent ability to interpret copyright law and publishers' policies to 
determine whether previously published materials may be added to the repository.
  * Strong skills to develop necessary institutional policies, guidelines, and 
procedures in compliance with federal, state, and local copyright law.
  * Strong communication, marketing, public speaking, project management, and 
time management capabilities.
  * Understanding of faculty research interests and outcomes, including 
disciplinary differences.
  * Familiarity with digital media trends and initiatives relevant in an 
academic environment.
  * Demonstrated ability to develop and foster effective working relationships 
within a diverse and fast-paced academic environment.
  * Conversant with new trends, tools, and opportunities (including grant 
funding) impacting repository management and scholarly communication issues.
  * Familiarity with standards and best practices to promote the discovery of 
open online resources, including metadata standards and website usability.
  
Preferred Qualifications

  * Education/Work Experience/Certifications:
  * MLS or MLIS from an ALA accredited program
  
Skills/Knowledge and Expertise:

  * Positive attitude, proven ability to work successfully with diverse 
populations and demonstrated commitment to promote and enhance diversity and 
inclusion
  * Previous experience creating policies and procedures for digital content 
with copyright protected and Creative Commons author rights.
  * Proven success utilizing repository software to showcase scholarship 
comprising different formats, using BePress Digital Commons and Selected Works 
software.
  * 

[CODE4LIB] Job: Digital Technologies Librarian at Tulane University

[jobs]

Digital Technologies Librarian
Tulane University
New Orleans

The Digital Technology Librarian will combine a strong service orientation
with application development to ensure that HTML maintains and builds upon the
high level of services for which it is renowned.

  
Posting Summary

The Digital Technologies Librarian takes an innovative, service-centric
approach to the oversight of several key information management and discovery
systems (including Tulane's implementations of Primo, Islandora, and
ArchivesSpace). S/he will be responsible for ensuring the optimal performance
of these systems, which will include: enabling data integration across
distributed and heterogeneous local and external data sources; providing
statistical, usage, and collection reports in support of decision making for
library collections and services; and promptly reporting issues/problems to
vendor(s) with follow-through until resolution. Additionally, the Digital
Technologies Librarian has secondary (back-up) responsibility for the
integrated library system (currently Voyager), link resolver (currently SFX),
proxy authentication, and interlibrary loan (ILLiad) systems. As a technology
liaison to library departments, s/he participates in formal task groups and
committees, both standing and ad-hoc, to analyze and improve systems and
services. S/he may assist with deploying hardware and software, including
ordering, troubleshooting, inventory, and licensing management. S/he will have
programming skills consummate with the Library's digital technology goals and
ambitions and will serve as part of a technology team that includes web
development, digital collections, and digital publishing initiatives.

  


Requirements

  
REQUIRED KNOWLEDGE, SKILLS, ABILITIES/COMPETENCIES TYPICALLY NEEDED TO PERFORM
THIS JOB SUCCESSFULLY:

• Experience managing integrated library systems and resource discovery tools,
link resolvers, and proxy authentication systems

• Experience managing Windows and Unix based servers

• Demonstrated ability to work with database management systems and scripts
(e.g., MS SQL, MySQL, Oracle, or MS Access) and writing queries in SQL

• Programming in XSLT, PHP, Ruby, or Python

• Experience with Web standards and scripting using HTML, XML, CSS, JavaScript
or JQuery

• Demonstrated analytical, technical, and troubleshooting skills for complex
applications

• Significant experience in project management

• Strong service orientation

• Proficiency in written and interpersonal communication

• Ability to succeed both independently and in a collaborative team
environment

• Ability to function fully and competently at technology competency Levels I,
II and III outlined in HTML Core Technology Competencies for Employees. (See h
ttp://library.tulane.edu/sites/library.tulane.edu/files/documents/core_technol
ogy_competencies.pdf)

  
PREFERRED QUALIFICATIONS:

• Familiarity with bibliographic record structure and classification systems

• Proficiency with standard computer hardware and desktop applications,
including deployment

• Experience with Primo, Voyager, Islandora, ArchivesSpace and ILLiad

• Experience integrating a wide variety of third-party applications into
library information systems.

• Knowledge of authentication using LDAP and Shibboleth.



Brought to you by code4lib jobs: http://jobs.code4lib.org/job/26625/
To post a new job please visit http://jobs.code4lib.org/

[CODE4LIB] Job: Film Archivist at Lucasfilm

[jobs]

Film Archivist
Lucasfilm
San Francisco

The Film Archivist works in collaboration with and under the direction of the
Lead Film Archivist to execute the receiving, cataloging, preserving,
curating, and storing of Lucasfilm media, including film, audio, video,
digital, and paperwork. Additionally, the Film Archivist facilitates research
of material and intra-company loans for Lucasfilm and Disney employees.

  * Heavy cataloguing of media including film, audio, video, digital and 
paperwork using Filemaker Pro and/or similar databases
  * Shelve and organize media for greatest accessibility and security
  * Research and fulfill requests originating from Lucasfilm and Disney 
employees. Loan, track and ensure return of materials to Lucasfilm and Disney 
employees, in accordance with Lucasfilm / Disney security and anti-piracy 
protocol
  * Loan, track, and ensure return of materials to Lucasfilm and Disney 
employees
  * Physically assist in reorganizing the film collection, including moving, 
labeling, reboxing, and shelving elements
  * Provide ongoing support to the daily operations of the Film Archive.
  * Provide stewardship of Lucasfilm's priceless legacy of assets utilizing 
preservation and storage best practices
Requirements Education / Experience:

  * Masters degree in a related field OR 2-3 years experience working in an 
archive
Required Skills / Competencies:

  * Ability to thrive in remote team environment, and excels at collaborating 
with internal and external stakeholders to gain insight into the larger 
organizational goals and strategies
  * Proficiency with Filemaker Pro and MS Excel
  * Demonstrates ability to properly manage time
  * Excellent at working independently on tasks requiring strict 
attention-to-detail and a high degree of accuracy and sensitivity to 
confidentiality
  * Ability to provide own transportation to and from work.
  * Excellent written and verbal communication skills
  * Strong organizational and multi-tasking skills in administrative environment
Desired Skills:

  * Previous film handling experience
  * Familiarity with Lucasfilm Ltd. productions strongly preferred
  * Previous rare printed material & paper handling experience
  * Experience with museum or archive databases other than FileMaker Pro



Brought to you by code4lib jobs: http://jobs.code4lib.org/job/26651/
To post a new job please visit http://jobs.code4lib.org/