[CODE4LIB] code4lib 2009 conference registration is *open*

2008-12-17 Thread Birkin James Diana

Y'all let me know if you experience any glitches.

https://library.brown.edu/code4libcon09/registration/form/

---
Birkin James Diana
Programmer, Integrated Technology Services
Brown University Library
birkin_di...@brown.edu


Re: [CODE4LIB] code4lib 2009 conference registration is *open*

2008-12-17 Thread Wick, Ryan
I'm stuck on the first page. I have everything filled out, pre-confs
selected, but when I click the Continue to confirmation button, the
page reloads, and there is no error at all. Just all my information like
I had it.

Ryan Wick

-Original Message-
From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
Birkin James Diana
Sent: Wednesday, December 17, 2008 9:03 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] code4lib 2009 conference registration is *open*

Y'all let me know if you experience any glitches.

https://library.brown.edu/code4libcon09/registration/form/

---
Birkin James Diana
Programmer, Integrated Technology Services Brown University Library
birkin_di...@brown.edu


Re: [CODE4LIB] code4lib 2009 conference registration is *open*

2008-12-17 Thread Ryan Eby
Is the a count of current registrations somewhere? I remember there
being one last year I think.

eby

On Wed, Dec 17, 2008 at 1:26 PM, Wick, Ryan ryan.w...@oregonstate.edu wrote:
 I'm stuck on the first page. I have everything filled out, pre-confs
 selected, but when I click the Continue to confirmation button, the
 page reloads, and there is no error at all. Just all my information like
 I had it.

 Ryan Wick

 -Original Message-
 From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
 Birkin James Diana
 Sent: Wednesday, December 17, 2008 9:03 AM
 To: CODE4LIB@LISTSERV.ND.EDU
 Subject: [CODE4LIB] code4lib 2009 conference registration is *open*

 Y'all let me know if you experience any glitches.

 https://library.brown.edu/code4libcon09/registration/form/

 ---
 Birkin James Diana
 Programmer, Integrated Technology Services Brown University Library
 birkin_di...@brown.edu



Re: [CODE4LIB] code4lib 2009 conference registration is *open*

2008-12-17 Thread Jean Rainwater
We didn't get around to doing a feed.  At 1:40pm EDT we're currently at 98.
-- Jean


On 12/17/08 1:36 PM, Ryan Eby ryan...@gmail.com wrote:

 Is the a count of current registrations somewhere? I remember there
 being one last year I think.
 
 eby
 
 On Wed, Dec 17, 2008 at 1:26 PM, Wick, Ryan ryan.w...@oregonstate.edu wrote:
 I'm stuck on the first page. I have everything filled out, pre-confs
 selected, but when I click the Continue to confirmation button, the
 page reloads, and there is no error at all. Just all my information like
 I had it.
 
 Ryan Wick
 
 -Original Message-
 From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
 Birkin James Diana
 Sent: Wednesday, December 17, 2008 9:03 AM
 To: CODE4LIB@LISTSERV.ND.EDU
 Subject: [CODE4LIB] code4lib 2009 conference registration is *open*
 
 Y'all let me know if you experience any glitches.
 
 https://library.brown.edu/code4libcon09/registration/form/
 
 ---
 Birkin James Diana
 Programmer, Integrated Technology Services Brown University Library
 birkin_di...@brown.edu
 


[CODE4LIB] glitch - on the case

2008-12-17 Thread Birkin James Diana
Lots of folk have successfully registered; 2 folk just noted a  
problem; I'm looking into it.


-b

---
Birkin James Diana
Programmer, Integrated Technology Services
Brown University Library
birkin_di...@brown.edu


Re: [CODE4LIB] glitch - on the case

2008-12-17 Thread Birkin James Diana
Hmmnn... Can't duplicate the single problem 2 folk mentioned. Folk are  
continuing to successfully register. I'll followup offline with the 2  
(though public questions welcome) and post an update here.


On Dec 17, 2008, at 1:40 PM, Birkin James Diana wrote:

Lots of folk have successfully registered; 2 folk just noted a  
problem; I'm looking into it.


---
Birkin James Diana
Programmer, Integrated Technology Services
Brown University Library
birkin_di...@brown.edu


[CODE4LIB] glitch update

2008-12-17 Thread Birkin James Diana

Update...

3 folk got stuck at registration page. I believe it's validation on  
the 'Affiliation' field that I don't have displaying, so you'd never  
know. The instance I duplicated had a period in that field; worked  
when the period was removed.


I'll fix soon, but if anyone else had this, try again without  
punctuation.


---
Birkin James Diana
Programmer, Integrated Technology Services
Brown University Library
birkin_di...@brown.edu


Re: [CODE4LIB] RDA - a standard that nobody will notice?

2008-12-17 Thread Rob Sanderson
My first question would be:  Why?

Why invent a new element for title (etc.) rather than using Dublin Core?
Wouldn't it have been easier to do this building from SWAP?
http://www.ukoln.ac.uk/repositories/digirep/index/Eprints_Application_Profile

And my second question would be: Really?

251 elements!! Man... At least they're not just numbers, but ... do you
expect anyone to actually use it?

Rob


Re: [CODE4LIB] [Fwd: Re: [CODE4LIB] RDA - a standard that nobody will notice?]

2008-12-17 Thread Bill Dueber
On Wed, Dec 17, 2008 at 10:13 AM, Diane I. Hillmann 
metadata.ma...@gmail.com wrote:

 I'd suggest that some specific use cases for what would be gained by open
 access and how that would provide value for libraries as well as the web
 communities might be the most useful thing right now.


I guess I'd be interested in the specific use cases where closed-access
would provide value for libraries.

 -Bill-


[CODE4LIB] RDA - a standard that nobody will notice?

2008-12-17 Thread Jakob Voss

Hi,

As you may already noticed the Resource Description and Access (RDA) 
cataloguing instructions will be published 2009. You can submit final 
comments on the full draft until February 2nd:


http://www.collectionscanada.gc.ca/jsc/rda.html
http://www.collectionscanada.gc.ca/jsc/rdafulldraft.html

Although there are several details you can argue about (and despite the 
questions whether detailed cataloguing rules have a future at all when 
people do cataloguing in LibraryThing, BibSonomy etc. without rules) I 
think that RDA is a step in the right direction. But there are some 
serious problems with the publication of RDA that should be of your 
interest:



1.) the standard is scattered in a set of PDF files instead of clean web 
based HTML (compare with the W3C recommendations). You cannot easily 
browse and search in RDA with your browser and a public search engine of 
your choice. You cannot link to a specific paragraph to cite RDA in a 
weblog positing etc. This shows me that the authors are still bound in 
physical world of dusty books instead of the digital age.



2.) RDA is not going to be published freely available on the web at all! 
See http://www.collectionscanada.gc.ca/jsc/rdafaq.html#7 Another reason 
why you won't be able to refer to specific sections of RDA. Defining a 
standard without putting in on Open Access (ideally under a specific 
CC-license) is retrogressive practise and a good strategy to make people 
ignored, misinterprete and violated it (you could also argue ethically 
that its a shame for every librarian not putting his publications under 
Open Access but the argument of quality should be enough).



3.) There are no official URIs for the elements of RDA. It looks like 
there has been no progress compared to FRBR (IFLA failed to publish an 
official RDF encoding of FRBR so several people created their own 
vocabularies). To encode bibliographic data on the Semantic web you need 
URIs for classes and properties. I don't expect RDA to get published as 
a full ontology but at least you could determine the basic concepts and 
elements and provide common URIs that people can build on. There are 
several attempts to create ontologies for bibliographic data but most of 
them come from outside the professional library community. Without 
connection to the Semantic Web RDA will be irrelevant outside the 
library world. With official URIs people can build on RDA and create a 
common ontology of it. Deirdre Kiorgaard did a good job in collecting 
elements [1] and Eversberg provides a database to start with.



What do you think about my concerns? We should try to get the JSC to 
make RDA Open Access, prepared for use in the Web and even prepared for 
the Semantic Web. This should not be too difficult - the main work is 
convincing people (ok, it may be difficult to convince people ;-). I'd 
be glad if you send your comments to the Joint Steering Committee for 
Development of RDA until February 2nd:


http://www.collectionscanada.gc.ca/jsc/rdadraftcomments.html

It would be a pitty if RDA is an irrelevant anachronism from the 
beginning just because it is not published the way standards need to be 
published on the Web.



Greetings
Jakob Voss

[1] http://www.collectionscanada.gc.ca/jsc/docs/5rda-elementanalysisrev.pdf

[2] A helpful tool for structured temporary access to RDA is provided by 
Bernhard Eversberg at http://www.biblio.tu-bs.de/db/wtr/detail.php - 
this is what should be provided officially!


--
Jakob Voß jakob.v...@gbv.de, skype: nichtich
Verbundzentrale des GBV (VZG) / Common Library Network
Platz der Goettinger Sieben 1, 37073 Göttingen, Germany
+49 (0)551 39-10242, http://www.gbv.de


Re: [CODE4LIB] RDA - a standard that nobody will notice?

2008-12-17 Thread Karen Coyle

Rob Sanderson wrote:

My first question would be:  Why?

Why invent a new element for title (etc.) rather than using Dublin Core?
Wouldn't it have been easier to do this building from SWAP?
http://www.ukoln.ac.uk/repositories/digirep/index/Eprints_Application_Profile

And my second question would be: Really?

251 elements!! Man... At least they're not just numbers, but ... do you
expect anyone to actually use it?

Rob


  
There are very few elements in RDA that have a real DC equivalent 
(although you'll find somewhere in the RDA documentation an RDA-to-DC 
crosswalk). Title may be the only one that could use the DC term, but I 
also have to confess that title as an element is not actually used in 
RDA -- only specific types of title (title proper, parallel title, 
etc.). The list we were working from had 'headers' like title, followed 
by specific elements, and we haven't yet decided if these headers become 
classes. So the element title is an anomaly, and there are a small 
number of others in the list that will require more study. That said, if 
the RDA 'title' has sub-elements for types of title, then I don't think 
we can use dcterms:title as it is defined.See the note under 
http://dublincore.org/documents/dcmi-terms/#terms-title.


251 elements -- well, have you looked at RDA? That's why we want to 
develop application profiles -- so that people can select only the 
elements they actually need. RDA attempts to cover all possible 
cataloging situations (as did AACR) so it's full of instructions that 
will be used only by very specialized libraries. (Note that MARC has 175 
fields and 1711 subfields -- and many of those subfields are what we 
would call 'elements'. RDA does not cover everything that is in MARC, so 
an actually data format that includes RDA will need many more than the 
RDA 251.)


kc

--
---
Karen Coyle / Digital Library Consultant
kco...@kcoyle.net http://www.kcoyle.net
ph.: 510-540-7596   skype: kcoylenet
fx.: 510-848-3913
mo.: 510-435-8234



[CODE4LIB] Job announcement: Digital Applications Librarian, Oregon State University Libraries

2008-12-17 Thread Ryan Ordway

Please excuse cross-postings

JOB ANNOUNCEMENT:

Digital Applications Librarian, Oregon State University Libraries

Oregon State University Libraries seeks a collaborative, innovative  
and service-oriented Librarian to develop and implement next  
generation digital access and storage systems. The incumbent joins an  
agile and innovative library that is responsible for the development  
of scholarsarch...@osu (the 8th ranked U.S. digital repository),  
internationally recognized digital collections, the Oregon Explorer  
natural resources digital library, the LibraryFind metasearch  
application, and countless other digital initiatives.


The Digital Applications Librarian is part of the Libraries’ Digital  
Access Services department and reports to the head of the department.  
The department supports the libraries’ continued transition to the  
digital information environment by providing digital access, and  
developing digital access tools, for the information resources that  
are essential to the research of the university and the citizens of  
Oregon. The department manages digital access and information  
management tools including the integrated library system, digital  
repositories, digital collections, link resolver, ejournal and  
database A-Z lists, proxy software, and other emerging applications.  
Department staff and librarians organize and provide access to all  
formats of library resources using these tools, and are increasingly  
responsible for facilitating open access to university-produced  
digital resources and to the libraries’ unique archival and special  
collections.



Position Responsibilities


The position investigates, recommends, implements and develops  
existing and emerging information management applications and  
technologies including the libraries’ DSpace and CONTENTdm digital  
repository systems and a next generation integrated library system.  
The first project for the incumbent will be the evaluation and  
implementation of a next generation integrated library system. The  
position maintains in-depth knowledge of digital repository and  
integrated library systems, particularly open source systems. The  
position assesses system effectiveness in meeting operational library  
needs such as circulation, acquisitions, serials, cataloging and  
metadata assignment. In addition, the position makes creative use of  
APIs, continually enhances and extends commercial, locally developed  
and open source applications, develops tools to enhance workflows and  
provides vision and leadership in the implementation of emerging  
information technologies. This is a tenure-track position that  
participates in scholarly research/publication and performs service  
activities in order to meet promotion and tenure requirements.


Required Qualifications


1) A Masters degree from an ALA-accredited program or an advanced  
degree from a computer science/information science program, as well as  
two or more years experience working in libraries or an academic  
setting.


2)   Proficient in at least one object oriented language (C++, Java,  
Python).


3)   Excellent communication, interpersonal and organizational skills.

4)   Demonstrated ability to work effectively and collegially with a  
diverse population.


5)   Demonstrated experience with Unix or Linux server platforms,  
related software, and basic system administration utilities.


6)   Creativity and strong analytical and problem-solving skills

7)   Ability to learn new technical skills quickly; ability to meet  
deadlines; strong service orientation.


8)   A demonstrable commitment to promoting and enhancing diversity.

Preferred Qualifications


1)   Hands-on experience implementing and managing library  
applications, digital repository systems or integrated library systems.


2)   Experience implementing and developing open source library  
applications.


3)   Working knowledge of CONTENTdm and DSpace digital repository  
systems.


4)   Knowledge of XML, OAI-PMH and/or OAI/ORE.


Employment Conditions:  This position is a full-time, 12-month, fixed  
annual tenure track appointment at the rank of Assistant/Associate  
Professor. Appointment at either the Assistant or Associate Professor  
level will depend on the successful candidates’ record of  
achievement.Renewal is at the discretion of the University Librarian.   
Salary range of  $42,000-$55,000  annually plus medical, dental and  
life insurance; staff tuition fee privileges for employee or a  
dependent at an Oregon University System school (restrictions apply).   
This position earns 15 hours of vacation and 8 hours of sick leave  
each month.


Application Procedure and deadline:

For a complete announcement, qualifications and application procedures  
see http://oregonstate.edu/jobs, posting 0003664.  For full  
consideration, apply by January 19, 2009.  OSU is an AA/EOE.






--
Ryan Ordway   E-mail: 

Re: [CODE4LIB] RDA - a standard that nobody will notice?

2008-12-17 Thread Karen Coyle

Jakob Voss wrote:


1.) the standard is scattered in a set of PDF files instead of clean 
web based HTML (compare with the W3C recommendations). You cannot 
easily browse and search in RDA with your browser and a public search 
engine of your choice. You cannot link to a specific paragraph to cite 
RDA in a weblog positing etc. This shows me that the authors are still 
bound in physical world of dusty books instead of the digital age.
These files are an output from the underlying XML that will fuel the 
online system. As you may know, no print output is anticipated -- this 
was done because the online system wasn't ready for the review period. 
(Thus: hang on to these files; they may be the only version of RDA you 
ever see!)





2.) RDA is not going to be published freely available on the web at 
all! See http://www.collectionscanada.gc.ca/jsc/rdafaq.html#7 Another 
reason why you won't be able to refer to specific sections of RDA. 
Defining a standard without putting in on Open Access (ideally under a 
specific CC-license) is retrogressive practise and a good strategy to 
make people ignored, misinterprete and violated it (you could also 
argue ethically that its a shame for every librarian not putting his 
publications under Open Access but the argument of quality should be 
enough).


Right, there's nothing like making standards unavailable as a way to 
promote their use :-)





3.) There are no official URIs for the elements of RDA. It looks like 
there has been no progress compared to FRBR (IFLA failed to publish an 
official RDF encoding of FRBR so several people created their own 
vocabularies). To encode bibliographic data on the Semantic web you 
need URIs for classes and properties. I don't expect RDA to get 
published as a full ontology but at least you could determine the 
basic concepts and elements and provide common URIs that people can 
build on.


This IS being done at the NSDL metadata registry.
 General URL: http://metadataregistry.org
 RDA elements: http://metadataregistry.org/schema/show/id/1.html
 RDA agent roles: http://metadataregistry.org/schema/show/id/4.html

We are also working on discovering and coding the various value 
vocabularies in RDA. Click on the Vocabularies link on the Metadata 
Registry home page. You'll find some RDA vocabularies, like:

  RDA base material: http://metadataregistry.org/vocabulary/show/id/35.html

It's been hard developing these because, as you can see, RDA has been 
created as a document and the information is buried within it. We are 
not yet in sync with the latest version of the text. But in any case, 
these properties and vocabularies all have URIs. There are no classes 
defined as yet, since RDA itself does not define anything in the RDF 
sense of things, but eventually we may be able to add those.


FRBR will also be included in the registry. It is currently in the 
registry 'sandbox' awaiting a decision by IFLA on the domain to use in 
the URI. But you can see tests of it here:


FRBR entities:  
http://sandbox.metadataregistry.org/vocabulary/show/id/49.html
FRBR relationships:  
http://sandbox.metadataregistry.org/vocabulary/show/id/90.html
FRBR relationships as concepts:  
http://sandbox.metadataregistry.org/vocabulary/show/id/64.html

user tasks:  http://sandbox.metadataregistry.org/vocabulary/show/id/69.html
 
In addition, there are some attempts to code RDA-based cataloging on the 
DC/RDA site, using the cataloging use cases that various folks have 
contributed (and there are more coming):


http://dublincore.org/dcmirdataskgroup/Scenarios

Click on the link to the right of the scenario (e.g. Scenarios/1) and 
you'll see a turtle representation of the cataloging scenario using the 
URIs from the registry.


kc
p.s. And Please Feel Free to participate in this project with us. We are 
doing it all in 'spare time'







What do you think about my concerns? We should try to get the JSC to 
make RDA Open Access, prepared for use in the Web and even prepared 
for the Semantic Web. This should not be too difficult - the main work 
is convincing people (ok, it may be difficult to convince people ;-). 
I'd be glad if you send your comments to the Joint Steering Committee 
for Development of RDA until February 2nd:





--
---
Karen Coyle / Digital Library Consultant
kco...@kcoyle.net http://www.kcoyle.net
ph.: 510-540-7596   skype: kcoylenet
fx.: 510-848-3913
mo.: 510-435-8234



[CODE4LIB] Job Announcement: Repository Software Programmer (Colorado Alliance of Research Libraries, Denver, CO)

2008-12-17 Thread Jessica Colati
(Apologies for cross-postings)

Repository Software Programmer

The ADR Software Programmer works to support consortial digital
repository initiatives by designing, developing, implementing, and
maintaining tools and applications for use in support of the
Fedora-based repository [http://www.fedora-commons.org/]. Position open
until filled; Application review begins January 2, 2009.

For full description, including tasks, requirements and compensation
details, please see:
http://www.coalliance.org/index.php?option=com_contenttask=viewid=271;
Itemid=103. 


About the ADR

The Alliance Digital Repository (ADR) [http://adr.coalliance.org] is a
consortial digital repository service currently in production release at
the Colorado Alliance of Research Libraries.  The repository actively
develops and maintains a set of services built supporting ingest, search
and discovery; digital object delivery and presentation; and
preservation of digital content (i.e. digital images, text, audio files,
video, and other content).
 
__

Jessica Branco Colati
Project Director
Alliance Digital Repository
Colorado Alliance of Research Libraries 
3801 E. Florida, Suite 515 
Denver, CO 80210 
t: (303) 759-3399 x113
f: (303) 759-3363
e: jess...@coalliance.org 
w: http:///adr.coalliance.org
w: http://www.coalliance.org 


[CODE4LIB] [Fwd: Re: [CODE4LIB] RDA - a standard that nobody will notice?]

2008-12-17 Thread Diane I. Hillmann

Jakob:

I'm glad you're interested in RDA and think it's a step in the right 
direction.  I'd like to update you on a few issues you mention in your 
post, however, which I hope will reassure you a bit.


Jakob Voss wrote:

Hi,

As you may already noticed the Resource Description and Access (RDA) 
cataloguing instructions will be published 2009. You can submit final 
comments on the full draft until February 2nd:


http://www.collectionscanada.gc.ca/jsc/rda.html
http://www.collectionscanada.gc.ca/jsc/rdafulldraft.html

Although there are several details you can argue about (and despite 
the questions whether detailed cataloguing rules have a future at all 
when people do cataloguing in LibraryThing, BibSonomy etc. without 
rules) I think that RDA is a step in the right direction. But there 
are some serious problems with the publication of RDA that should be 
of your interest:



1.) the standard is scattered in a set of PDF files instead of clean 
web based HTML (compare with the W3C recommendations). You cannot 
easily browse and search in RDA with your browser and a public search 
engine of your choice. You cannot link to a specific paragraph to cite 
RDA in a weblog positing etc. This shows me that the authors are still 
bound in physical world of dusty books instead of the digital age.



The PDF is output from XML files built and maintained for the purpose of 
providing a web-based product based on RDA, providing cataloging users 
with some of the functionality they're looking for.  It's not clear 
whether the kind of linking you mention will be possible, but the 
impediments to it are not technical.
2.) RDA is not going to be published freely available on the web at 
all! See http://www.collectionscanada.gc.ca/jsc/rdafaq.html#7 Another 
reason why you won't be able to refer to specific sections of RDA. 
Defining a standard without putting in on Open Access (ideally under a 
specific CC-license) is retrogressive practise and a good strategy to 
make people ignored, misinterprete and violated it (you could also 
argue ethically that its a shame for every librarian not putting his 
publications under Open Access but the argument of quality should be 
enough).


There's still a lot of discussion about how RDA will be made available.  
There's a great deal of concern about whether the licensing regime 
proposed by the RDA publishers will be affordable by small users, but 
also how the goal of making RDA usable beyond the traditional library 
community will be accomplished under such a regime. Many of us have been 
concerned that an already hard sell for RDA implementation will be made 
even harder by lack of open access for at least the most general 
portions of the guidance text.  I think that there's still room to argue 
for more openness, but I'd suggest that some specific use cases for what 
would be gained by open access and how that would provide value for 
libraries as well as the web communities might be the most useful thing 
right now.


3.) There are no official URIs for the elements of RDA. It looks like 
there has been no progress compared to FRBR (IFLA failed to publish an 
official RDF encoding of FRBR so several people created their own 
vocabularies). To encode bibliographic data on the Semantic web you 
need URIs for classes and properties. I don't expect RDA to get 
published as a full ontology but at least you could determine the 
basic concepts and elements and provide common URIs that people can 
build on. There are several attempts to create ontologies for 
bibliographic data but most of them come from outside the professional 
library community. Without connection to the Semantic Web RDA will be 
irrelevant outside the library world. With official URIs people can 
build on RDA and create a common ontology of it. Deirdre Kiorgaard did 
a good job in collecting elements [1] and Eversberg provides a 
database to start with.



There are indeed URIs for the RDA Elements, as well as for the RDA Role 
vocabulary and increasingly, the value vocabularies.  These are 
registered with the NSDL Registry (http://metadataregistry.org).  They 
have URIs, vocabulary descriptions, definitions (when available), RDF 
encodings and XML schemas (at the vocabulary level).  Unfortunately, 
this activity is not linked from the official RDA pages, but in fact 
the activity is going on under the aegis of the DCMI/RDA Task Group, 
working with the JSC and CoP to build this essential piece of 
infrastructure needed for RDA. The work is being funded by the British 
Library and Siderean Software, and also represents a great deal of 
volunteer effort by librarians and web professionals. You can take a 
look at the Task Group's wiki at 
http://dublincore.org/dcmirdataskgroup/FrontPage, where you can see the 
extensive work that has been done with specific cataloger (and 
developer) scenarios based on the registered vocabularies.  The intent 
is to have this work completed and reviewed in parallel to the 

[CODE4LIB] Wiki page for finding roommates, sharing rides, sightseeing

2008-12-17 Thread Wick, Ryan
I started a new wiki page for those looking for roommates for the
conference, those who'd like to share rides, sightsee with others, or
anything else anyone wants to add related to attending the conference.

http://wiki.code4lib.org/index.php/RoommatesRidesEtc

You don't need an account to edit the wiki (although it'd be great if
you signed up for one). You can use a * for a bulleted list.

Feel free to add as much or as little information or preferences to the
listing as you want. Probably some form of contact as well. And if you
do make arrangements with someone, please update your status.

Ryan Wick
Information Technology Consultant
Special Collections
Oregon State University Libraries
http://osulibrary.oregonstate.edu/specialcollections