Re: [CODE4LIB] DOI scraping

2013-05-17 Thread Owen Stephens
I'd say yes to the investment in jQuery generally - not too difficult to get the basics if you already use javascript, and makes some things a lot easier It sounds like you are trying to do something not dissimilar to LibX http://libx.org ? (except via bookmarklet rather than as a browser

Re: [CODE4LIB] DOI scraping

2013-05-17 Thread Joe Hourcle
On May 17, 2013, at 12:32 AM, Fitchett, Deborah wrote: Kia ora koutou, I’m wanting to create a bookmarklet that will let people on a journal article webpage just click the bookmarklet and get a permalink to that article, including our proxy information so it can be accessed off-campus.

[CODE4LIB] Policies for 3D Printers

2013-05-17 Thread Edward Iglesias
Hello All, It looks like we will be getting a 3D printer in the library and it is now my job to write up a policy for its use. Do any of you have similar policies you would be willing to share? Thanks, Edward Iglesias

Re: [CODE4LIB] Policies for 3D Printers

2013-05-17 Thread Nate Hill
This is a draft that will be tweaked and go before our board very soon. Feedback from the group is greatly appreciated. ### Chattanooga Public Library (CPL) is committed to offering community access to new and emerging technologies as part of our public computing services. In this age of digital

Re: [CODE4LIB] Policies for 3D Printers

2013-05-17 Thread Edward Iglesias
This looks great! I think we are in a slightly better position for part of this since we can point to the Student Handbook for the thou shalt nots Edward Iglesias On Fri, May 17, 2013 at 8:10 AM, Nate Hill nathanielh...@gmail.com wrote: This is a draft that will be tweaked and go before our

Re: [CODE4LIB] Policies for 3D Printers

2013-05-17 Thread Eric Lease Morgan
(I don't envy the job of articulating policies, and our profession sure is full of rules! --ELM)

[CODE4LIB] On-going support for DL projects

2013-05-17 Thread Tim McGeary
I'm interested in starting or joining discussions about best practices for on-going support for digital library projects. In particular, I'm looking at non-repository projects, such as projects built on applications like Omeka. In the repository context, there are initiatives like APTrust and

Re: [CODE4LIB] On-going support for DL projects

2013-05-17 Thread Robert Forkel
Good questions. I'm a programmer for a project lasting 4 years which will create quite a few web applications with uncertain future once the project ends. So what I have in mind is something like graceful degradation of these services. E.g. most of these apps make use of a javascript mapping

[CODE4LIB] Announcing Open Annotation Tutorial at JCDL 2013

2013-05-17 Thread Jacob Jett
Hi all, I hope that this announcement will be of some interest those on the list; the Open Annotation Community Group (http://www.w3.org/community/openannotation/) will be hosting a half-day tutorial describing their new Annotation Data Model (http://www.openannotation.org/spec/core/) at JCDL

Re: [CODE4LIB] On-going support for DL projects

2013-05-17 Thread Joe Hourcle
On May 17, 2013, at 9:51 AM, Tim McGeary wrote: I'm interested in starting or joining discussions about best practices for on-going support for digital library projects. In particular, I'm looking at non-repository projects, such as projects built on applications like Omeka. In the

[CODE4LIB] Job: Emerging Technology and Systems Librarian at University of Wisconsin-Green Bay

2013-05-17 Thread jobs
WORKING TITLE: Emerging Technology and Systems Librarian UW SYSTEM OFFICIAL TITLE: Academic Librarian POSTING DATE: May 16, 2013 POSITION NUMBER: A165 ESSENTIAL JOB FUNCTIONS: The Emerging Technology and Systems Librarian reports to the Library Director and provides leadership

Re: [CODE4LIB] Policies for 3D Printers

2013-05-17 Thread Ramirez, Rue
Nate, are you planning to charge for use of the 3D printer and what is the charge model? -- Rue -- Rue - Renulfo (Rue) Ramirez Associate University Librarian Library Systems Information Technology University of British Columbia

Re: [CODE4LIB] Policies for 3D Printers

2013-05-17 Thread Wilhelmina Randtke
Yes, that was my only comment. Supplies can can get expensive. Will you charge, and how will you handle that? It seems like it's not so different from recouping toner and paper when a person makes a Xerox. Putting pricing in the policy is a little too detailed, but maybe it should reference a

Re: [CODE4LIB] Policies for 3D Printers

2013-05-17 Thread Nate Hill
Yeah, costs are important but not part of a policy. We've got $800 worth of filament which we expect will last us a long, long time. Rather than charge for prints, we are trying to create a different type of social contract in the space... we are encouraging heavy users to contribute back and

Re: [CODE4LIB] Policies for 3D Printers

2013-05-17 Thread BWS Johnson
Salvete! We've got $800 worth of filament which we expect will last us a long, long time. Rather than charge for prints, we are trying to create a different type of social contract in the space... we are encouraging heavy users to contribute back and donate time, expertise, and materials.

Re: [CODE4LIB] On-going support for DL projects

2013-05-17 Thread Kevin Hawkins
These are good questions. Digital humanities centers have been dealing with these questions as they've accumulated projects, and sometimes they have dumped them on libraries to try to preserve. Leslie Johnston has experience with this, which she summarized recently:

Re: [CODE4LIB] On-going support for DL projects

2013-05-17 Thread Thomas Krichel
Kevin Hawkins writes Digital humanities centers have been dealing with these questions as they've accumulated projects, and sometimes they have dumped them on libraries to try to preserve. dumped maybe but I would still try to see this as an opportunity for libraries to move into a

Re: [CODE4LIB] On-going support for DL projects

2013-05-17 Thread Roy Tennant
On Fri, May 17, 2013 at 7:14 AM, Robert Forkel xrotw...@googlemail.com wrote: Good questions. Or once the web framework is no longer supported, there should be an export mechanism to create a set of static resources which can be hosted with just a webserver. Completely agree. This should be