Re: [CODE4LIB] software package for Elec. Theses/dissertations
Hello Yan, Could you send me your program? I would like to try on. Thanks, mj On Wed, Jan 7, 2009 at 5:57 PM, Han, Yan wrote: > Hello, Colleagues, > > > > As ProQuest/UMI switched its delivery platform for Electronic Theses and > dissertations(ETD), I have developed a small software package to process > ETD. The software package does: > > 1. Unzip ProQuest/UMI ETD delivery Zipped files, and create one > directory per ETD. > > 2. Rename these ETDs into other preferred file names (in my case, > Wang_arizona_0009D_10075.xml à azu_etd_10075_sip1_m.xml) > > 3. Generate digital signature for digital preservation. > > 4. Create MARC records from ProQuest/UMI XML files. (i.e. a MRK file > will be generated for direct loading to catalog. I use III innovative and > Koha) > > 5. Create embargo notification and moving embargo ETDs to a different > directory for future loading > > > > This package saves me a lot of time to process hundreds of ETDs. The > package (size of 50kb) has a Java compiled code (class file) and Perl > Scripts. Currently I run it on Linux, but it can be run in Windows. > > > > If anyone wants to have it or give it a try, please contact me. > > > > p.s. I also have a package handling ProQuest old platform (BePress) ETD > files. > > > > Thanks, > > > > Yan Han > > The University of Arizona Libraries > > > -- Myung-Ja (mj) Han Metadata Librarian University of Illinois at Urbana-Champaign
[CODE4LIB] software package for Elec. Theses/dissertations
Hello, Colleagues, As ProQuest/UMI switched its delivery platform for Electronic Theses and dissertations(ETD), I have developed a small software package to process ETD. The software package does: 1. Unzip ProQuest/UMI ETD delivery Zipped files, and create one directory per ETD. 2. Rename these ETDs into other preferred file names (in my case, Wang_arizona_0009D_10075.xml à azu_etd_10075_sip1_m.xml) 3. Generate digital signature for digital preservation. 4. Create MARC records from ProQuest/UMI XML files. (i.e. a MRK file will be generated for direct loading to catalog. I use III innovative and Koha) 5. Create embargo notification and moving embargo ETDs to a different directory for future loading This package saves me a lot of time to process hundreds of ETDs. The package (size of 50kb) has a Java compiled code (class file) and Perl Scripts. Currently I run it on Linux, but it can be run in Windows. If anyone wants to have it or give it a try, please contact me. p.s. I also have a package handling ProQuest old platform (BePress) ETD files. Thanks, Yan Han The University of Arizona Libraries
Re: [CODE4LIB] audio/video citations in an OpenURL
Legal? Yes, as far as I know. How well resolvers will handle them may be another question. I think the openurl is designed to be extensible in terms of metadata by use of community profiles. In theory this seems fine, but I'm not sure how easy it has been to get new profiles accepted in practice. Owen On 7 Jan 2009, at 17:40, "Jonathan Rochkind" wrote: Would it be a legal OpenURL to use any of those in an OpenURL? They aren't approved for OpenURL use, right? But if I have to do something non-standard with OpenURL, might as well use a non-OpenURL standard, sure. In general, the lack of easy extensibility of OpenURL is a flaw that hopefully we will learn from in subsequent standards. Jonathan Ross Singer wrote: On Wed, Jan 7, 2009 at 11:33 AM, Jonathan Rochkind wrote: Hmm, I could send a DC KEV OpenURL (ie info:ofi/fmt:kev:mtx:dc ; there is no format for an XML DC? Kind of odd), and use the "type" element. http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadataPrefix=oai_dc&identifier=info:ofi/fmt:xml:xsd:oai_dc Other possibilities here would be: http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadataPrefix=oai_dc&identifier=info:ofi/fmt:xml:xsd:MARC21 and http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadataPrefix=oai_dc&identifier=info:ofi/fmt:xml:xsd:mods The latter is in trial use, but it would be odd for it not to be approved at some point in the not too distant future. -Ross. -- Jonathan Rochkind Digital Services Software Engineer The Sheridan Libraries Johns Hopkins University 410.516.8886 rochkind (at) jhu.edu
Re: [CODE4LIB] audio/video citations in an OpenURL
The sap2-2004 Community Profile (http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadat aPrefix=oai_dc&identifier=info:ofi/pro:sap2-2004) only recognizes oai_dc and MARC21. The mods metadata format was registered to support the rtm-2007 profile (http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadat aPrefix=oai_dc&identifier=info:ofi/pro:rtm-2007). It's possible that a SAP2-2004 resolver *could* recognize the mods metadata format, but it would be non-standard behavior. Jeff > -Original Message- > From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of > Ross Singer > Sent: Wednesday, January 07, 2009 12:01 PM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: Re: [CODE4LIB] audio/video citations in an OpenURL > > On Wed, Jan 7, 2009 at 11:33 AM, Jonathan Rochkind > wrote: > > > Hmm, I could send a DC KEV OpenURL (ie info:ofi/fmt:kev:mtx:dc ; there > > is no format for an XML DC? Kind of odd), and use the "type" element. > > http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadata Pr > efix=oai_dc&identifier=info:ofi/fmt:xml:xsd:oai_dc > > Other possibilities here would be: > > http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadata Pr > efix=oai_dc&identifier=info:ofi/fmt:xml:xsd:MARC21 > > and > > http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadata Pr > efix=oai_dc&identifier=info:ofi/fmt:xml:xsd:mods > > The latter is in trial use, but it would be odd for it not to be > approved at some point in the not too distant future. > > -Ross.
Re: [CODE4LIB] audio/video citations in an OpenURL
Would it be a legal OpenURL to use any of those in an OpenURL? They aren't approved for OpenURL use, right? But if I have to do something non-standard with OpenURL, might as well use a non-OpenURL standard, sure. In general, the lack of easy extensibility of OpenURL is a flaw that hopefully we will learn from in subsequent standards. Jonathan Ross Singer wrote: On Wed, Jan 7, 2009 at 11:33 AM, Jonathan Rochkind wrote: Hmm, I could send a DC KEV OpenURL (ie info:ofi/fmt:kev:mtx:dc ; there is no format for an XML DC? Kind of odd), and use the "type" element. http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadataPrefix=oai_dc&identifier=info:ofi/fmt:xml:xsd:oai_dc Other possibilities here would be: http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadataPrefix=oai_dc&identifier=info:ofi/fmt:xml:xsd:MARC21 and http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadataPrefix=oai_dc&identifier=info:ofi/fmt:xml:xsd:mods The latter is in trial use, but it would be odd for it not to be approved at some point in the not too distant future. -Ross. -- Jonathan Rochkind Digital Services Software Engineer The Sheridan Libraries Johns Hopkins University 410.516.8886 rochkind (at) jhu.edu
Re: [CODE4LIB] audio/video citations in an OpenURL
On Wed, Jan 7, 2009 at 11:33 AM, Jonathan Rochkind wrote: > Hmm, I could send a DC KEV OpenURL (ie info:ofi/fmt:kev:mtx:dc ; there > is no format for an XML DC? Kind of odd), and use the "type" element. http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadataPrefix=oai_dc&identifier=info:ofi/fmt:xml:xsd:oai_dc Other possibilities here would be: http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadataPrefix=oai_dc&identifier=info:ofi/fmt:xml:xsd:MARC21 and http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadataPrefix=oai_dc&identifier=info:ofi/fmt:xml:xsd:mods The latter is in trial use, but it would be odd for it not to be approved at some point in the not too distant future. -Ross.
Re: [CODE4LIB] audio/video citations in an OpenURL
If it helps, the OAI_DC http://alcme.oclc.org/openurl/servlet/OAIHandler?verb=GetRecord&metadata Prefix=oai_dc&identifier=info:ofi/fmt:xml:xsd:oai_dc Includes dc:format and dc:type, so this might fill the need of an XML DC structure. You could use the MARCXML structure I guess, but much more complicated. Could you pass the metadata by context rather than by value to give you more flexibility? What format is the metadata in natively? Owen Owen Stephens Assistant Director: eStrategy and Information Resources Central Library Imperial College London South Kensington Campus London SW7 2AZ t: +44 (0)20 7594 8829 e: o.steph...@imperial.ac.uk > -Original Message- > From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of > Jonathan Rochkind > Sent: 07 January 2009 16:34 > To: CODE4LIB@LISTSERV.ND.EDU > Subject: [CODE4LIB] audio/video citations in an OpenURL > > [ The open...@oclc.org listserv seems to be down, so I'll send this > here > instead for some feedback, ignore if you know nothing about or don't > care about OpenURL. :) ] > > There doesn't seem to be any good way to specify an audio or video > 'genre' for a SAP1/2 OpenURL. > > The "book" format has all the metadata I'd need in it for audio or > video > work specified, but just doesn't let me say audio or video (which I > guess makes sense because it's called "book"). > > But in using my link resolver as a general purpose item-finder, I > really > want to be able to send citations to it for audio or video materials > (like a CD or DVD), and them identified as audio or video materials, so > the link resolver can respond accordingly. > > Is there anything I can do at all? > > Hmm, I could send a DC KEV OpenURL (ie info:ofi/fmt:kev:mtx:dc ; there > is no format for an XML DC? Kind of odd), and use the "type" element. > "The nature or genre of the content of the resource. Type includes > terms > describing general categories, functions, genres, or aggregation levels > for content. Recommended best practice is to select a value from a > controlled vocabulary (for example, the DCMI Type Vocabulary)." I'm > having trouble finding 'the DCMI Type Vocabulary' for sure (anyone know > where I find that?), but it looks like it might include terms "Sound" > and "MovingImage". > > There's no way to actually specify which controlled vocabulary I am > using in a DC KEV OpenURL 'type' element, is there? > > If anyone thinks this makes sense and there's a way to do this, can you > give me an example of a DC KEV OpenURL with a type in it specifying > something like 'audio' or 'video'? > > Jonathan > ** > > -- > Jonathan Rochkind > Digital Services Software Engineer > The Sheridan Libraries > Johns Hopkins University > 410.516.8886 > rochkind (at) jhu.edu
Re: [CODE4LIB] audio/video citations in an OpenURL
Jonathan, I can't help with most of your problem, but I can point you to the DCMI Type Vocabulary: http://dublincore.org/documents/dcmi-type-vocabulary/ Have a nice day, Jonathan On Wed, Jan 7, 2009 at 11:33 AM, Jonathan Rochkind wrote: > [ The open...@oclc.org listserv seems to be down, so I'll send this here > instead for some feedback, ignore if you know nothing about or don't care > about OpenURL. :) ] > > There doesn't seem to be any good way to specify an audio or video > 'genre' for a SAP1/2 OpenURL. > > The "book" format has all the metadata I'd need in it for audio or video > work specified, but just doesn't let me say audio or video (which I > guess makes sense because it's called "book"). > > But in using my link resolver as a general purpose item-finder, I really > want to be able to send citations to it for audio or video materials > (like a CD or DVD), and them identified as audio or video materials, so > the link resolver can respond accordingly. > > Is there anything I can do at all? > > Hmm, I could send a DC KEV OpenURL (ie info:ofi/fmt:kev:mtx:dc ; there > is no format for an XML DC? Kind of odd), and use the "type" element. "The > nature or genre of the content of the resource. Type includes terms > describing general categories, functions, genres, or aggregation levels for > content. Recommended best practice is to select a value from a controlled > vocabulary (for example, the DCMI Type Vocabulary)." I'm having trouble > finding 'the DCMI Type Vocabulary' for sure (anyone know where I find > that?), but it looks like it might include terms "Sound" and "MovingImage". > > There's no way to actually specify which controlled vocabulary I am using in > a DC KEV OpenURL 'type' element, is there? > > If anyone thinks this makes sense and there's a way to do this, can you > give me an example of a DC KEV OpenURL with a type in it specifying > something like 'audio' or 'video'? > > Jonathan > ** > > -- > Jonathan Rochkind > Digital Services Software Engineer > The Sheridan Libraries > Johns Hopkins University > 410.516.8886 > rochkind (at) jhu.edu > -- Jonathan M. Brinley jonathanbrin...@gmail.com http://xplus3.net/
[CODE4LIB] audio/video citations in an OpenURL
[ The open...@oclc.org listserv seems to be down, so I'll send this here instead for some feedback, ignore if you know nothing about or don't care about OpenURL. :) ] There doesn't seem to be any good way to specify an audio or video 'genre' for a SAP1/2 OpenURL. The "book" format has all the metadata I'd need in it for audio or video work specified, but just doesn't let me say audio or video (which I guess makes sense because it's called "book"). But in using my link resolver as a general purpose item-finder, I really want to be able to send citations to it for audio or video materials (like a CD or DVD), and them identified as audio or video materials, so the link resolver can respond accordingly. Is there anything I can do at all? Hmm, I could send a DC KEV OpenURL (ie info:ofi/fmt:kev:mtx:dc ; there is no format for an XML DC? Kind of odd), and use the "type" element. "The nature or genre of the content of the resource. Type includes terms describing general categories, functions, genres, or aggregation levels for content. Recommended best practice is to select a value from a controlled vocabulary (for example, the DCMI Type Vocabulary)." I'm having trouble finding 'the DCMI Type Vocabulary' for sure (anyone know where I find that?), but it looks like it might include terms "Sound" and "MovingImage". There's no way to actually specify which controlled vocabulary I am using in a DC KEV OpenURL 'type' element, is there? If anyone thinks this makes sense and there's a way to do this, can you give me an example of a DC KEV OpenURL with a type in it specifying something like 'audio' or 'video'? Jonathan ** -- Jonathan Rochkind Digital Services Software Engineer The Sheridan Libraries Johns Hopkins University 410.516.8886 rochkind (at) jhu.edu
Re: [CODE4LIB] T-Shirt Design Contest
re monkeybear, coincidentally Brown University's mascot is a (brown) bear... Bonnie On Mon, Jan 5, 2009 at 10:02 PM, Genny Engel wrote: > I made two versions, black-on-white and white-on-black, for use > depending on the selected T-shirt color. > > Inspired by the video retrospective of code4lib 2007 which was shown > last year to the tune of the Code Monkey song. Except I can't really do > a monkey without it looking kind of like a bear! So this is a Code > Monkeybear. > > Genny > > > >
Re: [CODE4LIB] Code4Lib wiki -- Collaboration on open source book widgets
Yes. There are no service level guarantees or anything, but the Code4Lib wiki is available for use by code4lib community members on development projects etc. At your own risk, of course. It would be a fine place for the open source book widget project, in my opinion. We have had some problems with spammers on it. There is a way to restrict editing privileges to logged in accounts for a certain page, but I forget how. I also think that MediaWiki is less than ideal for the development documentation/collaboration purposes we're using it for, but that's what we've got! Jonathan John Miedema wrote: Is the Code4Lib wiki intended for any related use? My Code4Lib account appears to give me editing rights, so I assume it's okay, but just wanted to check. A handful of people have been talking about their shared interest in developing open source book widgets. We see that some widgets are already in existence and new ones are being developed. There is clear overlap, and we've been eyeing the Code4Lib wiki as a place to collaborate. Are we good to go? If you're interested in the discussion, please come join our list: https://lists.sourceforge.net/lists/listinfo/openbookwpress-general. John m...@johnmiedema.ca http://johnmiedema.ca "We love open source. No, you can't Yes, you can have our code." -- Jonathan Rochkind Digital Services Software Engineer The Sheridan Libraries Johns Hopkins University 410.516.8886 rochkind (at) jhu.edu
[CODE4LIB] Code4Lib wiki -- Collaboration on open source book widgets
Is the Code4Lib wiki intended for any related use? My Code4Lib account appears to give me editing rights, so I assume it's okay, but just wanted to check. A handful of people have been talking about their shared interest in developing open source book widgets. We see that some widgets are already in existence and new ones are being developed. There is clear overlap, and we've been eyeing the Code4Lib wiki as a place to collaborate. Are we good to go? If you're interested in the discussion, please come join our list: https://lists.sourceforge.net/lists/listinfo/openbookwpress-general. John m...@johnmiedema.ca http://johnmiedema.ca "We love open source. No, you can't Yes, you can have our code."
