headers
Ed Summers | 1 Sep 21:12
Picon
Favicon

Re: Mapping records to classification data (was: Re: [NGC4LIB] Swedish union catalogue available as Linked Data)

On Tue, Aug 26, 2008 at 6:52 AM, Oliver Flimm <flimm <at> ub.uni-koeln.de> wrote:
> another step in linking library records would be to supply a mapping
> between individual records and the corresponding subject or
> classification scheme, e.g. with ISBN or something like Bibkey
> (http://www.gbv.de/wikis/cls/Bibliographic_Hash_Key).

Yes, these are definitely interesting. At a meeting at Open Library
earlier this year I listened in on a conversation between some folks
including Karen Coyle and Rob Styles (Talis) about this subject. It
definitely seems like there are lots of ways of doing the matching
[1]. At the end of the day, after you've done the painful part of
figuring out the linkages, you need a way of expressing them. URLs for
the resources being described, linked together w/ owl:sameAs or what
have you seems like a good, explicit way to start. And there's a
growing community of people doing the same thing in other pockets of
the web. [2]

> One possible solution would be to implement corresponding WebServices
> that get a ISBN or Bibkey and then deliver the appropriate LCSH or any
> other kind of related meta data. In my opinion a much better solution
> would be to offer the mapping data as a feed of flat files like
> LibraryThing (http://www.librarything.com/feeds/), e.g.
>
> ...
> <mapping>
>  <isbn>123<isbn>
>  <lcsh>aaa</lcsh>
>  <lcsh>bbb</lcsh>
> </mapping>
> <mapping>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Oliver Flimm | 2 Sep 08:41
Picon
Favicon

Re: Mapping records to classification data (was: Re: [NGC4LIB] Swedish union catalogue available as Linked Data)

Hi,

On Tue, Aug 26, 2008 at 02:59:45PM +0200, Martin Malmsten wrote:
>> other kind of related meta data. In my opinion a much better solution
>> would be to offer the mapping data as a feed of flat files like
>> LibraryThing (http://www.librarything.com/feeds/), e.g.
>
> Well, yes. But everything is already there in Linked Data.

hmm, almost everything. Except getting all titles in your local
catalogue that correspond to a specific subject heading, when this
subject heading doesn't get catalogued. Its all about enrichment of
your local data with external metadata and thus in the end its all
about metadata sharing.

This - in my mind - essential part cannot be done with Linked Data -
you have to use external metadata and find a source that provides it
;-) 

I don't think that it's possible to implement an efficient service
that returns eg. all ISBN's for a given subject heading in LoC, so you
can filter your local titles by them. It can be done easiest by
providing the mapping I suggested, so you can download the flat file,
enrich you local data with the additional subject headings and *then*
use Linked Data.

Regards,

Oliver
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dinberg Donna | 2 Sep 13:10
Picon

LAC: A Core Partner of the Open Library Environment (OLE) Project

** This message has been cross-posted to several lists **

Library and Archives Canada: A Core Partner of the Open Library Environment (OLE) Project

Library and Archives Canada (LAC) is pleased to announce that it is participating in the Open Library
Environment (OLE) Project joining other core partners, with Duke University as the project lead. 

With funding from the Andrew W. Mellon Foundation, the OLE Project will develop a design document for a
next-generation open-source library automation system that fits modern expectations for library
workflows and is built on a modern service-oriented architecture. This library system will be able to
meet the changing and complex needs of modern libraries and library users.

The small group of core partners will be highly involved in all phases of the project, by participating in
all the activities, by engaging other members of the library community in planning activities and by
writing the final project design document. 

LAC’s contribution will be significant and inclusive, as our mandate is to facilitate in Canada
co-operation among the communities involved in the acquisition, preservation and diffusion of
knowledge. Furthermore, because LAC is a national archive as well as a national library, this will bring
an added perspective to the project, and will provide another opportunity to find innovative solutions
to how both library and archival collections are managed and made accessible.

Currently, Library and Archives Canada is engaged in a multi-year project to evergreen and modernize its
own legacy library systems and incorporate them with an OAIS-compliant infrastructure to ingest,
store, manage, preserve and make accessible digital holdings.  LAC is embracing service-oriented
architecture and Web 2.0 features as a fundamental basis for its target application architecture. 

“By reaching out to Canadian libraries and archives, LAC has the potential to contribute significantly
to both the planning and build phases of an Open Library Management System, and to bring an additional
expertise and insight to the project,” says Ian E. Wilson, Librarian and Archivist of Canada. “We are
(Continue reading)

Permalink | Reply | 0 comments |
headers
Emily Lynema | 2 Sep 20:10
Picon
Favicon

REMINDER: Code4Lib Journal call for proposals, December issue, due 9/12

Just a reminder...proposals for the December 2008 issue of the Code4Lib 
Journal are due September 12, one week from this Friday. A first full 
draft of the article itself will not be due until October 17, so you 
still have some time to work.

Consider yourself encouraged to submit a proposal!

-emily lynema
coordinating editor, issue 5

-------- Original Message --------
Subject: Code4Lib Journal call for proposals, December issue
Date: Mon, 18 Aug 2008 21:35:01 -0400
From: Emily Lynema <emily_lynema <at> ncsu.edu>
To: Code for Libraries <CODE4LIB <at> LISTSERV.ND.EDU>

Call for Submissions:

The Code4Lib Journal (C4LJ) exists to foster community and share
information among those interested in the intersection of libraries,
technology, and the future.

The Code4Lib Journal is now accepting proposals for publication in its
5th issue. Don't miss out on this opportunity to share your ideas and
experiences in an issue that marks the first full year of publication
for this new journal. To be included in the 5th issue, scheduled for
publication in December 2008, please submit articles, abstracts, or
proposals to c4lj-articles <at> googlegroups.com by Friday, September 12,
2008. When submitting, please include the title or subject of the
proposal in the subject line of the message.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ken Varnum | 3 Sep 22:11
Picon
Favicon

Job Opening: Federated Search Developer at University of Michigan Library

The University of Michigan¹s Library Web Systems department has received
funding for a one-year term position to build a new, improved, federated
search tool for the University Library.

Library Web Systems manages the U-M Library web site [
http://www.lib.umich.edu ], federated search [
http://searchtools.lib.umich.edu ], the library's social bookmarking tool [
http://www.lib.umich.edu/mtagger/ ], develops other innovative and
experimental tools through MLibrary Labs [ http://www.lib.umich.edu/labs ],
and is implementing Drupal as our content management system.

The Federated Search Developer will create new tools to better match
licensed databases with patron needs.  The new system will lead our users to
A) the right database [relevant to search query] at the B) right level
[appropriate to the academic level of the specific question] of
subject-specific resources and C) ask the database the right question [using
vocabulary appropriate to the search target]. The successful candidate will
demonstrate experience and expertise in working with systems and data
integration in library databases.  Applicants should show experience with
PHP, Perl, MySQL, XML, and data interchange processes and formats.

This is a one-year term, full-time (40-hour) position. The University offers
a comprehensive benefits package, including 24 vacation days a year, health
insurance, generous retirement contributions, and much more.  Salary is
dependent on education and previous relevant experience.

Required Qualifications

- BS (MS preferred) in computer science or equivalent experience.
- 3-5 years programming experience in a library environment.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Martin Malmsten | 4 Sep 09:37
Picon
Favicon

Re: Swedish union catalogue available as Linked Data

> 30 mins later I had a simplistic 42 line harvester [...]
That's great!

> My suggestion to Roy was to imagine a world where library data sets
> were linked together [...]
Well, as long as we keep putting more stuff up as Linked Data, I'm  
sure someone will write the "killer app".

> At any rate along the way I noticed a few 500s, which you might want
> to look into. I think they all stemmed from the same problem:
Ooops, unescaped quotes.

> Also, when you link to lcsh.info remember [...]
Ooops again, the #concept was added to the HTML-page, not the RDF.

> And finally when you are creating the links between your subject
> authority data and lcsh.info you may want to leverage the SKOS mapping
> properties [2] instead of using skos:related.
Right. I have talked to the experts and they have authorized me to use  
skos:exactMatch. From what I understand this is almost always correct.

/martin
Permalink | Reply | 1 comment |
headers
Karen Coyle | 4 Sep 19:49

Attempt to "explain" DCAM

I've had a lot of discussions with a lot of people about the Dublin Core 
Abstract Model. I've made a very limited attempt to give my own 
understanding of the DCAM (along with a rant about terminology):

http://kcoyle.blogspot.com/2008/09/semantic-dementia.html

I'd love to have a deep discussion about whether this model is useful 
for us or not, and if not, what it is we really need. Feel free to 
comment, here, there, or anywhere.

kc
--

-- 
-----------------------------------
Karen Coyle / Digital Library Consultant
kcoyle <at> kcoyle.net http://www.kcoyle.net
ph.: 510-540-7596   skype: kcoylenet
fx.: 510-848-3913
mo.: 510-435-8234
------------------------------------
Permalink | Reply | 0 comments |
headers
Ed Summers | 4 Sep 21:24
Picon
Favicon

Re: Swedish union catalogue available as Linked Data

On Thu, Sep 4, 2008 at 3:37 AM, Martin Malmsten <martin.malmsten <at> kb.se> wrote:
> Ooops again, the #concept was added to the HTML-page, not the RDF.

Well it's in the rdf too. But I imagine you were an early adopter who
pulled down the data soon after it went live? About a month after the
initial release of lcsh.info I changed up the identifiers to be hash
URIs, since it simplified the delivery application quite a bit. If you
are curious I switched from 303 URIs forwarding to Different Documents
[1] to a Hash URI pattern described in the 4th paragraph of 4.4 [2].

I don't think this change was profoundly important, but it'll
definitely be interesting to see how the evolution of URI namespaces
plays out in the linked-data world.

//Ed

[1] http://www.w3.org/TR/cooluris/#r303uri
[2] http://www.w3.org/TR/cooluris/#choosing
Permalink | Reply | 0 comments |
headers
Gueguen, Gretchen | 4 Sep 21:53
Favicon

Job Posting: Web Services Librarian, East Carolina University

Apologies for cross-postings...

J.Y. Joyner Library, Academic Library Services, East Carolina University seeks an enthusiastic,
energetic and flexible colleague to lead the development and management of the Library's web presence. 

Responsibilities: Reporting to the Assistant Director for User Services, the Web Services Librarian will:

* Provide vision and leadership in designing, developing and supporting the Library's virtual presence,
including an increasing number of web-based services
* Lead, supervise, and direct the Web Development Team
* Collaborate effectively with librarians and staff to design and offer innovative digital library
services to our community
* Coordinate the creation of web resources through effective interface design,  sound information
architecture, usability and accessibility assessment techniques, and implementation of best
practices and standards
* Investigate, incorporate and deploy innovative technologies in library services such as wikis,
podcasting, RSS feeds, social networking technologies and other Library 2.0 concepts

Required Qualifications

* ALA-accredited master's degree or international equivalent in library or information science
* Strong leadership skills and ability to lead a web development team
* Ability to provide leadership in designing, developing, and supporting the Library's virtual presence
through use of best practices, standards, and emerging technologies
* Understanding of user-centered design for the development of web technologies
* Ability to employ effective web interface design, create sound information architecture, and perform
usability and accessibility assessments

Preferred Qualifications
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jesse Ephraim | 6 Sep 21:48
Picon
Picon

Re: NGC4LIB Digest - 22 Aug 2008 to 23 Aug 2008 (#2008-39)

>ILSes are, in fact, quite complicated, since, not only do 

>they manage workflows, but have to deal with each 

>individual doing everything a little bit differently 

>(as Jonathan Rochkind says, "we're unique little snowflakes").

...

>However, if they were 'simple systems' like you claim, the OSS 

>alternatives would have far surpassed the competition years ago.

Complexity is a relative thing.  From a programmatic standpoint, ILSes
are not very complex - certainly nowhere near the level of most business
systems and games.  Some of them - Horizon, for example - would barely
pass muster as shareware, at least from a reliability and design
standpoint.  I helped build much, much more complex business and
entertainment applications during my decade as a professional
programmer.  

Even at that, there is a lot of unnecessary complexity in many ILSes,
often stemming from the use of archaic data handling methods and
proprietary, closed systems.  There are a lot of parts to ILSes, and it
would take a little time to build a complete system from scratch, but
they are ultimately just specialized forms of a certain type of common
business software.  Patrons are "customers," books and such are our
"products," and circulation is just a type of "order fulfillment."
Rules and exceptions that may apply to certain individuals, items,
(Continue reading)

Permalink | Reply | 3 comments |

Gmane