Re: [CODE4LIB] A metadata tool that scales

2008-10-10 Thread Susan Teague Rector
Have you all looked at enterprise metadata repository tools? Oracle and 
SAS have nice tools that could be extended to meet some of the 
requirements listed below.


Thanks,
Susan

--
Susan Teague Rector
Web Applications Manager
Library Information Systems, VCU Libraries
804.827.3554 | [EMAIL PROTECTED]



Will Sexton wrote:

In January of 2007 I sent a post to the Web4lib list titled Metadata
tools that scale.  At Duke we were seeking opinions about a software
platform to capture metadata for digital collections and finding
databases.  The responses to that inquiry suggested that what we were
seeking didn't exist.

About a year ago, an OCLC report on a survey of 18 member institutions,
RLG Programs Descriptive Metadata Practices Survey Results, supported
that basic conclusion.  When asked about the tools that they used to
create, edit and store metadata descrptions of digital and physical
resources, a sizable majority responded customized or homegrown tool.

Since my initial inquiry, we launched a new installation of our digital
collections at http://library.duke.edu/digitalcollections/.  Yet we still
lack a full-featured software platform for capturing descriptive metadata.

We did our own informal survey of peer institutions building digital
collections, which further reinforced that familiar conclusion -- there
are lots of Excel spreadsheets, Access and FileMaker databases, etc., out
there, but no available enterprise-level solution (and we're still happy
to be wrong on this point).

We also articulated a detailed series of specifications for a metadata
tool.  The library has committed to hiring two programmers each to a
two-year appointment for producing a tool that meets these specs.  I just
posted on this list the job description, for which there are two openings.

I have a longer version of this post on our digital collections blog
(http://library.duke.edu/blogs/digital-collections/2008/10/10/a-metadata-tool-that-scales/),
listing our specifications in more detail.  But here are some of the
basics:

* Digitization:  integrates with, or provides a module for, management of
digitization workflow.

* Description:  supports a collections-based data model; flexible metadata
schema (for us, the Duke Core, derived from qualified Dublin Core);
authority lists; cardinality and required-field constraints; metametadata
(i.e., flagging, notations and status indicators for individual items);
access control; simple and intuitive use.

* Publication:  exports METS documents as well as other common formats
(CSV, etc.).

* Asset Management:  must be compatible with an asset management policy.

While the Duke specifications are particular to our internal needs, I
think we captured a lot of what makes the need for a full-featured
metadata tool felt around the field.  I have some ideas about how to go
about implementing this set of specifications, but thought I'd see if the
concept might spur discussion on CODE4LIB.  How would you approach this
project?  Any thoughts on architecture, platform, data models,
methodologies?

Will
--
Will Sexton
Metadata Analyst / Programmer
Duke University Libraries
  


[CODE4LIB] Position Announcement: Systems Programmer (Duke University)

2008-10-10 Thread Will Sexton
Systems Programmer - 2 Year Term Appointment

Reporting to the Metadata Systems Programmer, the systems programmer will
contribute to the development of a technical infrastructure based on open
source software to support metadata creation and management. S/He will
design and program the tool and integrate it with other modules in the
systems architecture.

Responsibilities
* Creates and implements emerging digital technologies in support digital
library initiatives including repository configuration, systems
administrative tools, metadata crosswalking, indexing/search engines.
* Designs and programs interface for metadata creation and management;
supports data interchange with databases; writes queries using available
scripting languages.
* Designs and programs interface for management of digitization workflow.
* Develops enhancements for current digital collections interface.
* Applies principles of usability, accessibility and assessment to develop
effective interfaces and navigation structures to meet user needs.
* Works collaboratively with a variety of individuals in the libraries
including archivists, librarians, metadata specialists, and other IT staff
to identify and understand digital collection workflows, source data
systems and mapping requirements.
* Creates documentation for all phases of the project.
* Other duties as assigned.

Qualifications
It is the expectation that all Duke University Libraries staff members
will demonstrate exceptional workplace behaviors in the execution of their
specific position responsibilities. These behaviors are customer focus,
collaboration, creative problem solving, continuous learning and a
commitment to diversity.

Education
Required: BA/BS or equivalent combination of relevant experience and
training.

Experience
Required: Two years of programming experience in Java, Python, XML, XSL
and/or SQL; excellent interpersonal, oral and written communication
skills; ability to work independently and as a member of a team; strong
organizational and project management skills; demonstrated commitment to
providing outstanding customer service.

Preferred: Prior experience working in an academic research library;
demonstrated proficiency with PHP, JavaScript, AJAX, Perl; knowledge of
information technology trends and their application to digital storage
formats and metadata standards; experience working with metadata standards
and protocols such as METS, MODS, PREMIS, TEI, EAD, or OAI-PMH; experience
in providing programming support in a digital library, digital publishing,
tools development, or digital humanities environment.

Working Conditions
* Must be able to work in an environment in which exposure to
materials containing dust and mold is possible
* Normal office environment

These statements are intended to describe the general nature and level of
work being performed by the employee in this position. They are not
intended to be construed as an exhaustive list of all responsibilities,
duties, and skills required of a person in this position.

Salary and Benefits
Salary dependent on qualifications and experience. Comprehensive benefits
package includes 15 days vacation, 13 holidays, 12 days sick leave;
health, dental, disability and life insurance and support for professional
development and training.

Environment
The Duke University Libraries are the shared center of the university's
intellectual life, connecting people and ideas. The William R. Perkins
Library, its branches (Lilly, Music, Biological and Environmental
Sciences, Marine Laboratory in Beaufort, and the Rare Book, Manuscript,
and Special Collections Library) and the separately administered libraries
serving the schools of Business, Divinity, Law, and Medicine, comprise one
of the nation's top ten private university library systems. Duke is a
member of the Triangle Research Libraries Network, which promotes
collaboration in the areas of collection development and management,
access services, information technology and human resources among the
libraries of Duke University, the University of North Carolina-Chapel
Hill, North Carolina Central University and North Carolina State
University.

Duke University and Durham are located in the Research Triangle, a region
that encompasses one of the nation's premier concentrations of academic,
corporate, and public research. The Triangle region is rated among the
most desirable areas in North America to live and work and has been
identified by Money magazine as one of the Best Places to Live in the
U.S.

Application
Send cover letter, detailed resume and the names, addresses (mailing and
e-mail), and telephone numbers of three references to: Teresa Tillman,
Library Human Resources, at [EMAIL PROTECTED]  Please include
PROGRAMMERS in the subject line.  Review of applications will begin in
mid-October and will continue until the position is filled.

An electronic resume should also be submitted at:
http://www.hr.duke.edu/jobs/main.html. Refer to 

[CODE4LIB] A metadata tool that scales

2008-10-10 Thread Will Sexton
In January of 2007 I sent a post to the Web4lib list titled Metadata
tools that scale.  At Duke we were seeking opinions about a software
platform to capture metadata for digital collections and finding
databases.  The responses to that inquiry suggested that what we were
seeking didn't exist.

About a year ago, an OCLC report on a survey of 18 member institutions,
RLG Programs Descriptive Metadata Practices Survey Results, supported
that basic conclusion.  When asked about the tools that they used to
create, edit and store metadata descrptions of digital and physical
resources, a sizable majority responded customized or homegrown tool.

Since my initial inquiry, we launched a new installation of our digital
collections at http://library.duke.edu/digitalcollections/.  Yet we still
lack a full-featured software platform for capturing descriptive metadata.

We did our own informal survey of peer institutions building digital
collections, which further reinforced that familiar conclusion -- there
are lots of Excel spreadsheets, Access and FileMaker databases, etc., out
there, but no available enterprise-level solution (and we're still happy
to be wrong on this point).

We also articulated a detailed series of specifications for a metadata
tool.  The library has committed to hiring two programmers each to a
two-year appointment for producing a tool that meets these specs.  I just
posted on this list the job description, for which there are two openings.

I have a longer version of this post on our digital collections blog
(http://library.duke.edu/blogs/digital-collections/2008/10/10/a-metadata-tool-that-scales/),
listing our specifications in more detail.  But here are some of the
basics:

* Digitization:  integrates with, or provides a module for, management of
digitization workflow.

* Description:  supports a collections-based data model; flexible metadata
schema (for us, the Duke Core, derived from qualified Dublin Core);
authority lists; cardinality and required-field constraints; metametadata
(i.e., flagging, notations and status indicators for individual items);
access control; simple and intuitive use.

* Publication:  exports METS documents as well as other common formats
(CSV, etc.).

* Asset Management:  must be compatible with an asset management policy.

While the Duke specifications are particular to our internal needs, I
think we captured a lot of what makes the need for a full-featured
metadata tool felt around the field.  I have some ideas about how to go
about implementing this set of specifications, but thought I'd see if the
concept might spur discussion on CODE4LIB.  How would you approach this
project?  Any thoughts on architecture, platform, data models,
methodologies?

Will
--
Will Sexton
Metadata Analyst / Programmer
Duke University Libraries


[CODE4LIB] FW: Logo vote

2008-10-10 Thread Roy Tennant
Thanks to Ross Singer, the second vote on the logo idea is now open, and
will be open until Tuesday evening, 10:45-ish EST (I didn't make this up).
The options are listed below, as well as on the voting form. You will need
to have an account on http://code4lib.org/ in order to vote, and you use the
same login and password. Please see:

http://dilettantes.code4lib.org/voting_booth/election/index/6

And vote early and often!
Roy

 -- Forwarded Message
 From: Roy Tennant [EMAIL PROTECTED]
 Date: Fri, 26 Sep 2008 10:53:07 -0700
 To: Code for Libraries CODE4LIB@LISTSERV.ND.EDU
 Subject: Logo vote

 The logo voting seems to have died down at 109 votes cast, and it breaks
 down like this (you can see these results at
 http://www.micropoll.com/akira/mpresult/479444-107406):

 No logo: 8%
 Do it ourselves: 8%
 Combo of professional designer and ourselves: 26%
 Don't care: 27%
 Professional designer: 31%

 Since there was no clear majority, I think we should have a run-off between
 the combo option and only a professional designer.

 But I think the options should be more clearly stated than they were before
 (sorry!):

 Combo Option:
 One person would receive all the designs from both internal designers and
 any professional designers willing to submit designs for free, and they are
 put up for a vote without anyone knowing who did which design.

 Professional Option 1:
 We accept Stephanie Brinley's kind offer, request a few different ideas,
 vote on those ideas to settle on one, and the final version is created from
 the winning idea.

 Professional Option 2:
 Hire a different professional designer (to be determined) from whom we
 solicit a few different ideas, vote on the ideas, and the final version is
 created from the winning idea.

 Yes, consensus is tedious. Competing ideas, objections, embellishments
 welcome. Otherwise, I'll set up another vote on the three options above and
 the one with the most votes takes it.
 Roy



 -- End of Forwarded Message





-- End of Forwarded Message


Re: [CODE4LIB] FW: Logo vote

2008-10-10 Thread Kevin S. Clarke
Hi Roy,

Did we lose the no logo option?  I know this is an opportunity for
refinement but the no logo and I don't care options in the last
poll, when put together, had a pretty big total.  Perhaps we drop the
I don't care which is nice for self expression, but doesn't really
tell us much in the way of what we should do and just have a no logo
option?

2c

Kevin



On Fri, Oct 10, 2008 at 10:17 AM, Roy Tennant [EMAIL PROTECTED] wrote:
 Thanks to Ross Singer, the second vote on the logo idea is now open, and
 will be open until Tuesday evening, 10:45-ish EST (I didn't make this up).
 The options are listed below, as well as on the voting form. You will need
 to have an account on http://code4lib.org/ in order to vote, and you use the
 same login and password. Please see:

 http://dilettantes.code4lib.org/voting_booth/election/index/6

 And vote early and often!
 Roy

 -- Forwarded Message
 From: Roy Tennant [EMAIL PROTECTED]
 Date: Fri, 26 Sep 2008 10:53:07 -0700
 To: Code for Libraries CODE4LIB@LISTSERV.ND.EDU
 Subject: Logo vote

 The logo voting seems to have died down at 109 votes cast, and it breaks
 down like this (you can see these results at
 http://www.micropoll.com/akira/mpresult/479444-107406):

 No logo: 8%
 Do it ourselves: 8%
 Combo of professional designer and ourselves: 26%
 Don't care: 27%
 Professional designer: 31%

 Since there was no clear majority, I think we should have a run-off between
 the combo option and only a professional designer.

 But I think the options should be more clearly stated than they were before
 (sorry!):

 Combo Option:
 One person would receive all the designs from both internal designers and
 any professional designers willing to submit designs for free, and they are
 put up for a vote without anyone knowing who did which design.

 Professional Option 1:
 We accept Stephanie Brinley's kind offer, request a few different ideas,
 vote on those ideas to settle on one, and the final version is created from
 the winning idea.

 Professional Option 2:
 Hire a different professional designer (to be determined) from whom we
 solicit a few different ideas, vote on the ideas, and the final version is
 created from the winning idea.

 Yes, consensus is tedious. Competing ideas, objections, embellishments
 welcome. Otherwise, I'll set up another vote on the three options above and
 the one with the most votes takes it.
 Roy



 -- End of Forwarded Message





 -- End of Forwarded Message




-- 
There are two kinds of people in the world: those who believe there
are two kinds of people and those who know better.


Re: [CODE4LIB] A metadata tool that scales

2008-10-10 Thread Shaun Ellis

Hi Will,
In Issue #1 of the Code4Lib Journal some of my colleagues here at 
Rutgers published an article on the open sourcing of our homegrown 
system, which may serve your purposes or at least serve as a starting 
point.  Anyway, here's the article:


http://journal.code4lib.org/articles/25

-Shaun Ellis

Will Sexton wrote:

In January of 2007 I sent a post to the Web4lib list titled Metadata
tools that scale.  At Duke we were seeking opinions about a software
platform to capture metadata for digital collections and finding
databases.  The responses to that inquiry suggested that what we were
seeking didn't exist.

About a year ago, an OCLC report on a survey of 18 member institutions,
RLG Programs Descriptive Metadata Practices Survey Results, supported
that basic conclusion.  When asked about the tools that they used to
create, edit and store metadata descrptions of digital and physical
resources, a sizable majority responded customized or homegrown tool.

Since my initial inquiry, we launched a new installation of our digital
collections at http://library.duke.edu/digitalcollections/.  Yet we still
lack a full-featured software platform for capturing descriptive metadata.

We did our own informal survey of peer institutions building digital
collections, which further reinforced that familiar conclusion -- there
are lots of Excel spreadsheets, Access and FileMaker databases, etc., out
there, but no available enterprise-level solution (and we're still happy
to be wrong on this point).

We also articulated a detailed series of specifications for a metadata
tool.  The library has committed to hiring two programmers each to a
two-year appointment for producing a tool that meets these specs.  I just
posted on this list the job description, for which there are two openings.

I have a longer version of this post on our digital collections blog
(http://library.duke.edu/blogs/digital-collections/2008/10/10/a-metadata-tool-that-scales/),
listing our specifications in more detail.  But here are some of the
basics:

* Digitization:  integrates with, or provides a module for, management of
digitization workflow.

* Description:  supports a collections-based data model; flexible metadata
schema (for us, the Duke Core, derived from qualified Dublin Core);
authority lists; cardinality and required-field constraints; metametadata
(i.e., flagging, notations and status indicators for individual items);
access control; simple and intuitive use.

* Publication:  exports METS documents as well as other common formats
(CSV, etc.).

* Asset Management:  must be compatible with an asset management policy.

While the Duke specifications are particular to our internal needs, I
think we captured a lot of what makes the need for a full-featured
metadata tool felt around the field.  I have some ideas about how to go
about implementing this set of specifications, but thought I'd see if the
concept might spur discussion on CODE4LIB.  How would you approach this
project?  Any thoughts on architecture, platform, data models,
methodologies?

Will
--
Will Sexton
Metadata Analyst / Programmer
Duke University Libraries

  



--
Shaun Ellis
Web Applications Programmer
Rutgers University Libraries
[EMAIL PROTECTED]
732/445-5896


[CODE4LIB] Vote for NE code4lib meetup location

2008-10-10 Thread Jay Luker
It's time to do a quick vote on where we'd like to hold our first New
England gathering. If you are interested in attending please cast your
ballot at http://dilettantes.code4lib.org/voting_booth/election/index/5.

We'll keep voting open for a few days (at least through Tuesday). You
can give from 0 to 3 points to each location, so more points to your
1st choice, less to your 2nd fave, etc. You can also go back and
change you votes any time. Use the same login as you would at the main
code4lib.org site. Yes, this means you have to be registered at
code4lib.org already. Hopefully you got all that straightened out when
you cast you ballot for the 2009 conference keynotes, right?

Thanks to Ross Singer and his supertastic Diebold-O-Tron for setting this up.

--jay


Re: [CODE4LIB] FW: Logo vote

2008-10-10 Thread Roy Tennant
Well, I don't really think don't care equates to no logo, since it is
more of an abstention than anything. And you won't find me trying to be
funny in a vote again. So considering there was only 8% saying no, and 65%
voting for some version of creating a logo, I felt like the question about
whether to do it or not had been settled. Therefore, I moved on to the
how. If there are widespread objections I will reconsider, but it seemed
to me that the basic question had been decided.
Roy


On 10/10/08 10/10/08 € 7:39 AM, Kevin S. Clarke [EMAIL PROTECTED]
wrote:

 Hi Roy,
 
 Did we lose the no logo option?  I know this is an opportunity for
 refinement but the no logo and I don't care options in the last
 poll, when put together, had a pretty big total.  Perhaps we drop the
 I don't care which is nice for self expression, but doesn't really
 tell us much in the way of what we should do and just have a no logo
 option?
 
 2c
 
 Kevin
 
 
 
 On Fri, Oct 10, 2008 at 10:17 AM, Roy Tennant [EMAIL PROTECTED] wrote:
 Thanks to Ross Singer, the second vote on the logo idea is now open, and
 will be open until Tuesday evening, 10:45-ish EST (I didn't make this up).
 The options are listed below, as well as on the voting form. You will need
 to have an account on http://code4lib.org/ in order to vote, and you use the
 same login and password. Please see:
 
 http://dilettantes.code4lib.org/voting_booth/election/index/6
 
 And vote early and often!
 Roy
 
 -- Forwarded Message
 From: Roy Tennant [EMAIL PROTECTED]
 Date: Fri, 26 Sep 2008 10:53:07 -0700
 To: Code for Libraries CODE4LIB@LISTSERV.ND.EDU
 Subject: Logo vote
 
 The logo voting seems to have died down at 109 votes cast, and it breaks
 down like this (you can see these results at
 http://www.micropoll.com/akira/mpresult/479444-107406):
 
 No logo: 8%
 Do it ourselves: 8%
 Combo of professional designer and ourselves: 26%
 Don't care: 27%
 Professional designer: 31%
 
 Since there was no clear majority, I think we should have a run-off between
 the combo option and only a professional designer.
 
 But I think the options should be more clearly stated than they were before
 (sorry!):
 
 Combo Option:
 One person would receive all the designs from both internal designers and
 any professional designers willing to submit designs for free, and they are
 put up for a vote without anyone knowing who did which design.
 
 Professional Option 1:
 We accept Stephanie Brinley's kind offer, request a few different ideas,
 vote on those ideas to settle on one, and the final version is created from
 the winning idea.
 
 Professional Option 2:
 Hire a different professional designer (to be determined) from whom we
 solicit a few different ideas, vote on the ideas, and the final version is
 created from the winning idea.
 
 Yes, consensus is tedious. Competing ideas, objections, embellishments
 welcome. Otherwise, I'll set up another vote on the three options above and
 the one with the most votes takes it.
 Roy
 
 
 
 -- End of Forwarded Message
 
 
 
 
 
 -- End of Forwarded Message
 
 
 

-- 


[CODE4LIB] Director of Library Desktop Support

2008-10-10 Thread Vickery, Kelly
University of Kentucky Libraries

Lexington, KY 40506-0456

www.uky.edu/Librarieshttp://www.uky.edu/Libraries

September 29, 2008

POSITION:  Director of Library Desktop Support - JOB #SP523836
AVAILABLE:  November 1, 2008
DESCRIPTION AND RESPONSIBILITIES:  The University of Kentucky Libraries seeks a 
knowledgeable, personable and technically experienced professional to serve as 
the Director of Library Desktop Support.  The Director is responsible for 
overseeing the allocation and maintenance of over 700 desktop computers for 
library staff and the public, and the distribution and proper function of 
networked printers and other computer peripherals.   The Director will manage 
library desktop support services including supervision of two full-time 
computer support personnel, and will plan and manage computer leases and 
equipment deployment and installation.  The Director will manage the technical 
support budget, handle equipment and software requests from library staff and 
faculty, evaluate requests and alternatives and seek solutions based on needs 
assessments.  The Director must be aware of workflow and processes in an 
academic library; the position will require them to orient new library faculty 
and staff on University and Library computing policy, basic computer 
operations, general library systems, and standard University computing services 
like IDs, passwords, and email.  The Director may need to conduct training or 
demonstrations for some software applications.  The successful candidate will 
be expected to possess a keen understanding of computer operations, and will be 
expected to monitor trends in information technology and new uses of computing 
and software in academic libraries.  Reporting to the Associate Dean for 
Library Information Technology, the Director of Library Desktop Support must 
communicate and maintain close interaction with most departments in the UK 
library system.  Additionally, the Director will participate in library 
committee/workgroups and other library service activities.  Interested 
applicants must attach a resume and cover letter to apply for this position.
QUALIFICATIONS
Required:  ALA-accredited MLS. Experience with library systems department 
and/or library public or staff computer support.  Supervisory experience.  
Evidence of ability to plan and implement large projects.  Excellent 
organizational and oral and written communication skills and the ability to 
work productively with a wide range of individuals and groups.  Proficient 
knowledge of current Microsoft Windows environment and MS Office applications.  
Commitment to ongoing professional development and activity; evidence of the 
ability to meet University of Kentucky requirements for promotion and tenure.
Preferred Education/Experience:  Experience working in a research university 
environment. Knowledge of Voyager, Illiad, Ariel, and other library 
applications.  Microsoft Certification.
SALARY AND BENEFITS:  Salary commensurate with qualifications and experience. 
Tenure track, faculty rank, 12 month appointment, 22 days annual leave. 
TIAA/CREF and Fidelity retirement plans. For additional benefits see 
http://www.uky.edu/HR/benefits.
LIBRARY:  Located in the beautiful bluegrass region of central Kentucky, the 
University of Kentucky Libraries system includes the main William T. Young 
Library, Medical Center Library, Law Library, Special Collections  Digital 
Programs, Agricultural Information Center, Little Fine Arts Library, Design 
Library, Education Library, Engineering Library and five science libraries. 
Combined holdings total more than 3 million volumes. The system has a faculty 
of 70 and a support and professional staff of 100 who serve a student body of 
28,000. The UK Libraries use the Voyager integrated library system. Library 
membership includes the Association of Research Libraries, SOLINET, ASERL, and 
the Center for Research Libraries. The UK Libraries is a regional depository 
for government publications.
TO APPLY for job # SP523836, a UK Academic Profile must be submitted at 
www.uky.edu/ukjobshttp://www.uky.edu/ukjobs.  If you have any questions, 
contact HR/Employment, phone (859)257-9555 press 2 or email [EMAIL 
PROTECTED]mailto:[EMAIL PROTECTED].  Application deadline is October 31, 
2008, but may be extended as needed.  Upon offer of employment, successful 
applicants for certain positions must undergo a national background check as 
required by University of Kentucky Human Resources.
The University of Kentucky is an equal opportunity employer and encourages 
applications from minorities and women.


Faculty Recruitment Webpage:

www.uky.edu/professorshttp://www.uky.edu/professors



UK in the News:

www.uky.eduhttp://www.uky.edu



Additional Information About Lexington, Kentucky and the Surrounding Area:

www.visitlex.comhttp://www.visitlex.com

www.commercelexington.comhttp://www.commercelexington.com

Re: [CODE4LIB] FW: Logo vote

2008-10-10 Thread Kevin S. Clarke
On Fri, Oct 10, 2008 at 11:29 AM, Roy Tennant [EMAIL PROTECTED] wrote:
 Well, I don't really think don't care equates to no logo, since it is
 more of an abstention than anything. And you won't find me trying to be
 funny in a vote again. So considering there was only 8% saying no, and 65%
 voting for some version of creating a logo, I felt like the question about
 whether to do it or not had been settled.

Okay.  Yes, I agree those two aren't the same.

Kevin

-- 
There are two kinds of people in the world: those who believe there
are two kinds of people and those who know better.