Library Science 101 [infographic]

So you want to be a librarian?

Social Media Tips for Libraries (& others!)

Social media tips for libraries - great stuff here

Social media for librarians in the public sector - Health Sciences Library Groups Conference 2013 from Krishna De

IBM 3D prints world's smallest magazine [video]

I guess they are just trying to show what it could do… 

IBM 3D Prints World's Smallest Magazine Cover http://mashable.com/2014/04/25/ibm-world-smallest-magazine-cover/#:eyJzIjoidCIsImkiOiJfZTk1bGFmM3IzNHNlMG9iOXlseTFodF8ifQ

Interacting with dynamic shape display [video]

This is so cool - almost mind boggling where we are getting with technology.


inFORM - Interacting With a Dynamic Shape Display from Tangible Media Group on Vimeo.

Making it happen - linkeddata, bigdata, opendata and the semantic web

So, a question was asked in one of my linkeddata discussion groups. How does linkeddata, bigdata, opendata and the semantic web fit together?

My answer:
The Semantic web is the interface to make sense of all of the data (bigdata) which has to be accessible (open data); linkeddata is the mechanism making the data connections which are interpreted by the semantic web.

A very simplified view, for sure but I think it sums it up in a sentence.  

OpenLibrary - what it is (besides trending on reddit)

In addition to being a digital library, it is a linked data experiment with strong accessibility support. It is often cited as an example of linking bib data.






It was created by Aaron Swartz (yes, the Aaron Swartz) and is now a project of the Internet Archive (woot! love the IA).

https://openlibrary.org/

Linked data info:
http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Open_Library_Data

Watch it blow up reddit:
http://www.reddit.com/domain/openlibrary.org/

Linkeddata and libraries survey

For those doing linkeddata work in libraries:
http://bibliothek.univie.ac.at/limesurvey/

Opensource repository comparisom from Unesco - Dspace, Fedora, Islandora (Drupal + Fedora)

No Omeka, but a good overall comparison of opensource repository software:

More here
http://www.unesco.org/new/fileadmin/MULTIMEDIA/HQ/CI/CI/pdf/news/institutional_repository_software.pdf

3D technology - the next industrial revolution

As schools across the country are beginning to prepare children for what some have called "the next industrial revolution" by assimilating 3D printing technology into their curriculum, toy manufacturing giant Hasbro is planning to incorporate the technology into kids' playtime. More here and here



References:
http://www.3dprinterworld.com/article/3d-systems-hasbro-team-bring-3d-printing-playtime
http://www.theguardian.com/technology/2014/feb/17/hasbro-3d-printing-children-kids

the future of libraries - community spaces for the community

Librarians are "part wizard, part genius, part explorer. The work they do everyday changes people's lives." YES. I do think she gets to the heart of the transition for libraries and this article speaks to that issue http://narrative.ly/long-live-the-book/what-is-a-library/ So what is the treehouse for academia? Building a space for learning and knowledge, creation and collaboration; however, we can't forget that libraries are archives of culture as well.

Thoughts on CATALOGING, RDA, and metadata in netflix

 I have so many thoughts on this nexflix article but they can all be summed as humans and machines working together to organize, describe and provide relevance (the best of both worlds!) : semantic cataloging. Of course, libraries have been organizing, categorizing, and describing materials from the beginning, but RDA is a big step forward. With the end of print card catalogs and record limits (for the most part), the amount of data within a library catalog record can be much more expansive. Other library databases like repositories and digital libraries, generally have not faced record limits nor have they been tied to MARC (which has its own pros/cons). Of course, quantity doesn't always equal quality, either, but under RDA, we can provide as much description as we would like.

Another aspect of RDA is breaking up more data into smaller bits. Information that might have only appeared in a free text note field or was omitted from a library catalog record, may now be included in -- in some cases, as part of a controlled vocabulary, such as relator codes. These CODES provide information about the relationship of a particular person to a variety of things and can be used to build different kinds of linking, relevance, and all sorts of things! Libraries could create mechanisms so that users and others can more easily use the data to dynamically build lists or collections that are relevant to them (there's the semantic aspect!)  Of course, in order to use the data to make new things, it has to be open. 

Netflix has had a similar evolution in metadata. Thinking to what our nexgen library catalog systems could be like, let's look at what Netflix has done (and what a few folks have done with their data, which could only happen with at least, some of the data being open). 

Tagging/Data
It starts with people creating data and machine data collection:

"They [workers] capture dozens of different movie attributes. They even rate the moral status of characters. When these tags are combined with millions of users viewing habits, they become Netflix's competitive advantage. "


Much like traditional cataloging work, tagging is only as good as the tagger. The advantage that libraries have had is that the staff who do this sort of work (cataloging) most likely have some sort of training or relevant education.

In most popular social media (facebook, twitter, etc.) and image gallery sites (flickr, youtube, etc.) sub-tags if any, are limited: geographic (GIS , frequently from phone or camera gps coordinates in the exif metadata), subjects (topics as input by the uploader or tagger), names (user who uploaded or who tags other users in item), dates (item uploaded), access (public/private/select user group), system file information (file format, name, etc.)  and rights (copyright, permissions, etc.) are among the most common. For some image sites, exif data will automatically be loaded in, most frequently date, type of camera, file information and general image specs (size, resolution, etc.) ; other information such as rights (copyright)  is less likely to be picked up.  Facebook's support of metadata is marginal* (EXIF metadata is stripped out) and while Flickr does support the most metadata for images*, it relies primarily on the user to fill out the forms correctly to describe and assign the metadata. (See photometadata.org for more information about EXIF and social media).

In terms of search, crowdsourced metadata can be a challenge. It is only as good (and complete!) as the user who creates it. If you have ever searched for hashtags in twitter, or tags in Flickr, you will see they are used every way imaginable. Hashtags are used as a statement #fail #thisisstupid #greatread,  duplicated #ala (multiple things with the same keyword),  or misspelled #teh (the), with little in the way of quality control placed on them.

Structure
However, there is some structure in place, which facilitates searching by hashtag/tag vs. date.

While libraries have had better systems in that the metadata was created by experts and experienced staff, much of the data in a traditional MARC record is unstructured. Funny, no? We think of MARC as being so structured and while it is in terms of field order and use and the fixed field (character placement is essential there), it is not so structured within some fields, like the 5XX fields or even within the 245 (title/statement of responsibility) field. As long as the indicators are correct and the subfields are input correctly, the content within that field is really a type of free text. albeit with some rules for inputting. For example, while the 245 was and remains under RDA as a transcription field (key it as you see it), there are still "shortcuts" (i.e., ways to minimize data recorded) under RDA (See: a nice overview of changes between AAC2 and RDA). So, while it's transcription, it's not exactly ALWAYS word for word (albeit more so with RDA).

The third major component is that the data is open, or at least partially open.With siloed data, this experiment would have not been possible. Having siloed data decreases its ability to be used by others, as well.



So, how was Netflix able to make this successful from a metadata standpoint?

• a defined (controlled) vocabulary (subject headings, authorities): " The same adjectives appeared over and over. Countries of origin also showed up, as did a larger-than-expected number of noun descriptions like Westerns and Slasher..."  

• a structure (for catalogers, a similarity to how subject headings are formatted in a traditional library catalog), in netflix:  

• Region, Awards named first (at least for Oscars)
• Adjectives (Keywords, subject headings)
• Dates and places named last (akin to a geographic subdivision)

"If a movie was both romantic and Oscar-winning, Oscar-winning always went to the left: Oscar-winning Romantic Dramas. Time periods always went at the end of the genre: Oscar-winning Romantic Dramas from the 1950s....
In fact, there was a hierarchy for each category of descriptor. Generally speaking, a genre would be formed out of a subset of these components:

Region + Adjectives + Noun Genre + Based On... + Set In... + From the... + About... + For Age X to Y"

 Akin to traditional subject headings:
6510 Sardinia (Italy) $v maps $v Early works to 1800  
650 0  $a Beach erosion $z Florida $z Pensacola Beach $x History $y 20th century $v Bibliography.

•  data bits that can be repackaged: "little "packets of energy" that compose each movie.... "microtag."" (the smaller the data bits, the more they can be repackaged in different ways) 

 "Netflix's engineers took the microtags and created a syntax for the genres..... "


Thinking back to nexgen systems: RDA is providing a fairly good foundation to go beyond the traditional catalog. When done right (more vs. less, quality AND quantity), cataloging will net structured data bits that can be repackaged and relationship information that can build provide links between previously unrelated items (at least within the catalog); provided the data is open to be used and mechanisms are built so that users can create their own catalog experience. In that world, cataloging truly becomes semantic.
 


References:
Open Bibliographic Data, http://opendefinition.org/bibliographic/
Photometadata.org photometadata.org
AACR2 compared to RDA, field by field: http://www.rda-jsc.org/docs/5sec7rev.pdf  
How netflix reverse engineered hollywood: http://www.theatlantic.com/technology/archive/2014/01/how-netflix-reverse-engineered-hollywood/282679/
 

*Disclaimer: I have no idea what the backend systems of sites do with metadata; my thoughts are based upon the user experience. 

Flying a drone - of sorts- through the NYPL

What a cool project
. Yay Gopro!
http://www.theatlanticcities.com/neighborhoods/2013/11/amazing-drones-eye-view-new-york-public-library/7487/

GLAMLOD: Linked data, semantic web group meetup

Some of you may remember this group was formed last year after GLA. Please excuse crossposting: Interested in linked data? Interested in the semantic web? Not even sure what the heck that is or how it applies to libraries, archives, or museums? GLAMLOD: Georgia Libraries, Archives & Museums Linked Open Data (http://www.facebook.com/glamlod/) is hosting a meetup in atlanta in November. Please join our discussion group at google groups or like us on facebook for news and updates. If you're interested in the meetup, please contact a member of the group. Feel free to share this with colleagues who might be interested. Here is the proposed plan. What: This is a GLAMLOD meet-up with presentations and information sharing on tools, training, demos, potential uses, or emerging practices regarding linked data. When: (TBD) Sometime the week of November 11th 2013. 6:30pm - 9:00pm Where: Atlanta GA (Manuel's Tavern) Who: GLAMLOD members and guests How: In person (and we can explore using Skype for remote attendance) Please contact Laura Akerman (liblna@emory.edu), Robin Fay (georgiawebgurl@gmail.com ), or Doug Goans (doug.goans@library.gatech.edu): * If you are interested in attending and especially if you would like to attend virtually. * If you would like to give short presentations or information sharing about linked data. (We are looking for 2-minute lightning talks to about 15 minutes max for each presentation.) * If you have other suggestions for programming.

Linked data presentations

Reading list: linked data & ex-libris

1. Linked data and Ex Libris products – introduction - Lukas Koster, University of Amsterdam, Netherlands
2. Publishing Aleph data as linked open data - Silke Schomburg, HBZ, Germany
3. Linked open dedup vectors – An experiment with RDFa in Primo - Corey Harper, New York University, USA
4. Exploiting DBPedia for use in Primo - Ulrike Krabo, OBVSG, Austria
5. Linking library and theatre data - Lukas Koster,University of Amsterdam, Netherlands
6. Linked data and Ex Libris products – summary - Lukas Koster, University of Amsterdam, Netherlands
7. Ex Libris – linked data outlook - Axel Kaschte, Ex Libris

RDA/FRBR reading list

Lots of RDA/FRB in this list:

• Karen Coyle: Understanding the Semantic Web: Bibliographic Data and Metadata, Chapters 1 and 2 http://alatechsource.metapress.com/content/g212v1783607/?p=b4700bc9fec34b12a3f42a94a9fd9d4f&pi=0
• Diane Hillmann, Karen Coyle, Jon Phipps and Gordon Dunsire: RDA Vocabularies: Process, Outcome, Use http://dlib.org/dlib/january10/hillmann/01hillmann.html
•  Barbara Tillett: What RDA Is and Isn't http://www.loc.gov/bibliographic-future/rda/trainthetrainer.html
• RDA Prospectus: http://www.rda-jsc.org/rdaprospectus.html
• (Presentation with Slides and Notes) Tom Delsey: Moving Cataloguing into the 21st Century. http://tsig.wikispaces.com/Pre-conference+2010 
• RDA Scope and Structure http://www.rda-jsc.org/docs/5rda-scoperev4.pdf

Mendeley news - Acquired by Elsevier, Open Data & more

Mendeley has been acquired by elsevier & other tidbits via the Mendeley May Librarian Newsletter (the talk about Mendeley is very interesting):

--------------------
This month we're giving a look inside our relationship with open data, looking for your feedback on a new user resource, and inviting you to participate in upcoming programs.

1. Mendeley Vision
2. What do you think: New User Guide
3. Upcoming Mendeley Open Day
4. Supporting Researchers: It's what we do
http://us5.campaign-archive1.com/?u=5560fe5e9f52735e40444340c&id=00de5749db&e=59dee60172

LInked data, big data presentations archives

OCLC/Lyrasis discussion/presentation that Peter Murray and I facilitated:

Shared Data:

    

Shared Data & Big Data for Libraries from robin fay

Archive: http://tinyurl.com/d89qzmf

Linked Data:

Linked data for Libraries from robin f

Archive:      http://tinyurl.com/cob9uur

Global Change Queue (Batch edit) @ELUNA 2103 notes

Global Data Change Queue Notes

(Compiled by Robin Fay @georgiawebgurl ; http://www.contentdivergent.blogspot.com)

http://works.bepress.com/julene/ (many batch edit presentations)

Eluna presentation: http://works.bepress.com/julene/5/

What can GDC do?

• Can edit marc tags, fields
• can delete, edit, add
• can set preferences
• can limit by user names including create rules but not implement - so some one person could create rules but someone else has authority to run; can define by user role what can be edited (R note could be useful for a review/test  process)

Examples:

• all records must have ____ (specific criteria; R note in the case of POs 910 = PA + lacking 245 indicators )
• like a global find and replace (R note: YES! yes! So, could fix typos in 5xx fields! or invalid MARC tagging in PO ; looks useful)

How to do it:

• create record set (R note: we could use old provisional records with incorrect marc indicators as a test)
• RULE: create a rule use if/then statements
• further define rules through sets  - (R note: daisy chain together) to edit multiple fields - one rule for each field but then change them
• Preview /Review before change
• Will highlight changes
• Jump through set of records (e.g., 10 records at a time - your choice)
• If you find something that doesn't belong, you can remove it manually during preview
• If rule doesn't work, you will get a notice
• Update or review changes before you actually run

Run job or schedule

More powerful/easier to use than marcedit

More examples - updated authorized headings (RDA)

fixed fields

add OCLC #s

cleanup recon

add/remove standard notes

changed locations - pick and scan for item tho (of course you have to have the barcode.... but you don't have to have piece - R note) doesn't interfere with cataloging work - because whoever has record open has it (“locked” sort of) ; can schedule

Cataloging: Cuttering resources

I put this together for someone else and thought I would share it with you too! ________________________________________
cutter tables at
http://www.itsmarc.com/crs/mergedProjects/cutter/cutter/basic_table_cutter.htm

and the cataloging calculator is a pretty nifty tool:
http://calculate.alptown.com/

This is a good overall resource:
http://www.itsmarc.com/crs/mergedProjects/cutter/cutter/contents.htm

One of the main things to be aware of in cuttering, is the local shelflist. ;-)

As for creating call numbers, for us that would be LC classification, so there is the subject analysis part to get the class and then the cutter. LCSH can be browsed via this list
http://www.biblio.tu-bs.de/db/lcsh/index.htm
I'm not sure how detailed it is, but it seems like a good overall tool.

Survey on Research practices of historians

Ithaka S+R’s Research Support Services for Scholars program has released the report of their NEH-funded study, Supporting the Changing Research Practices of Historians(http://www.sr.ithaka.org/news/understanding-historians-today-%E2%80%94-new-ithaka-sr-report). Here’s a brief description of the project from the report’s Executive Summary:

In 2011-2012, Ithaka S+R examined the changing research methods and practices of academic historians in the United States, with the objective of identifying services to better support them. Based on interviews with dozens of historians, librarians, archivists, and other support services providers, this project has found that the underlying research methods of many historians remain fairly recognizable even with the introduction of new tools and technologies, but the day to day research practices of all historians have changed fundamentally. Ithaka S+R researchers identified numerous opportunities for improved support and training, which are presented as recommendations to information services organizations including libraries and archives, history departments, scholarly societies, and funding agencies.