From shiv.mail at gmail.com Mon Aug 7 08:22:45 2006 From: shiv.mail at gmail.com (Shivendra Singh) Date: Mon, 7 Aug 2006 17:52:45 +0530 Subject: [Dspace-general] its way of sorting Message-ID: Dear Members, I have installed DSpace 1.4 Beta-1 on MS windows 2000 server. At present I have uploaded more than 500 documents. I have three problems. 1. I am facing some problem in the collection during in its way of sorting. During the browsing by title and author in a collection, there are two way of sorting option, one is "sort by Title" and second is "sort by Date". Both are not sorting on its way. 2. How can I update DSpace 1.4 Beta-1 to DSpace Stable 1.4. 3. There is always showing Internal System Error during the New User registration. I do not have configured e-mail server in same server (MS Windows 2000 server) where my DSpace is installed, but have another e-mail server in Linux platform. How can I solve this problem in Windows Based server? Is it any way to create user by DOS command same as created administrator? Thanks and Regards, -- Shivendra Singh Electronic Information Retrieval System National Institute of Pharmaceutical Education & Research Sector-67, Phase-10, SAS Nagar (Mohali) Punjab-160062, India Ph: +0172-2214682-87, Ext. 2017, Mobile 9815526163. E-mail: shiv.mail at gmail.com or shivendra at niper.ac.in http://eirs.blogspot.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.mit.edu/pipermail/dspace-general/attachments/20060807/d5a624be/attachment.htm From pbm2 at cam.ac.uk Mon Aug 7 12:53:07 2006 From: pbm2 at cam.ac.uk (Peter Morgan) Date: Mon, 7 Aug 2006 17:53:07 +0100 Subject: [Dspace-general] OPEN SCHOLARSHIP 2006: NEW CHALLENGES FOR OPEN ACCESS REPOSITORIES Message-ID: Forwarded at the request of the organisers. -- Peter Morgan Project Director, DSpace at Cambridge Cambridge University Library West Road Cambridge CB3 9DR UK email: pbm2 at cam.ac.uk tel: +44 (0)1223 333130/336757 fax: +44 (0)1223 339973 ************************************************************************ * >== Apologies for any cross-posting == > >The University of Glasgow, SPARC Europe and LIBER are proud to >announce: > >OPEN SCHOLARSHIP 2006: NEW CHALLENGES FOR OPEN ACCESS REPOSITORIES > >This inaugural conference will be held at the University of >Glasgow, Scotland, UK on 18-20 October 2006. > >Open Scholarship 2006: New Challenges for Open Access >Repositories is a companion European Conference to the OAI >meetings at Cern in Geneva, and to the Nordic Scholarly >Communication Conferences, and is aimed at Librarians, >University Administrators, funders, academics and technical >specialists. > >Open access and the development of OA repositories are >transforming scholarship and bringing new opportunities and >challenges for researchers, librarians and publishers. Open >Scholarship 2006 is a pan-European conference which will focus >on these new challenges and opportunities. In addition to >tutorial sessions on advocacy and policy issues as well as >functionality and sofwtare issues, OS 2006 will address key >themes presented by many leading European practitioners in the >field of Open Access. > >Key themes will include: > > * Repository Developments > * Added Value Services > * Quality Assessment > * Policies and Implementation > * Sustainability > >The conference will also provide an opportunity for posters to >be submitted and displayed in a dedicated slot in the >programme. Posters should fit into the one of the themes >addressed by the conference [and be no larger than 1m x 1m] > >Further details about the poster session is available at >http://www.lib.gla.ac.uk/openscholarship/posters.shtml > >To register and for further information about the conference, >including the preliminary programme go to: >http://www.lib.gla.ac.uk/openscholarship > >The organising committee gratefully acknowledges our sponsors: >JISC, LIBER, SHERPA, SHERPA-Leap, Ex Libris, SURF, >EPrints.org, SPARC Europe and Proquest. > >For further information please contact us at >openscholarship at lib.gla.ac.uk > >We look forward to seeing you in Glasgow in October, > >The Organising Committee, >Open Scholarship 2006 > > >Paul Ayris, MA, Ph.D. >Director of UCL Library Services and UCL Copyright Officer >UCL (University College London) >Gower Street >London >WC1E 6BT > >Tel. +44 (0) 20-7679-7834 (Internal Ext: 37834) >Fax +44 (0) 20-7679-7373 > >Mobile: 07771974051 >E-mail: p.ayris at ucl.ac.uk > From roberttansley at google.com Mon Aug 7 14:10:32 2006 From: roberttansley at google.com (Robert Tansley) Date: Mon, 7 Aug 2006 14:10:32 -0400 Subject: [Dspace-general] [Dspace-tech] INTERNATIONAL CONFERENCE ON Semantic Web and Digital Libraries (ICSD 2007) In-Reply-To: References: Message-ID: <38d44e00608071110p2caa4228sfd140b42c5029a65@mail.google.com> A reminder, the abstract submission deadline for this conference is August 15. It would be great to get some DSpace papers in this! Rob On 15/07/06, Dimple Patel wrote: > **************Apologies for cross postings, if any************** > > > > Indian Statistical Institute Platinum Jubilee Events > > INTERNATIONAL CONFERENCE ON Semantic Web and Digital Libraries (ICSD 2007) > http://drtc.isibang.ac.in/icsd > > Documentation Research and Training Centre > Indian Statistical Institute, Bangalore, INDIA > > February 21-23, 2007 > > As part of the Indian Statistical Institute Platinum jubilee > celebrations, DRTC/ISI announces International conference on Semantic > Web and Digital Libraries. The objective is to bring together the best > expertise in the areas of Semantic Web and Digital Libraries from > leading initiatives worldwide. > > Themes include: (but not limited to) > * Digital Libraries > * Digital Resource Organization > * Technology issues in Digital Services > * Design of Digital Information Services > * Retrieval issues in digital environment > * Standards and Specifications for Digital objects > * Metadata standards, Interoperability and Crosswalks > * Knowledge Organization and Ontologies > * Semantic Web Technologies and Digital Libraries > * Semantic Web and Information Retrieval > * Architecture for Semantic Web > * Technology and Semantic Web Modeling tools > * Intelligent Agents in Semantic Retrieval > * Semantic Portals and Semantic Web Services > * Vocabulary and Taxonomy development > * Tools and Techniques for managing digital repositories > * Digital Resource Management Strategies > * Content Development: Policies > * Content Development: tools and techniques > * Technology issues in Digital Services > * Resource Media and formats > * Multilingual Digital Libraries > * Patron interaction and facilitation tools > * Digital Library applications and case studies > * Digital Library and Semantic Web Projects and Case Studies > > CALL FOR PAPERS > Original papers in English are invited on a theme related to those > mentioned above. An international review panel will review the papers > based on originality of the work, quality and relevance to the main > theme of the conference. Peer reviewed and accepted papers will be > published in the conference proceedings. The papers should follow the > submission instructions that will be furnished along with acceptance > note and also on the conference website. > > IMPORTANT DATES > * _Expression of interest to submit paper with abstract: August 15, > 2006 > * Submission of full papers: September 15, 2006 > * Notification of acceptance of paper with comments: October 31, 2006 > * Submission of the final paper after incorporating comments: November > 30, 2006 > > REGISTRATION > * Early Bird Registration: December 15, 2006 (Last Date) > Rs. 5000/- (Indian & SAARC Delegates); > USD 150 (Foriegn Delegates other than SAARC) > * After December 15: > Rs. 6000/- (Indian & SAARC Delegates); > USD 175 (Foriegn Delegates other than SAARC) > * Tutorial: > Rs. 1500/- (Indian & SAARC Delegates); > USD 40 (Foriegn Delegates other than SAARC) > > CONTACT & ENQUIRIES: (with CC to gmail address) > Dr. A.R.D.Prasad, (Conference Convenor) > Associate Professor, > Documentation Research and Training Centre, > Indian Statistical Institute, > 8th Mile, Mysore Road, Bangalore - 560 059 > Karnataka, INDIA > Phone: 91-80-28483002/3/4 extn no. 496 or 490 > Fax : 91-80-28484265 > email: icsd at drtc.isibang.ac.in > icsd2007 at gmail.com > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > > _______________________________________________ > DSpace-tech mailing list > DSpace-tech at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech > > > From rrodgers at MIT.EDU Thu Aug 10 11:50:33 2006 From: rrodgers at MIT.EDU (Richard Rodgers) Date: Thu, 10 Aug 2006 11:50:33 -0400 Subject: [Dspace-general] DSpace committers welcome 2 new members Message-ID: <1155225033.10647.182.camel@localhost.localdomain> In response to the growing demands of DSpace platform development, and in recognition of their contributions, the committers are pleased to announce 2 new members. Tim Donohue is the Research Programmer for the IDEALS repository (http://ideals.uiuc.edu) at the University of Illinois, currently in its pilot phase. Thus far, his DSpace development interests have centered on the submission user interface (e.g. the Configurable Submission patch), and local customizations of the DSpace user interface (e.g. "DSpace How-To Guide" - http://wiki.dspace.org/DspaceGuides , written with Dorothea Salo). More generally, he's interested in helping to make the DSpace platform easier to customize and manage. Claudia J?rgen is the librarian in charge of the maintenance and further development of the document server at the University Library of Dortmund https://eldorado.uni-dortmund.de/. The server was started in 1996 and migrated to DSpace in 2005. Her main interests in DSpace and institutional repositories at large are: - Long term preservation - i18n - Metadata modelling - WAI/XHTML-compliance - documentation and structured information about DSpace - making DSpace more flexible and easier to handle We know the DSpace community joins us in welcoming Tim & Claudia to the team, The DSpace Committers From mmLO at hampshire.edu Mon Aug 14 10:34:54 2006 From: mmLO at hampshire.edu (Meenu Madan) Date: Mon, 14 Aug 2006 10:34:54 -0400 Subject: [Dspace-general] Hello Message-ID: <44E08A0E.8010500@hampshire.edu> Hello All, I just subscribed to this alias. Hope to get good info from here. I'm working at Hampshire college as a Web Programmer and we have set up DSpace here to act as an archive for our final year student thesis. Now one question I had was about authorization. Is it necessary to make all communities public? Secondly Can I have authorization levels based on community, like I want to have an Admin access over community1 and give people1, people2 only read access on this community1. And at later stages change there authorization or add more people to read access. Thanks in advance. Meenu Madan Hampshire College From kenzie at MIT.EDU Mon Aug 14 11:56:20 2006 From: kenzie at MIT.EDU (MacKenzie Smith) Date: Mon, 14 Aug 2006 11:56:20 -0400 Subject: [Dspace-general] Hello In-Reply-To: <44E08A0E.8010500@hampshire.edu> Message-ID: <5.2.1.1.2.20060814115319.027f3ed0@hesiod> Hi Meenu, Welcome to the DSpace general mailing list. This list is for general questions and non-technical discussions related to the DSpace platform. Your technical questions like this one should be sent to the other list, called dspace-tech, which you can subscribe to at SourceForge http://sourceforge.net/mail/?group_id=19984 Thanks, MacKenzie Smith Associate Director for Technology MIT Libraries 10:34 AM 8/14/2006 -0400, Meenu Madan wrote: >Hello All, >I just subscribed to this alias. Hope to get good info from here. >I'm working at Hampshire college as a Web Programmer and we have set up >DSpace here to act as an archive for our final year student thesis. > >Now one question I had was about authorization. >Is it necessary to make all communities public? >Secondly Can I have authorization levels based on community, like I want >to have an Admin access over community1 and give people1, people2 only >read access on this community1. And at later stages change there >authorization or add more people to read access. > >Thanks in advance. >Meenu Madan >Hampshire College >_______________________________________________ >Dspace-general mailing list >Dspace-general at mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general From mr41 at cornell.edu Tue Aug 15 15:39:19 2006 From: mr41 at cornell.edu (Marcy Rosenkrantz) Date: Tue, 15 Aug 2006 15:39:19 -0400 Subject: [Dspace-general] Announcing iPRES 2006 Message-ID: <44E222E7.6060002@cornell.edu> Announcing iPRES 2006 With Apologies for cross posting * Are you 100% buzzword compliant in digital preservation? Have you heard of kopal? Planets? Nestor? aDORe? * Do you want to be among the first to hear about the digital preservation repository audits conducted by the Center for Research Libraries? * How about meeting the project leads from major e-journal archiving programs? * Do you need an update on national digital preservation efforts in Canada, China, Germany, the Netherlands, New Zealand, Switzerland, the US, and the UK? * Would you like to explore preservation components in repository software? If your response to some of these questions is "yes," we would like to invite you to the 3rd International Conference on the Preservation of Digital Objects (iPRES 2006), October 8-10, 2006, Cornell University, Ithaca, NY U.S.A. An impressive list of speakers have been assembled and the program is available at: http://ipres.library.cornell.edu/ Early registration closes on September 1, 2006. Come to upstate New York to view the Fall leaves, take a Finger Lakes wine tour, and get the latest information on digital preservation! Best, From pbm2 at cam.ac.uk Wed Aug 16 11:51:38 2006 From: pbm2 at cam.ac.uk (Peter Morgan) Date: Wed, 16 Aug 2006 16:51:38 +0100 Subject: [Dspace-general] FW: Open Scholarship 2006 - Early Bird registration deadline Message-ID: Forwarded at the request of the organisers. Peter -- Peter Morgan Project Director, DSpace at Cambridge Cambridge University Library West Road Cambridge CB3 9DR UK email: pbm2 at cam.ac.uk tel: +44 (0)1223 333130/336757 fax: +44 (0)1223 339973 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Dear Colleagues, ** Apologies for any cross-posting ** The Early Bird registration for OPEN SCHOLARSHIP 2006: NEW CHALLENGES FOR OPEN ACCESS REPOSITORIES closes on the 31 August (?150) and the registration fee rises to ?180 after that date. This inaugural conference will be held at the University of Glasgow, Scotland, UK on 18-20 October 2006. Open Scholarship 2006: New Challenges for Open Access Repositories is a companion European Conference to the OAI meetings at CERN in Geneva, and to the Nordic Scholarly Communication Conferences, and is aimed at Librarians, University Administrators, funders, academics and technical specialists. Key themes will include: * Repository Developments * Added Value Services * Quality Assessment * Policies and Implementation * Sustainability To register and for further information about the conference, including the programme go to: http://www.lib.gla.ac.uk/openscholarship The conference will also provide an opportunity for posters to be submitted and displayed in a dedicated slot in the programme. Posters should address one of the themes of the conference and be no larger than 1m x 1m. Further details about the poster session, including the list of themes is available at http://www.lib.gla.ac.uk/openscholarship/posters.shtml The organising committee gratefully acknowledges our sponsors: JISC, LIBER, SHERPA, SHERPA-LEAP, Ex Libris, SURF, EPrints.org, SPARC Europe, OSI, Thomson Scientific, Proquest and Biomed Central. For further information please contact us at openscholarship at lib.gla.ac.uk We look forward to seeing you in Glasgow in October, The Organising Committee, Open Scholarship 2006 Paul Ayris, MA, Ph.D. Director of UCL Library Services and UCL Copyright Officer UCL (University College London) Gower Street London WC1E 6BT Tel. +44 (0) 20-7679-7834 (Internal Ext: 37834) Fax +44 (0) 20-7679-7373 Mobile: 07771974051 E-mail: p.ayris at ucl.ac.uk From cdygert at american.edu Wed Aug 16 11:59:30 2006 From: cdygert at american.edu (Claire Dygert) Date: Wed, 16 Aug 2006 11:59:30 -0400 Subject: [Dspace-general] Claire Dygert is out of the office. Message-ID: I will be out of the office starting 08/16/2006 and will not return until 08/23/2006. If you need immediate help from the Serials/E-Resources Unit, please contact Mark Hemhauser, Serials Supervisor, at (202) 885 -3247 or by email at mbhhbm at american.edu. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.mit.edu/pipermail/dspace-general/attachments/20060816/9e8d5500/attachment.htm From emorgan at nd.edu Wed Aug 16 13:02:57 2006 From: emorgan at nd.edu (Eric Lease Morgan) Date: Wed, 16 Aug 2006 13:02:57 -0400 Subject: [Dspace-general] combining dspace, etd-db, and digitool Message-ID: <92FE6562-AB67-4E5F-9531-769DB4136EF2@nd.edu> If you plan on attending ECDL 2006 (or even if you haven't made up your mind yet), consider signing up the half-day tutorial called "Creating a more full-featured institutional repository: Combining DSpace, ETD-db, and DigiTool". For more information, see the URL and details, below: http://www.ecdl2006.org/tutorial6.jsp BTW, ECDL is a great conference. It a wonderful place to catch-up on and learn more about the most recent advancements in the development of digital libraries. 'Well worth the time. * Title - Creating a more full-featured institutional repository: Combining DSpace, ETD-db, and DigiTool. * Abstract - DSpace, ETD-db, and DigiTool are all well-respected systems designed to facilitate aspects of an institutional repository. Each have their own particular strengths and weaknesses, but none of them are perfect. By exploiting the OAI data repository features of each system the developer is able to amalgamate their content, automatically classify it, cache it centrally, and provide sets of enhanced services against the cache. Building on the strengths of each system developers are able to provide a more full- featured institutional repository system. The primary goal of this tutorial is to outline the benefits and drawbacks of such an implementation, demonstrate how it has been implemented at the University of Notre Dame, and discuss how it can be implemented with other software components. By the end of the tutorial participants will be able to: highlight the problems IR systems are expected to solve, be able to compare and contrast three IR systems, address meta- data issues regarding the organization of information in IR systems, state the advantages of amalgamating IR content into a centralized cache, discuss ways these same ideas can be implemented with a variety of software. * Duration - Half day * Experience level - Intermediate * Outline - The problems institutional repositories are trying to solve - What is an institutional repository, and what problems is it intended to solve? What qualities characterize successful institutional repository implementations? The group answers to these questions become the benchmarks for evaluating the success of repositories. Functional overview of DSpace, ETD-db, and DigiTool - Each of these applications have strengths and weaknesses. This section will enumerate them and in the process compare and contrast the applications. Developing an over-arching information architecture - In order to create a synergistic whole from the three repository applications it is necessary to apply aspects of information architecture to the systems - aspects of users, context, and content. This section will focus on the content issues and elaborate upon methods of logically organizing it using a faceted classification system. Using OAI to harvest content and cache it centrally - At first, this seems like the easy part. Point your harvester at the repository and save the output locally. After a bit of examination, issues regarding homogeneity and variations in OAI compliance come into play and adjustments need to be made. This section describes some ways to address these issues. Creating user-centered services against the cache - This is the fun part. Here we provide services against the cache. Searching (via SRU). Browsing. What's new? services. Syndicating content to campus portals. Syndicating content via RSS. Creating dynamically generated Web pages listing author publications. Calculating Google page rank. Each of these things will be described in more detail. Discussion of other ways the same things could be implemented - The implementation of Notre Dame uses specific tools to accomplish its goal. By exploiting protocols, not specific applications, these tools could easily be changed out for other tools. This section discusses these issues and provides an opportunity for participants to brainstorm other ways these techniques could be employed in their institution. * Biographical sketch - Eric Lease Morgan is the Head of the Digital Access and Information Architecture Department at the University Libraries of Notre Dame. He considers himself to be a librarian first and a computer user second. His professional goal is to discover new ways to use computers to provide better library service. Some of his more well-known investigations and implementations include MyLibrary and the Alex Catalogue of Electronic Texts. An advocate for open source software and open access publishing, Morgan has been freely distributing his software and publications for years before the terms "open source" and "open access" were coined. Morgan also hosts his own Internet domain, infomotions.com. -- Eric Lease Morgan University Libraries of Notre Dame From hany at u.library.arizona.edu Wed Aug 16 15:24:01 2006 From: hany at u.library.arizona.edu (Han, Yan) Date: Wed, 16 Aug 2006 12:24:01 -0700 Subject: [Dspace-general] DSpace v.s. MySQL In-Reply-To: <92FE6562-AB67-4E5F-9531-769DB4136EF2@nd.edu> Message-ID: <9510F1D040F68C4793F2AEEAA4C3BBC01756EB@scorpius.library.arizona.edu> I have been working with DSpace code for 2 years. Just wondering if anyone implemented MySQL w/ DSpace. How much modification will this change involve? Thanks, Yan From tyler.walters at library.gatech.edu Wed Aug 16 16:06:41 2006 From: tyler.walters at library.gatech.edu (Tyler Walters) Date: Wed, 16 Aug 2006 16:06:41 -0400 (EDT) Subject: [Dspace-general] Volunteers for DSpace Program Committee for OR2007 Message-ID: <2968.Vl0RVQBWDVY=.1155758801.squirrel@mail.library.gatech.edu> Good day DSpacers, We are now soliciting volunteers to work on the DSpace Users Group program committee for the International Conference on Open Repositories. The conference will be held in San Antonio, Texas, USA, during January 23-26, 2007. The program committees? work will take place this September-October. We are looking to create six sessions of 90 minutes each and will be putting out a call for session proposals in early September. Committee members will assist with reviewing the submissions and generating session ideas ourselves, should the need arise. If you are interested in participating on the DSpace program committee, please volunteer by contacting me no later than Thursday, August 31, 2006. We are looking to provide a very timely and worthwhile program and we hope to see many of you there. Your contributions to the committee will be very much appreciated! Kind regards, Tyler Walters Chair, DSpace Users Group Program Committee International Conference on Open Repositories, 2007 -- Tyler O. Walters Associate Director, Technology & Resource Services Library and Information Center Georgia Institute of Technology Atlanta, GA 30332-0900 404-385-4489 voice 404-894-6084 fax tyler.walters at library.gatech.edu http://www.library.gatech.edu/research_help/librarians/walters.html "Whether you think you can or think you can?t, you are right." -- Henry Ford ---------------------------------------------------------------------- This email was composed using the GTEL Webmail client. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. Georgia Tech Library and Information Center http://www.library.gatech.edu ---------------------------------------------------------------------- From hany at u.library.arizona.edu Wed Aug 16 20:10:50 2006 From: hany at u.library.arizona.edu (Han, Yan) Date: Wed, 16 Aug 2006 17:10:50 -0700 Subject: [Dspace-general] DSpace v.s. MySQL In-Reply-To: <9510F1D040F68C4793F2AEEAA4C3BBC01756EB@scorpius.library.arizona.edu> Message-ID: <9510F1D040F68C4793F2AEEAA4C3BBC01756F8@scorpius.library.arizona.edu> I forgot "NOT". I have NOT been looking at DSpace for 2years. -----Original Message----- From: dspace-general-bounces at mit.edu [mailto:dspace-general-bounces at mit.edu] On Behalf Of Han, Yan Sent: Wednesday, August 16, 2006 12:24 PM To: DSpace General Subject: [Dspace-general] DSpace v.s. MySQL I have been working with DSpace code for 2 years. Just wondering if anyone implemented MySQL w/ DSpace. How much modification will this change involve? Thanks, Yan _______________________________________________ Dspace-general mailing list Dspace-general at mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general From nabonitaguha at gmail.com Thu Aug 17 06:30:52 2006 From: nabonitaguha at gmail.com (Nabonita Guha) Date: Thu, 17 Aug 2006 16:00:52 +0530 Subject: [Dspace-general] DRTC/ISI ICSD 2007 : Extended deadlines Message-ID: <60fe5c400608170330p282f7accp79496f026dbda472@mail.gmail.com> Kindly note the extended dates for paper submission (full paper with abstract) and early bird registration. The changed dates are as follows: * Submission of full paper with abstract: September 30, 2006 * Early Bird registration: January 01, 2007 Other important dates are: * Notification of acceptance with comments: October 31, 2006 * Submission of the final papers after incorporating comments: November 30, 2006 ************************************** ICSD 2007: CALL FOR PAPERS Indian Statistical Institute Platinum Jubilee Events International Conference on SEMANTIC WEB & DIGITAL LIBRARIES (ICSD 2007) http://drtc.isibang.ac.in/icsd Documentation Research and Training Centre Indian Statistical Institute, Bangalore, INDIA February 21-23, 2007 Themes include: (but not limited to) * Digital Libraries * Digital Resource Organization * Technology issues in Digital Services * Design of Digital Information Services * Retrieval issues in digital environment * Standards and Specifications for Digital objects * Metadata standards, Interoperability and Crosswalks * Knowledge Organization and Ontologies * Semantic Web Technologies and Digital Libraries * Semantic Web and Information Retrieval * Architecture for Semantic Web * Technology and Semantic Web Modeling tools * Intelligent Agents in Semantic Retrieval * Semantic Portals and Semantic Web Services * Vocabulary and Taxonomy development * Tools and Techniques for managing digital repositories * Digital Resource Management Strategies * Content Development: Policies * Content Development: tools and techniques * Technology issues in Digital Services * Resource Media and formats * Multilingual Digital Libraries * Patron interaction and facilitation tools * Digital Library applications and case studies * Digital Library and Semantic Web Projects and Case Studies FORMAT The conference aims to explore the topics in themes and sub themes through tutorials, workshops, demonstrations, Invited talks and presentations. Eminent researchers and academicians will be invited to deliver theme papers and invited talks on select topics. CALL FOR PAPERS Original papers in English are invited on a theme related to those mentioned above. An international review panel will review the papers based on originality of the work, quality and relevance to the main theme of the conference. Peer reviewed and accepted papers will be published in the conference proceedings. The papers should follow the submission instructions that will be furnished along with acceptance note and also on the conference website. REGISTRATION * Early Bird Registration: January 01, 2006 (Last Date) Rs. 5000/- (Indian & SAARC Delegates); USD 150.00 (Foriegn Delegates other than SAARC) * After January 01, 2007: Rs. 6000/- (Indian & SAARC Delegates); USD 175.00 (Foriegn Delegates other than SAARC) * Tutorial: Rs. 1500/- (Indian & SAARC Delegates); USD 40.00 (Foriegn Delegates other than SAARC) NEWS ICSD conference brochure is now available at conference website. CONTACT & ENQUIRIES: (with CC to gmail address) Dr. A.R.D.Prasad, (Conference Convenor) Associate Professor, Documentation Research and Training Centre, Indian Statistical Institute, 8th Mile, Mysore Road, Bangalore - 560 059 Karnataka, INDIA Phone: 91-80-28483002/3/4 extn no. 496 or 490 Fax : 91-80-28484265 email: icsd at drtc.isibang.ac.in icsd2007 at gmail.com -- Nabonita Guha Junior Research Fellow, Documentation Research & Training Centre, Indian Statistical Institute, 8th Mile, Mysore Road, Bangalore - 560059 Karnataka Email: nabonitaguha at yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.mit.edu/pipermail/dspace-general/attachments/20060817/08206224/attachment.htm From emorgan at nd.edu Thu Aug 17 12:45:10 2006 From: emorgan at nd.edu (Eric Lease Morgan) Date: Thu, 17 Aug 2006 12:45:10 -0400 Subject: [Dspace-general] hacking dspace: harvests, caches, and services Message-ID: <9DCEB33F-84B8-45F4-9064-10A9748BD6E8@nd.edu> This purpose of this posting is to share with some the DSpace community ways we have been "hacking" DSpace, ETD-db, and DigiTool for the sake of open access publishing. Many of the things I outlined a number of months ago are coming to fruition. DSpace, ETD-db, and DigiTool are institutional repository-like applications. Each of these applications have their own strengths and weaknesses, but the biggest problems facing their implementation here at Notre Dame include: * they are "applications" not libraries/modules * they will always have a particular look & feel * they operate as "information silos" * they implement specific searching/browsing interfaces To overcome these issues, as well as in an effort to improve upon the functionality of an institutional repository, we here at Notre Dame have hacked (and we mean that in a good way) each of these applications to create something different. Specifically, we have exploited OAI-PMH to first harvest and cache the content from each application, and then we provide services against the cache. Some of these processes are itemized and described below. Be forewarned. The things listed below are implemented in a "sandbox". Response times will be slow, the links will change, and your milage will vary. 0. Enhanced Dublin Core - For better or for worse, we created sets of facet/term combinations (think "subjects") and inserted them into DSpace fields. When we harvest the content we note its physical structure, parse it accordingly, and cache it in a specific place. A good record to see how some of this has been implemented is here: http://dspace.library.nd.edu:8080/dspace/handle/2305/142? mode=full&submit_simple=Show+full+item+record 1. Harvest & cache - Each application has an OAI-PMH interface. We use Net::OAI::Harvester to harvest the Dublin Core metadata from each of the applications and cache the content in a (MyLibrary) database. As the content is retrieved we do a (tiny) bit of normalization, but we also supplement the metadata with facet/term combinations describing where the content came from, what format it is, and some sort of subject/descriptor. 2. Name authority - For a sub-set of our implementation, the Excellent Undergraduate Research, we needed to include photographs and short biographies of students in browsable displays. To accomplish this we first created facet/term combinations (name authorities) in our database. These authorities defined a key which pointed to a directory containing a JPEG image and more detailed information regarding the author. By combining these facet/terms, the files in the directory, and the records in DSpace we are able to create a browsable list of authors complete with pictures and bios. For example, see: http://dewey.library.nd.edu/morgan/idr/undergrad/?cmd=authors 3. Standards-based search - Each application provides search, but not in a "standard" way, nor against each other. By indexing our cache and providing an SRU interface to the index we can over come these problems. Moreover, using such an approach we can swap out our indexer at will. We began using swish-e as our indexer. We moved to Plucene (slow), and we will probably switch again. Fun: http://dewey.library.nd.edu/morgan/idr/sru/client.html 4. Syndicating content with "widgets" - The name of the game is, "Put your content were the users are; don't expect the users to come to your site." We created a number of one-line Javascript "widgets" allowing Web masters to insert content from our institutional repository into their pages. For example, the Aerospace Engineering department might want to list the recently "published" theses/ dissertations, or an author might want to do something similar. See: http://dewey.library.nd.edu/morgan/idr/widgets/widget-03.html http://dewey.library.nd.edu/morgan/idr/etd/widgets/widget-03.html http://dewey.library.nd.edu/morgan/idr/etd/?cmd=widgets 5. Pseudo peer-review - Faculty want to be recognized (and cited) by their peers. Right now the standard for this practice is publication in peer-reviewed journals and citation counts from ISI. Google is a trusted resource. ("If you don't believe me, then why do you use it so frequently?") As more and more content is made available on the Web things like Google PageRank and links from remote documents may supplement peer-review and citation counts. Using Google API's it is possible to retrieve a PageRank and lists of linking documents, and this has been implemented against some of the browsable lists in our ETD collection. See: http://dewey.library.nd.edu/morgan/idr/etd/?cmd=term&id=25 http://dewey.library.nd.edu/morgan/idr/etd/?cmd=term&id=50 Unfortunately, all of our documents have PageRanks of 0, 3, or 4, and all of the linking documents come from within our own domain. After time I think this may change. 6. Thumbnail browsing - We are using DigiTool to store images for art history classes. Not only is this content fraught with copyright issues, but the content is based on pictures, not words. As content is harvested from DigiTool's (non-standard) OAI-PMH interface we are able to "calculate" the location of thumbnail images on the remote server. Consequently we are able to provide (standard) search interfaces to the content and display pictures of hits as well as descriptions. 7. Batch loading - One problem with institutional repositories is getting content. It is hard to acquire and hard to key in. To get around this problem we searched our bibliographic indexes for things written by local authors. We saved these records to EndNote, a bibliographic citation manager. We then exported the EndNote content as an XML file, parsed the file, and saved the results in directories importable by DSpace. After importing we were able to cache the content and provide browsable interfaces against it. Using this technique it took two people less than one day to import more than 600 citations. For example: http://dewey.library.nd.edu/morgan/idr/?cmd=term&id=43331 There are a few other "kewl" features of our implementation, but the ones outlined above give you the gist of where we are going and what is possible as long as you have the data. "I don't need the interface; just give me the data." Our experiments have not been 100 percent successful. We still have some problems with controlled vocabularies, normalization, scalability, getting content in the first place, priority setting, and links to the "real" content as opposed to "splash" screens. Despite these issues, we believe thing are moving forward and in the right direction. Fun with institutional repositories. -- Eric From mark.merifield at biomedcentral.com Fri Aug 18 09:40:49 2006 From: mark.merifield at biomedcentral.com (mark.merifield@biomedcentral.com) Date: Fri, 18 Aug 2006 14:40:49 +0100 Subject: [Dspace-general] Job Vacancy - Open Repository (DSpace) Software Developer Message-ID: ***Apologies for cross-posting. Please pass this message on to anyone not on the lists who may be interested*** Job Vacancy - Open Repository (DSpace) Software Developer BioMed Central currently has a vacancy for a talented, self-motivated software developer to work in a team developing our hosted repository service built on customised DSpace software. The successful candidate should exhibit a keen willingness to work with others, have the initiative to take responsibility for their own duties when necessary, and have experience with and an understanding of institutional repository systems and issues. Must haves * DSpace or other institutional repository software (E-prints, Fedora, etc.) * Java, J2EE, Servlets, JSP, multi-threading * Struts, Spring MVC or Cocoon * An understanding of Java application frameworks (Spring, EJB3, etc.) * Apache Tomcat / HTTPD * Oracle 9i/10g / SQL Server / PostrgeSQL * HTML, CSS, JavaScript * XML, XSLT * Linux / Unix OS with bash scripting * Metadata formats and standards (e.g., Dublin Core, METS, MARC, PRISM, OAIS data model, etc.) Desirables * Warehousing of large datasets * OAI-PMH / SFX protocols * Lucene * Web Services (SOAP, JAX-WS, Axis) * Agile methodologies (Extreme Programming XP, DSDM, RUP) Candidates should have a strong, computing related university qualification and excellent A-levels. Please send your CV and covering letter, stating salary expectations and quoting job reference to: Recruitment, SNG, 34-42 Cleveland Street, London, W1T 4LB, or by email to: jobs at sciencenow.com. Any questions about the role can be sent to me off-list. Thanks, Mark Mark Merifield Open Repository Project Manager BioMed Central Middlesex House 34-42 Cleveland Street London W1T 4LB +44 (0)20 7631 9954 http://www.openrepository.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.mit.edu/pipermail/dspace-general/attachments/20060818/6f965d96/attachment.htm From Michael.Guthrie at RoyalNavalMuseum.org Tue Aug 22 05:51:13 2006 From: Michael.Guthrie at RoyalNavalMuseum.org (Michael Guthrie) Date: Tue, 22 Aug 2006 10:51:13 +0100 Subject: [Dspace-general] Metadata spreadsheet Message-ID: <0FE6871D6D854C4FB0C41DABDBD37B6904E877@vanguard.RoyalNaval.local> Hi all, I'm new to dspace and we will be implementing an instance soon, but in the meantime I am trying to create spreadsheet that our researchers can use to record metadata about digital assets while we work on getting our instance running. I am trying to determine what woudl be the relevant fields for them to use and fill in. Does anyone have an example of a resultant xml file or some advice in this regard. Thanks Michael Guthrie IT Officer 'Sea Your History' Royal Naval Museum HM Naval Base (PP66) Portsmouth Hampshire PO1 3NH Tel: 023 9272 7576 michael.guthrie at royalnavalmuseum.org -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.mit.edu/pipermail/dspace-general/attachments/20060822/2969a90b/attachment.htm From stephen.thomas at adelaide.edu.au Thu Aug 24 03:16:09 2006 From: stephen.thomas at adelaide.edu.au (Stephen Thomas) Date: Thu, 24 Aug 2006 16:46:09 +0930 Subject: [Dspace-general] The collective wisdom on handles? Message-ID: <00cf01c6c74d$2c5f4c50$984e7f81@LIBNT130> One thing that is niggling away at the back of mind is the question of handles -- whether we should be using them at this stage. We've just launched our DSpace here, and its going well so far, and even limited promo is eliciting a lot of enthusiasm. Among its virtues, we're touting the use of handles for permanent links. But ... I can't help wondering if this is wise, or indeed honest. Because what I tell people is that the handles mean the links will always work, even if we migrate to a different platform, but in fact I don't really know how true this is. If we move to new hardware while retaining DSpace, I guess there's no problem. But ... and I'm not suggesting we will, but who knows what the future may bring ... if we migrate from DSpace to something else ... ARROW, Digital commons, whatever ... will we still be able to use our handles? Or will the reliability of our handle links be predicated on sticking with DSpace? So I'm wondering what others are doing in this respect. I note that many DSpace installations don't use handle.net, but some do. So I'd like to hear from others as to what their feelings are on this issue, whether they share my concerns, and whether they use handle.net or not, and why. Regards, Steve Stephen Thomas, Senior Systems Analyst, University of Adelaide Library UNIVERSITY OF ADELAIDE SA 5005 AUSTRALIA Phone: +61 8 830 35190 Fax: +61 8 830 34369 Email: stephen.thomas at adelaide.edu.au URL: http://www.adelaide.edu.au/directory/stephen.thomas CRICOS Provider Number 00123M ----------------------------------------------------------- This email message is intended only for the addressee(s) and contains information that may be confidential and/or copyright. If you are not the intended recipient please notify the sender by reply email and immediately delete this email. Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited. No representation is made that this email or any attachments are free of viruses. Virus scanning is recommended and is the responsibility of the recipient. From r.davis at ulcc.ac.uk Thu Aug 24 09:19:22 2006 From: r.davis at ulcc.ac.uk (Richard Davis) Date: Thu, 24 Aug 2006 14:19:22 +0100 Subject: [Dspace-general] The collective wisdom on handles? In-Reply-To: <00cf01c6c74d$2c5f4c50$984e7f81@LIBNT130> References: <00cf01c6c74d$2c5f4c50$984e7f81@LIBNT130> Message-ID: <44EDA75A.2050205@ulcc.ac.uk> Stephen Thomas wrote: > So I'm wondering what others are doing in this respect. I note that many > DSpace installations don't use handle.net, but some do. So I'd like to > hear from others as to what their feelings are on this issue, whether > they share my concerns, and whether they use handle.net or not, and why. Could I second this request for others' thoughts or pointers to practical info about PIs in DSpace. Are there alternatives to Handle.Net that can be used in DSpace without too much hacking? Is there any viable exit strategy from Handle.Net, once set up and subscribed? What's the balance of pros and cons of sticking with local repository URIs for the time being? Thanks in advance! Richard -- / \ Richard M Davis / Digital Archives Specialist \ University of London Computer Centre / Tel: +44 (0) 20 7692 1350 \ mailto: r.davis at ulcc.ac.uk / From roberttansley at google.com Thu Aug 24 11:04:26 2006 From: roberttansley at google.com (Robert Tansley) Date: Thu, 24 Aug 2006 11:04:26 -0400 Subject: [Dspace-general] The collective wisdom on handles? In-Reply-To: <00cf01c6c74d$2c5f4c50$984e7f81@LIBNT130> References: <00cf01c6c74d$2c5f4c50$984e7f81@LIBNT130> Message-ID: <38d44e00608240804m23efbd86o1f5ab0789635333@mail.google.com> Hi Stephen, One of the reasons for the initial choice of Handles in DSpace is precisely because it's independent of DSpace, and would enable folks to move or replicate content into other systems. It even lets you track content replicated in multiple systems with the same identifier, as the China Digital Museum project is exploring: http://www.dlib.org/dlib/july06/tansley/07tansley.html Since Handles give you a level of indirection, it's much easier to keep the Handles pointing at the right content, whichever system your content is stored in. Otherwise, you'd have to make e.g. Digital Commons 'understand' the DSpace URL space, and you'd have to keep the host name the same. But of course Handles (as well as the underlying content) don't preserve themselves, and if you do migrate to another platform, it will be up to you to make sure the Handles still work, it doesn't happen by magic. However the Handle infrastructure is designed to make this as easy as possible (certainly easier than trying to maintain a URL space with a particular domain name etc). Plus, you wouldn't even need the new system to support the Handle system natively (although plenty, including FEDORA with a 3rd party add-on, do) -- you could just run a Handle server that redirects Handle resolutions to the appropriate page or service in your new system. In terms of alternatives, lots of folks simply don't run a Handle Service, and just: - Configure 'handle.prefix' to be something like 'id' - Fix appropriate points in the code so that the IDs appear as the URL for the item display page, instead of http://hdl.handle.net/.... This basically means that the URLs for the item display pages *are* the IDs for the objects. To use another ID scheme with a separate resolution mechanism would need some development work. I hope some pluggable API will make this easier to do in the future. In terms of an exit strategy from Handles, that would be tricky. Handles are displayed in the http://hdl.handle.net/... form because that works in browsers, and we feared if the Handles didn't work in browsers people just wouldn't use them. That may or may not have been a wise decision. The hdl:12.34/56 form is probably more 'portable' but people will still expect them to behave like Handles. So at the end of the day, of all the choices you make in setting up a long-term digital repository, identifiers is the one choice you're pretty much stuck with ad infinitum. However, the fact is that back in 2001/2002 as well as now, Handles are a proven, supported, scalable standard for portable identifiers (the fact that DOI is based on the Handle system has always given us a degree of confidence) and alternatives with the same level of functionality are thin on the ground, so they're as good a choice as any IMO. Plenty of notes on: http://wiki.dspace.org/PersistentIdentifiers Rob On 24/08/06, Stephen Thomas wrote: > One thing that is niggling away at the back of mind is the question of > handles -- whether we should be using them at this stage. > > We've just launched our DSpace here, and its going well so far, and even > limited promo is eliciting a lot of enthusiasm. Among its virtues, we're > touting the use of handles for permanent links. But ... I can't help > wondering if this is wise, or indeed honest. Because what I tell people > is that the handles mean the links will always work, even if we migrate > to a different platform, but in fact I don't really know how true this > is. > > If we move to new hardware while retaining DSpace, I guess there's no > problem. But ... and I'm not suggesting we will, but who knows what the > future may bring ... if we migrate from DSpace to something else ... > ARROW, Digital commons, whatever ... will we still be able to use our > handles? Or will the reliability of our handle links be predicated on > sticking with DSpace? > > So I'm wondering what others are doing in this respect. I note that many > DSpace installations don't use handle.net, but some do. So I'd like to > hear from others as to what their feelings are on this issue, whether > they share my concerns, and whether they use handle.net or not, and why. > > > Regards, > Steve From stephen.thomas at adelaide.edu.au Thu Aug 24 19:48:51 2006 From: stephen.thomas at adelaide.edu.au (Stephen Thomas) Date: Fri, 25 Aug 2006 09:18:51 +0930 Subject: [Dspace-general] The collective wisdom on handles? In-Reply-To: <38d44e00608240804m23efbd86o1f5ab0789635333@mail.google.com> Message-ID: <00dd01c6c7d7$da05d830$984e7f81@LIBNT130> Thanks Robert. That gives me courage to continue with handles. I guess I'd just reached that point of the project where one thinks, "OMG, am I doing the right thing here?" Thanks again, Steve Stephen Thomas, Senior Systems Analyst, University of Adelaide Library UNIVERSITY OF ADELAIDE SA 5005 AUSTRALIA Phone: +61 8 830 35190 Fax: +61 8 830 34369 Email: stephen.thomas at adelaide.edu.au URL: http://www.adelaide.edu.au/directory/stephen.thomas CRICOS Provider Number 00123M ----------------------------------------------------------- This email message is intended only for the addressee(s) and contains information that may be confidential and/or copyright. If you are not the intended recipient please notify the sender by reply email and immediately delete this email. Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited. No representation is made that this email or any attachments are free of viruses. Virus scanning is recommended and is the responsibility of the recipient. > -----Original Message----- > From: Robert Tansley [mailto:roberttansley at google.com] > Sent: Friday, 25 August 2006 12:34 am > To: Stephen Thomas > Cc: dspace-general at mit.edu > Subject: Re: [Dspace-general] The collective wisdom on handles? > > Hi Stephen, > > One of the reasons for the initial choice of Handles in DSpace is > precisely because it's independent of DSpace, and would enable folks > to move or replicate content into other systems. It even lets you > track content replicated in multiple systems with the same identifier, > as the China Digital Museum project is exploring: > http://www.dlib.org/dlib/july06/tansley/07tansley.html > > Since Handles give you a level of indirection, it's much easier to > keep the Handles pointing at the right content, whichever system your > content is stored in. Otherwise, you'd have to make e.g. Digital > Commons 'understand' the DSpace URL space, and you'd have to keep the > host name the same. > > But of course Handles (as well as the underlying content) don't > preserve themselves, and if you do migrate to another platform, it > will be up to you to make sure the Handles still work, it doesn't > happen by magic. However the Handle infrastructure is designed to > make this as easy as possible (certainly easier than trying to > maintain a URL space with a particular domain name etc). Plus, you > wouldn't even need the new system to support the Handle system > natively (although plenty, including FEDORA with a 3rd party add-on, > do) -- you could just run a Handle server that redirects Handle > resolutions to the appropriate page or service in your new system. > > In terms of alternatives, lots of folks simply don't run a Handle > Service, and just: > - Configure 'handle.prefix' to be something like 'id' > - Fix appropriate points in the code so that the IDs appear as the URL > for the item display page, instead of http://hdl.handle.net/.... > > This basically means that the URLs for the item display pages *are* > the IDs for the objects. To use another ID scheme with a separate > resolution mechanism would need some development work. I hope some > pluggable API will make this easier to do in the future. > > In terms of an exit strategy from Handles, that would be tricky. > Handles are displayed in the http://hdl.handle.net/... form because > that works in browsers, and we feared if the Handles didn't work in > browsers people just wouldn't use them. That may or may not have been > a wise decision. The hdl:12.34/56 form is probably more 'portable' > but people will still expect them to behave like Handles. > > So at the end of the day, of all the choices you make in setting up a > long-term digital repository, identifiers is the one choice you're > pretty much stuck with ad infinitum. > > However, the fact is that back in 2001/2002 as well as now, Handles > are a proven, supported, scalable standard for portable identifiers > (the fact that DOI is based on the Handle system has always given us a > degree of confidence) and alternatives with the same level of > functionality are thin on the ground, so they're as good a choice as > any IMO. > > Plenty of notes on: http://wiki.dspace.org/PersistentIdentifiers > > Rob > > On 24/08/06, Stephen Thomas wrote: > > One thing that is niggling away at the back of mind is the question > of > > handles -- whether we should be using them at this stage. > > > > We've just launched our DSpace here, and its going well so far, and > even > > limited promo is eliciting a lot of enthusiasm. Among its virtues, > we're > > touting the use of handles for permanent links. But ... I can't help > > wondering if this is wise, or indeed honest. Because what I tell > people > > is that the handles mean the links will always work, even if we > migrate > > to a different platform, but in fact I don't really know how true > this > > is. > > > > If we move to new hardware while retaining DSpace, I guess there's > no > > problem. But ... and I'm not suggesting we will, but who knows what > the > > future may bring ... if we migrate from DSpace to something else ... > > ARROW, Digital commons, whatever ... will we still be able to use > our > > handles? Or will the reliability of our handle links be predicated > on > > sticking with DSpace? > > > > So I'm wondering what others are doing in this respect. I note that > many > > DSpace installations don't use handle.net, but some do. So I'd like > to > > hear from others as to what their feelings are on this issue, > whether > > they share my concerns, and whether they use handle.net or not, and > why. > > > > > > Regards, > > Steve From S.C.Corn at lboro.ac.uk Fri Aug 25 04:58:35 2006 From: S.C.Corn at lboro.ac.uk (S.C.Corn) Date: Fri, 25 Aug 2006 09:58:35 +0100 Subject: [Dspace-general] Accessibility & screen readers Message-ID: <001d01c6c824$a5de1250$98507d9e@lboro.ac.uk> Hi, I'm interested in accessibility for visually-impaired users and wondered if anyone had tried accessing Dspace with a screenreader such as JAWS? Any info. gratefully received! Many thanks, Steve. Stephen Corn Support Services Librarian Loughborough University 01509 222348 From mark.merifield at biomedcentral.com Wed Aug 30 10:14:18 2006 From: mark.merifield at biomedcentral.com (mark.merifield@biomedcentral.com) Date: Wed, 30 Aug 2006 15:14:18 +0100 Subject: [Dspace-general] Job Vacancy - Open Repository (DSpace) Software Developer Message-ID: > ***Apologies for cross-posting (and re-posting!). Please pass this message on to anyone you know who may be interested*** > > Job Vacancy - Open Repository (DSpace) Software Developer > > BioMed Central currently has a vacancy for a talented, self-motivated software developer to work in a team developing our hosted repository service built on customised DSpace software. The successful candidate should exhibit a keen willingness to work with others, have the initiative to take responsibility for their own duties when necessary, and have experience with and an understanding of institutional repository systems and issues. > > Must haves > * DSpace or other institutional repository software (E-prints, Fedora, etc.) > * Java, J2EE, Servlets, JSP, multi-threading > * Struts, Spring MVC or Cocoon > * An understanding of Java application frameworks (Spring, EJB3, etc.) > * Apache Tomcat / HTTPD > * Oracle 9i/10g / SQL Server / PostrgeSQL > * HTML, CSS, JavaScript > * XML, XSLT > * Linux / Unix OS with bash scripting > * Metadata formats and standards (e.g., Dublin Core, METS, MARC, PRISM, OAIS data model, etc.) > > Desirables > * Warehousing of large datasets > * OAI-PMH / SFX protocols > * Lucene > * Web Services (SOAP, JAX-WS, Axis) > * Agile methodologies (Extreme Programming XP, DSDM, RUP) > > Candidates should have a strong, computing related university qualification and excellent A-levels. The position is based in London. > > Please send your CV and covering letter, stating salary expectations and quoting job reference to: Recruitment, SNG, 34-42 Cleveland Street, London, W1T 4LB, or by email to: jobs at sciencenow.com. > > Any questions about the role should be sent to me off-list. > Many thanks, > Mark > > > Mark Merifield > Open Repository Project Manager > > BioMed Central > Middlesex House > 34-42 Cleveland Street > London W1T 4LB > +44 (0)20 7631 9954 > > http://www.openrepository.com > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.mit.edu/pipermail/dspace-general/attachments/20060830/38f7ba03/attachment.htm