Re: [CODE4LIB] Open Source Institutional Repository Software?
Phil Cryer wrote: On Fri, 2008-08-22 at 09:21 -0600, Binkley, Peter wrote: Note that having said Fedora, you're only half-way there: you still need a front end. Fez is popular, but Muradora was very well spoken of at RIRI last week (http://vre.upei.ca/riri/), and UPEI is doing very interesting work putting Drupal in front of Fedora (they're planning to release code shortly, having been distracted over the summer by an impromptu ILS migration that cost them 5 whole weeks - honestly, you wonder what these people do all day). Muradora's future was in doubt for a while due to reorganization of the development team, but the most recent word is that it will continue to be developed. The open-ness of Fedora, and it's lack of a front end, has been a hurdle for many to overcome before adoption, but from what I saw at RIRI last week, the work the UPEI staff is doing is very nice, leveraging Drupal, which is a great app. Richard Green (Univ of Hull) was big on promoting Muradora with examples and current posts from the dev group that they are going to continue. I'd like to see them target Fedora 3.0 and release that soon, same to be said about Fez, who have working 3.0 bids in svn currently. What I've taken away from RIRI is that Fedora-commons is ready for business on the backend, but needs search, acl and front-ends plugged in, and will for some time. One of my ideas is get Solr running with FC (something we failed to get accomplished at RIRI) and then build a front end that just looks at Solr. I'm sure there's more to it, but I'm going to start looking, thanks for the Open collections link, I already heard back from them, they're integrating Solr now, and will be working on a fedora-commons plugin next year... It's worth noting that Fedora Commons and DSpace are now officially collaborating. Chances are that the the DSpace Manakin UI could sit on top of Fedora services. Much of the work that is going on is in providing functionality such that Fedora will be an *Institutional* repository, not just a web site for presenting a collection of a couple hundred digital objects for a unit library. While I haven't worked with Alfresco I know one of the core developers and have done some development using a JCR-170 content repository (the standard that Alfresco uses and it's really flexible.
[CODE4LIB] Job Posting: Senior Developer, Columbia University Library Center for Digital Research and Scholarship
Hi, We have a Developer position open at Columbia University Library's Center for Digital Research and Scholarship. Position Title: Senior Developer The Center for Digital Research and Scholarship (CDRS) [http://cdrs.columbia.edu/] at Columbia University seeks a Senior Developer to help implement its online platform and applications. CDRS serves the digital research and scholarly communication needs of faculty, graduate students, and scholars through the innovative creation and implementation of online tools and services. Working in a multi-host and heterogeneous application environment with the Fedora repository software at its core, the Senior Developer will code, integrate, and maintain services and applications that support digital object ingest, preservation, search, discovery, distribution, and presentation. The position requires the design, implementation, testing, and documentation of custom software applications; the integration and extension of various open-source solutions; and the manipulation of large metadata sets. This position reports to the Lead Developer. Requirements: - Bachelor's degree in Computer Science or equivalent required; advanced degree desirable - 3-5 years of related experience required, with a minimum of 2 years of Java experience highly preferred and experience with other programming languages, such as PHP, Python, or Ruby also highly desirable - Extensive experience with XML technologies; experience with XQuery and XML schemas highly preferred - Extensive experience with relational databases, database design, and fluency in SQL strongly desired - Strong Java skills and object-oriented design experience, including knowledge of core libraries, Servlets, JDBC - Extensive familiarity with the Unix/Linux environment Preferred: - Experience with Web services technologies (SOAP/WSDL) - Experience with the Fedora repository software and issues related to knowledge representation and management - Experience with Apache Web server and Tomcat application server - Knowledge of RESTful architectures and HTTP - Familiarity with existing tools and standards of the semantic Web (RDF, OWL, triplestores) Columbia offers a competitive benefits package that includes 26 days of paid vacation and a tuition exemption for employees (graduate and undergraduate) and their qualified family members (undergraduate only). Applicants must apply via: http://jobs.columbia.edu/applicants/Central?quickFind=112188 Please include salary requirements in cover letter.
Re: [CODE4LIB] Open Source Institutional Repository Software?
On Fri, 2008-08-22 at 09:21 -0600, Binkley, Peter wrote: > Note that having said Fedora, you're only half-way there: you still need > a front end. Fez is popular, but Muradora was very well spoken of at > RIRI last week (http://vre.upei.ca/riri/), and UPEI is doing very > interesting work putting Drupal in front of Fedora (they're planning to > release code shortly, having been distracted over the summer by an > impromptu ILS migration that cost them 5 whole weeks - honestly, you > wonder what these people do all day). Muradora's future was in doubt for > a while due to reorganization of the development team, but the most > recent word is that it will continue to be developed. The open-ness of Fedora, and it's lack of a front end, has been a hurdle for many to overcome before adoption, but from what I saw at RIRI last week, the work the UPEI staff is doing is very nice, leveraging Drupal, which is a great app. Richard Green (Univ of Hull) was big on promoting Muradora with examples and current posts from the dev group that they are going to continue. I'd like to see them target Fedora 3.0 and release that soon, same to be said about Fez, who have working 3.0 bids in svn currently. What I've taken away from RIRI is that Fedora-commons is ready for business on the backend, but needs search, acl and front-ends plugged in, and will for some time. One of my ideas is get Solr running with FC (something we failed to get accomplished at RIRI) and then build a front end that just looks at Solr. I'm sure there's more to it, but I'm going to start looking, thanks for the Open collections link, I already heard back from them, they're integrating Solr now, and will be working on a fedora-commons plugin next year... P > You'll end up with very different beasts depending on what you choose, > so you really need to list Fedora+Fez, Fedora+Muradora, etc. as separate > options. > > Peter > > > > -Original Message- > > From: Code for Libraries [mailto:[EMAIL PROTECTED] On > > Behalf Of Edward M. Corrado > > Sent: Thursday, August 21, 2008 2:25 PM > > To: CODE4LIB@LISTSERV.ND.EDU > > Subject: [CODE4LIB] Open Source Institutional Repository Software? > > > > Hello all, > > > > I've been investigating possible solutions for the beginnings > > of a repository of electronic documents [1]. At this point, > > we have no budget, so I am only looking at Open Source > > options. I've identified a number of options that may meet > > our needs that are either advertised as institutional > > repository software or digital library software. Basically > > what I am wonder is am I missing some OSS programs that in > > these categories that might work for us. Software that I have > > identified so far that looks promising are: > > > > DSpace: http://www.dspace.org/ > > Fedora: http://www.fedora-commons.org/ > > E-prints: http://www.eprints.org/ > > Greenstone: www.*greenstone*.org/ > > Kete: http://kete.net.nz/ > > Rescarta: http://www.rescarta.org/ > > > > > > I have identified some others, but rejected them because they > > were either experimental or appear not to be in current > > development. At this point we haven't really narrowed down > > our focus, so almost any digital library or institutional > > repository program would be under consideration, providing it > > is 1) somewhat fully developed (again, no budget), 2) > > somewhat easy to use and install, 3) has some level of user > > base, and 4) is actively being maintained. Does anyone have > > any suggestions for other software to investigate > > > > Edward > > > > [1] I'm not going to call this an institutional repository, > > because what > > I am envision is more of a hybrid of a digital library and > > institutional > > repository. I'd be less vague, but I only have a vague idea > > of what we want. > > > > -- Phil Cryer | Open Source Development | Missouri Botanical Garden www: http://mobot.org | latitude, longitude: 38.613877, -90.257943 email: phildotcryeratmobotdotorg | im googletalk/skype: phil.cryer
Re: [CODE4LIB] Open Source Institutional Repository Software?
Thanks Jade. I think I saw this one mentioned somewhere a month or so ago but I couldn't find it when I was searching for options. Edward Anderson, Jade N wrote: You could check out Open Collection too: http://www.opencollection.org/ My Digital Libraries class at UT chose it (over Greenstone, DSpace, and Fedora) to create a digital collection last semester. It is newer but they are actively developing it, fixing bugs, etc. Jade __ Jade Anderson Information Architect University of Texas Libraries [EMAIL PROTECTED] 512.495.4431 -Original Message- From: Code for Libraries [mailto:[EMAIL PROTECTED] On Behalf Of Nicole Engard Sent: Friday, August 22, 2008 7:14 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Open Source Institutional Repository Software? I just learned about Alfresco yesterday: http://wiki.alfresco.com/wiki/Main_Page was this one that you decided against - or is it new to you? --- Nicole C. Engard Open Source Evangelist, LibLime (888) Koha ILS (564-2457) ext. 714 [EMAIL PROTECTED] AIM/Y!/Skype: nengard http://liblime.com http://blogs.liblime.com/open-sesame/ On Thu, Aug 21, 2008 at 4:25 PM, Edward M. Corrado <[EMAIL PROTECTED]> wrote: Hello all, I've been investigating possible solutions for the beginnings of a repository of electronic documents [1]. At this point, we have no budget, so I am only looking at Open Source options. I've identified a number of options that may meet our needs that are either advertised as institutional repository software or digital library software. Basically what I am wonder is am I missing some OSS programs that in these categories that might work for us. Software that I have identified so far that looks promising are: DSpace: http://www.dspace.org/ Fedora: http://www.fedora-commons.org/ E-prints: http://www.eprints.org/ Greenstone: www.*greenstone*.org/ Kete: http://kete.net.nz/ Rescarta: http://www.rescarta.org/ I have identified some others, but rejected them because they were either experimental or appear not to be in current development. At this point we haven't really narrowed down our focus, so almost any digital library or institutional repository program would be under consideration, providing it is 1) somewhat fully developed (again, no budget), 2) somewhat easy to use and install, 3) has some level of user base, and 4) is actively being maintained. Does anyone have any suggestions for other software to investigate Edward [1] I'm not going to call this an institutional repository, because what I am envision is more of a hybrid of a digital library and institutional repository. I'd be less vague, but I only have a vague idea of what we want.
Re: [CODE4LIB] Open Source Institutional Repository Software?
If you are after a quick and easy proof of concept, that requires no programming skill, then I would plump for EPrints.org - there's even a debian package for it, which makes it really easy to install 2008/8/22 Edward M. Corrado <[EMAIL PROTECTED]>: > Ben O'Steen wrote: >> >> 2008/8/22 David Kane <[EMAIL PROTECTED]>: >> >>> >>> I use EPrints, which is great. >>> >>> Do look out for Microsoft's offering though, which is in the pipeline. >>> It >>> will be free. Of course It will need to run on a Windows server and will >>> be >>> optimised for SQL Server. >>> >> >> Er.. it will *only* run on the most recent SQLServer - their repo is a >> shim on top of SQLServers native XPath handling system, as far as I >> could make out. From talking to them, they seem to have convinced a >> SQLServer that it is really an RDF triplestore, and have added a few >> gui things on top. >> >> My actual advice to the first poster however, is that if you have no >> resources (money and/or time) then don't bother with an IR - it will >> require time, effort and probably money. If you feel up to putting in >> that time and effort, then fantastic, but don't be mislead that it >> won't suck up your time. >> >> > > I should have clarified... we have time to support and grow it, but not time > to program it (since we don't have any programmers). Also, we plan on having > money in the future, but we need to get something up and running now in > order to convince the people with money to provide it to us for this > purpose. Kind of a chicken and an egg thing. > > Edward > > > >> Ben O'Steen >> Software Engineer, >> Oxford University >> >> >>> >>> David. >>> >>> >>> -- >>> David Kane >>> Systems Librarian >>> Waterford Institute of Technology >>> http://library.wit.ie/ >>> T: ++353.51302838 >>> M: ++353.876693212 >>> >>> >
Re: [CODE4LIB] Open Source Institutional Repository Software?
Hi Nicole, Thanks for the suggestion. I haven't seen this one before. Edward Nicole Engard wrote: I just learned about Alfresco yesterday: http://wiki.alfresco.com/wiki/Main_Page was this one that you decided against - or is it new to you? --- Nicole C. Engard Open Source Evangelist, LibLime (888) Koha ILS (564-2457) ext. 714 [EMAIL PROTECTED] AIM/Y!/Skype: nengard http://liblime.com http://blogs.liblime.com/open-sesame/ On Thu, Aug 21, 2008 at 4:25 PM, Edward M. Corrado <[EMAIL PROTECTED]> wrote: Hello all, I've been investigating possible solutions for the beginnings of a repository of electronic documents [1]. At this point, we have no budget, so I am only looking at Open Source options. I've identified a number of options that may meet our needs that are either advertised as institutional repository software or digital library software. Basically what I am wonder is am I missing some OSS programs that in these categories that might work for us. Software that I have identified so far that looks promising are: DSpace: http://www.dspace.org/ Fedora: http://www.fedora-commons.org/ E-prints: http://www.eprints.org/ Greenstone: www.*greenstone*.org/ Kete: http://kete.net.nz/ Rescarta: http://www.rescarta.org/ I have identified some others, but rejected them because they were either experimental or appear not to be in current development. At this point we haven't really narrowed down our focus, so almost any digital library or institutional repository program would be under consideration, providing it is 1) somewhat fully developed (again, no budget), 2) somewhat easy to use and install, 3) has some level of user base, and 4) is actively being maintained. Does anyone have any suggestions for other software to investigate Edward [1] I'm not going to call this an institutional repository, because what I am envision is more of a hybrid of a digital library and institutional repository. I'd be less vague, but I only have a vague idea of what we want.
Re: [CODE4LIB] Open Source Institutional Repository Software?
Ben O'Steen wrote: 2008/8/22 David Kane <[EMAIL PROTECTED]>: I use EPrints, which is great. Do look out for Microsoft's offering though, which is in the pipeline. It will be free. Of course It will need to run on a Windows server and will be optimised for SQL Server. Er.. it will *only* run on the most recent SQLServer - their repo is a shim on top of SQLServers native XPath handling system, as far as I could make out. From talking to them, they seem to have convinced a SQLServer that it is really an RDF triplestore, and have added a few gui things on top. My actual advice to the first poster however, is that if you have no resources (money and/or time) then don't bother with an IR - it will require time, effort and probably money. If you feel up to putting in that time and effort, then fantastic, but don't be mislead that it won't suck up your time. I should have clarified... we have time to support and grow it, but not time to program it (since we don't have any programmers). Also, we plan on having money in the future, but we need to get something up and running now in order to convince the people with money to provide it to us for this purpose. Kind of a chicken and an egg thing. Edward Ben O'Steen Software Engineer, Oxford University David. -- David Kane Systems Librarian Waterford Institute of Technology http://library.wit.ie/ T: ++353.51302838 M: ++353.876693212
Re: [CODE4LIB] Open Source Institutional Repository Software?
Good point, Peter. Edward, it's also worth considering your institution's overall user experience goals. Here at UVA, we want to give users a single place to go, instead of having to search the repository and the library catalog, so the front end for our Fedora repository is going to be Blacklight (also open source: http:// blacklight.rubyforge.org), the same as the front end for our library catalog. You can see an example here (still in development, so be kind), of a search that has retrieved both a book from the catalog and images from our repository: http://blacklightdev.lib.virginia.edu/catalog?q%5B%5D=Radburn Bess Elizabeth (Bess) Sadler Research and Development Librarian Digital Scholarship Services Box 400129 Alderman Library University of Virginia Charlottesville, VA 22904 [EMAIL PROTECTED] (434) 243-2305 On Aug 22, 2008, at 11:21 AM, Binkley, Peter wrote: Note that having said Fedora, you're only half-way there: you still need a front end. Fez is popular, but Muradora was very well spoken of at RIRI last week (http://vre.upei.ca/riri/), and UPEI is doing very interesting work putting Drupal in front of Fedora (they're planning to release code shortly, having been distracted over the summer by an impromptu ILS migration that cost them 5 whole weeks - honestly, you wonder what these people do all day). Muradora's future was in doubt for a while due to reorganization of the development team, but the most recent word is that it will continue to be developed. You'll end up with very different beasts depending on what you choose, so you really need to list Fedora+Fez, Fedora+Muradora, etc. as separate options. Peter -Original Message- From: Code for Libraries [mailto:[EMAIL PROTECTED] On Behalf Of Edward M. Corrado Sent: Thursday, August 21, 2008 2:25 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] Open Source Institutional Repository Software? Hello all, I've been investigating possible solutions for the beginnings of a repository of electronic documents [1]. At this point, we have no budget, so I am only looking at Open Source options. I've identified a number of options that may meet our needs that are either advertised as institutional repository software or digital library software. Basically what I am wonder is am I missing some OSS programs that in these categories that might work for us. Software that I have identified so far that looks promising are: DSpace: http://www.dspace.org/ Fedora: http://www.fedora-commons.org/ E-prints: http://www.eprints.org/ Greenstone: www.*greenstone*.org/ Kete: http://kete.net.nz/ Rescarta: http://www.rescarta.org/ I have identified some others, but rejected them because they were either experimental or appear not to be in current development. At this point we haven't really narrowed down our focus, so almost any digital library or institutional repository program would be under consideration, providing it is 1) somewhat fully developed (again, no budget), 2) somewhat easy to use and install, 3) has some level of user base, and 4) is actively being maintained. Does anyone have any suggestions for other software to investigate Edward [1] I'm not going to call this an institutional repository, because what I am envision is more of a hybrid of a digital library and institutional repository. I'd be less vague, but I only have a vague idea of what we want.
Re: [CODE4LIB] Open Source Institutional Repository Software?
Note that having said Fedora, you're only half-way there: you still need a front end. Fez is popular, but Muradora was very well spoken of at RIRI last week (http://vre.upei.ca/riri/), and UPEI is doing very interesting work putting Drupal in front of Fedora (they're planning to release code shortly, having been distracted over the summer by an impromptu ILS migration that cost them 5 whole weeks - honestly, you wonder what these people do all day). Muradora's future was in doubt for a while due to reorganization of the development team, but the most recent word is that it will continue to be developed. You'll end up with very different beasts depending on what you choose, so you really need to list Fedora+Fez, Fedora+Muradora, etc. as separate options. Peter > -Original Message- > From: Code for Libraries [mailto:[EMAIL PROTECTED] On > Behalf Of Edward M. Corrado > Sent: Thursday, August 21, 2008 2:25 PM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: [CODE4LIB] Open Source Institutional Repository Software? > > Hello all, > > I've been investigating possible solutions for the beginnings > of a repository of electronic documents [1]. At this point, > we have no budget, so I am only looking at Open Source > options. I've identified a number of options that may meet > our needs that are either advertised as institutional > repository software or digital library software. Basically > what I am wonder is am I missing some OSS programs that in > these categories that might work for us. Software that I have > identified so far that looks promising are: > > DSpace: http://www.dspace.org/ > Fedora: http://www.fedora-commons.org/ > E-prints: http://www.eprints.org/ > Greenstone: www.*greenstone*.org/ > Kete: http://kete.net.nz/ > Rescarta: http://www.rescarta.org/ > > > I have identified some others, but rejected them because they > were either experimental or appear not to be in current > development. At this point we haven't really narrowed down > our focus, so almost any digital library or institutional > repository program would be under consideration, providing it > is 1) somewhat fully developed (again, no budget), 2) > somewhat easy to use and install, 3) has some level of user > base, and 4) is actively being maintained. Does anyone have > any suggestions for other software to investigate > > Edward > > [1] I'm not going to call this an institutional repository, > because what > I am envision is more of a hybrid of a digital library and > institutional > repository. I'd be less vague, but I only have a vague idea > of what we want. > >
Re: [CODE4LIB] Open Source Institutional Repository Software?
On Fri, 22 Aug 2008, Leslie Johnston wrote: Agreed that you need a label for the function/tool/platform. I have been in many discussions that went around and around on the word "repository." Some folks liked it because it was a reasonably generic term for a class of tool that had some physical association with a place where things are stored/saved. Some folks hated it because, well, who knows what the heck a repository is, and how do you explain it to people who have no clue what it might be or how it would be of use to them? I was at workshop a few years back, and my boss made a comment that 'repository' comes from 'repose', which suggests that the materials are being placed there to never be used again. 'Archive' suggests that the materials have value, and are being stored for some later use. Of course, this is also the same person who's been known to refer to our archive as 'write once, read never'. (jokingly, of course, as we have regular connections from other sites, trying to mirror our whole collection) -Joe
Re: [CODE4LIB] Open Source Institutional Repository Software?
You could check out Open Collection too: http://www.opencollection.org/ My Digital Libraries class at UT chose it (over Greenstone, DSpace, and Fedora) to create a digital collection last semester. It is newer but they are actively developing it, fixing bugs, etc. Jade __ Jade Anderson Information Architect University of Texas Libraries [EMAIL PROTECTED] 512.495.4431 -Original Message- From: Code for Libraries [mailto:[EMAIL PROTECTED] On Behalf Of Nicole Engard Sent: Friday, August 22, 2008 7:14 AM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Open Source Institutional Repository Software? I just learned about Alfresco yesterday: http://wiki.alfresco.com/wiki/Main_Page was this one that you decided against - or is it new to you? --- Nicole C. Engard Open Source Evangelist, LibLime (888) Koha ILS (564-2457) ext. 714 [EMAIL PROTECTED] AIM/Y!/Skype: nengard http://liblime.com http://blogs.liblime.com/open-sesame/ On Thu, Aug 21, 2008 at 4:25 PM, Edward M. Corrado <[EMAIL PROTECTED]> wrote: > Hello all, > > I've been investigating possible solutions for the beginnings of a > repository of electronic documents [1]. At this point, we have no budget, so > I am only looking at Open Source options. I've identified a number of > options that may meet our needs that are either advertised as institutional > repository software or digital library software. Basically what I am wonder > is am I missing some OSS programs that in these categories that might work > for us. Software that I have identified so far that looks promising are: > > DSpace: http://www.dspace.org/ > Fedora: http://www.fedora-commons.org/ > E-prints: http://www.eprints.org/ > Greenstone: www.*greenstone*.org/ > Kete: http://kete.net.nz/ > Rescarta: http://www.rescarta.org/ > > > I have identified some others, but rejected them because they were either > experimental or appear not to be in current development. At this point we > haven't really narrowed down our focus, so almost any digital library or > institutional repository program would be under consideration, providing it > is 1) somewhat fully developed (again, no budget), 2) somewhat easy to use > and install, 3) has some level of user base, and 4) is actively being > maintained. Does anyone have any suggestions for other software to > investigate > > Edward > > [1] I'm not going to call this an institutional repository, because what I > am envision is more of a hybrid of a digital library and institutional > repository. I'd be less vague, but I only have a vague idea of what we want. >
Re: [CODE4LIB] Open Source Institutional Repository Software?
Agreed that you need a label for the function/tool/platform. I have been in many discussions that went around and around on the word "repository." Some folks liked it because it was a reasonably generic term for a class of tool that had some physical association with a place where things are stored/saved. Some folks hated it because, well, who knows what the heck a repository is, and how do you explain it to people who have no clue what it might be or how it would be of use to them? Often these discussions ended up with a desire to come up with a name for the public facing service so we never had to tell anyone what a repo was but could tell them to use "Edgar" or whatever to add or find collections. Not that coming up with a name is any easier... Just as I was leaving UVA 4 months ago we started to internally refer to "Library managed content" for digital materials of all sorts that were under local control. It successfully draws a circle around a class of activities — managing and delivering collections housed in the local environment, but again, it draws a line between those collections and the majority of the Library's digital content — ejournals and databases. The distinction between local and remote should be transparent to users so, again, not so useful on the public-facing side. Very useful on the administrative side, though. Leslie >>> Jonathan Rochkind <[EMAIL PROTECTED]> 8/21/2008 5:22 PM >>> I agreewholeheartedly with "there is no digital library, it's just the library". And just the library increasingly has not only it's collections but it's services digital and online (is digital reference part of the 'digital library'? can you have a 'digital library' without online reference? Forget it, it's just the library, but that library better be increasingly digital if it wants to survive. ) But of course, you still need some name for this class of software intended to be a platform for your digital stuff, possibly with preservation, possibly with workflow built in, possibly not. But it's a platform to hold your digital stuff. One of my local colleagues says "digital shelves", which sounds good to me. "Digital library" I don't like for the reasons Leslie mentioned, and because I've always been confused as to why the "library" in "digital library" is understood to just be talking about _stuff_, about collections, , when we all work in libraries and know a library is more than just it's collections! "Institutional repository", talk about jargon, and yeah, it's not clear to me _why_ we'd draw such a distinction between digital copies of our own institutional output, and digital copies of other stuff. But if we did need such a special name for our own institution's output, didn't we already have the word "archives" for that? What's the point of all these new jargony phrases? They seem only to serve to seperate off certain organizational activities and collections in their own silos, when they ought to be integrated into a "single business" model instead. Jonathan Leslie Johnston wrote: > I have grown to really dislike the phrase "digital library." > > In my last job most folks referred to "The DL" when they meant the > digital collection repository (NOT an IR, but a repo for digitized > library collections). Some of us kept making the point that "digital > library" meant not just digitized physical collections, but databases > and ejournals and licensed digital images and GIS data and faculty > publications and born-digital scholarship and so on. And even if we > used the phrase more inclusively, it seemed silly to semantically > segregate that content from the physical collections just because it was > digital. > > There is no digital library — it's just the library. > > Leslie > > -- > Leslie Johnston > Digital Media Project Coordinator > Office of Strategic Initiatives > Library of Congress > 202-707-2801 > [EMAIL PROTECTED] > > -- Jonathan Rochkind Digital Services Software Engineer The Sheridan Libraries Johns Hopkins University 410.516.8886 rochkind (at) jhu.edu
Re: [CODE4LIB] Open Source Institutional Repository Software?
I just learned about Alfresco yesterday: http://wiki.alfresco.com/wiki/Main_Page was this one that you decided against - or is it new to you? --- Nicole C. Engard Open Source Evangelist, LibLime (888) Koha ILS (564-2457) ext. 714 [EMAIL PROTECTED] AIM/Y!/Skype: nengard http://liblime.com http://blogs.liblime.com/open-sesame/ On Thu, Aug 21, 2008 at 4:25 PM, Edward M. Corrado <[EMAIL PROTECTED]> wrote: > Hello all, > > I've been investigating possible solutions for the beginnings of a > repository of electronic documents [1]. At this point, we have no budget, so > I am only looking at Open Source options. I've identified a number of > options that may meet our needs that are either advertised as institutional > repository software or digital library software. Basically what I am wonder > is am I missing some OSS programs that in these categories that might work > for us. Software that I have identified so far that looks promising are: > > DSpace: http://www.dspace.org/ > Fedora: http://www.fedora-commons.org/ > E-prints: http://www.eprints.org/ > Greenstone: www.*greenstone*.org/ > Kete: http://kete.net.nz/ > Rescarta: http://www.rescarta.org/ > > > I have identified some others, but rejected them because they were either > experimental or appear not to be in current development. At this point we > haven't really narrowed down our focus, so almost any digital library or > institutional repository program would be under consideration, providing it > is 1) somewhat fully developed (again, no budget), 2) somewhat easy to use > and install, 3) has some level of user base, and 4) is actively being > maintained. Does anyone have any suggestions for other software to > investigate > > Edward > > [1] I'm not going to call this an institutional repository, because what I > am envision is more of a hybrid of a digital library and institutional > repository. I'd be less vague, but I only have a vague idea of what we want. >
Re: [CODE4LIB] Open Source Institutional Repository Software?
Just as an aside I'd look at how you want items deposited. We use eprints for our Master's Theses and they get cataloged. If you want faculty at a number of locations to submit work with just a few tags you might want to look at dspace. Another consideration is harvesting. Both of these allow OAI harvesting. The other thing I would look at is what you plan to put up. We are starting to host some honors projects and I had to break it to the Graduate Committee that only two dimensional objects would work so that sculpture while nice ... ~ Edward Iglesias Systems Librarian Central Connecticut State University On Fri, Aug 22, 2008 at 7:29 AM, Rob Sanderson <[EMAIL PROTECTED]>wrote: > To throw in my 2c. > > > Eric Lease Morgan wrote: > > > On Aug 21, 2008, at 4:34 PM, Jonathan Rochkind wrote: > > >> If you can figure out what the difference between an 'institutional > > >> repository' and a 'digital library' is, let me know. > > > I think an institutional repository is a type of digital library. > > I think the set of "institutional repository" is a subset of the set of > "digital library". The defining feature being that IRs are designed to > be updated relatively frequently, by more than one or two people, and > typically non technical members of an institution. This happens via a > user UI, rather than via an admin UI. The contents of the IR are > research output, whereas a DL can hold anything. > > Rob > -- Edward Iglesias
Re: [CODE4LIB] Open Source Institutional Repository Software?
To throw in my 2c. > Eric Lease Morgan wrote: > > On Aug 21, 2008, at 4:34 PM, Jonathan Rochkind wrote: > >> If you can figure out what the difference between an 'institutional > >> repository' and a 'digital library' is, let me know. > > I think an institutional repository is a type of digital library. I think the set of "institutional repository" is a subset of the set of "digital library". The defining feature being that IRs are designed to be updated relatively frequently, by more than one or two people, and typically non technical members of an institution. This happens via a user UI, rather than via an admin UI. The contents of the IR are research output, whereas a DL can hold anything. Rob
Re: [CODE4LIB] Open Source Institutional Repository Software?
Eric Lease Morgan wrote: On Aug 21, 2008, at 4:34 PM, Jonathan Rochkind wrote: If you can figure out what the difference between an 'institutional repository' and a 'digital library' is, let me know. I think an institutional repository is a type of digital library. To ma an institutional repository is a *component* of the digital library. A digital library might consist of an repository where digital objects are persisted, preserved, and managed but it also needs a presentation layer, tools for collection building, metadata creation, discovery tools, and scanning/transformation services of objects which are not born digital, etc. Typically I've seen digital libraries start by identifying a collection based on a genre, material collected and stored in a "digital library in a box" (like DSpace or Greenstone) and then made available through the UI provided by the all-in-one solutions. I am working on a model which collects and persists all of the available digital objects and persists them to a repository, then collections can be built from any of the material in the repository as well as material from other institutional repositories.
Re: [CODE4LIB] Open Source Institutional Repository Software?
2008/8/22 David Kane <[EMAIL PROTECTED]>: > I use EPrints, which is great. > > Do look out for Microsoft's offering though, which is in the pipeline. It > will be free. Of course It will need to run on a Windows server and will be > optimised for SQL Server. Er.. it will *only* run on the most recent SQLServer - their repo is a shim on top of SQLServers native XPath handling system, as far as I could make out. From talking to them, they seem to have convinced a SQLServer that it is really an RDF triplestore, and have added a few gui things on top. My actual advice to the first poster however, is that if you have no resources (money and/or time) then don't bother with an IR - it will require time, effort and probably money. If you feel up to putting in that time and effort, then fantastic, but don't be mislead that it won't suck up your time. Ben O'Steen Software Engineer, Oxford University > > David. > > > -- > David Kane > Systems Librarian > Waterford Institute of Technology > http://library.wit.ie/ > T: ++353.51302838 > M: ++353.876693212 >
