Hi all About Prism - I think this would be definitely worth exploring more, but I only had a brief look at it.
Graham and Robin(Edinburgh) mentioned it on the list last year and I thought YESSSS.... this would work. http://www.prismstandard.org/faq/ "Hey there all you other Rep Managers" have a look and see if an out of the box DSpace with this extra/additional/instead of schema would work for you. Cheers Leonie -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Friday, 21 January 2011 1:02 p.m. To: [email protected] Subject: Dspace-general Digest, Vol 13, Issue 13 Send Dspace-general mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/dspace-general or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Dspace-general digest..." Today's Topics: 1. Re: DSpace 1.7 discussion: Introductions (Andrea Schweer) 2. Re: DSpace 1.7 discussion: Upgrade Challenges (Graham Triggs) 3. Re: 1.7 discussion Introductions (Graham Triggs) 4. Re: DSpace 1.7 discussion: more than one DSpace instance (Platt, Alice) 5. Re: DSpace 1.7 discussion: more than one DSpace instance (Andrea Schweer) ---------------------------------------------------------------------- Message: 1 Date: Fri, 21 Jan 2011 09:58:03 +1300 From: Andrea Schweer <[email protected]> Subject: Re: [Dspace-general] DSpace 1.7 discussion: Introductions To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 Hi all, I'm Andrea Schweer, my official title is Institutional Research Repository Technical Specialist. I'm a software developer based at the University of Waikato in New Zealand; I'm responsible for development and maintenance of four different institutional repositories for the Library Consortium of New Zealand. I haven't been in this role for more than a few months, which means I inherited all four repositories. I think the "older" ones went live around 2008 and the "newest" one early in 2010. Currently, three are on 1.6.1 and the fourth is on 1.6.2; all are on RHEL 5.5. There are no immediate plans to go to 1.7, though an upgrade to 1.7.1 (if it's been released by then) is tentatively scheduled for after Easter. Two of the repositories use XMLUI, the other two use JSPUI. We have a whole bunch of customisations of code and user interface, mostly around embargoes but also for usage statistics. cheers, Andrea -- Andrea Schweer IRR Technical Specialist, ITS Information Systems The University of Waikato, Hamilton, New Zealand ------------------------------ Message: 2 Date: Thu, 20 Jan 2011 21:01:56 +0000 From: Graham Triggs <[email protected]> Subject: Re: [Dspace-general] DSpace 1.7 discussion: Upgrade Challenges To: Brian Freels-Stendel <[email protected]> Cc: "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1" On 20 January 2011 16:53, Brian Freels-Stendel <[email protected]> wrote: > Our philosophy is not to be bleeding edge, so we generally don't jump > on a .0 release, but we do want to remain semi-current, so a .1 is ok. > Hi, This is a common perception (not just with DSpace, but most software), but it's worth addressing in the context of how DSpace releases are managed. The primary focus and planning of DSpace releases is on the .0 release. When cutting a major version, we don't plan to do a .1, .2, etc. release. These only happen if there are significant problems found in the .0 release (and they may not even be problems that originated in the .0 release - quite often they have actually existed for a number of releases, but have only just been uncovered), which justify a .1 release. For 1.7.0, we changed our release planning from "when it's ready", to setting a date for the release well in advance and working towards getting features into it. Going forward, we would hope to regulate that to become a predictable cycle for the .0 releases. We're also including more testing in the development process, and are looking to build community involvement in the testing phases prior to the actual release (such as having longer periods for testing, more test releases). Between the quality analysis and testing in the development process, and the tighter scheduling of major releases, it's quite possible that we will have major releases in the future that have no .1 release, due to no problems being found within a reasonable amount of time of the major release. It's understandable to want to wait for a period of time before upgrading to see if any problems are found, but anyone waiting solely for a bug fix release may end up waiting for something that never happens (for all the right reasons though!). We also have a devil of a time with prerequisite software (we almost > were not able to upgrade to 1.6 due to Ant, and we will have to wait for > 1.7 because RH isn't offering a late enough version of maven.) We > customize fairly heavily, and that is always a challenge, but almost > always possible because of great community support. > Prerequisites are tricky, and we try as best as possible to support versions of the major components (ie. Postgres, Java) that are supported and/or provided on the recent major platforms (Mac, Windows, Red Hat, Suse, Debian, Ubuntu). With distributions like Red Hat and Debian, they have a 'steady' and cautious approach to new releases, so there will be times when that may be impossible. In the case of prerequisites like Maven and Ant, current versions can be installed on any platform simply by unarchiving a file downloaded from those projects homepage. And [particularly where it is just a development / deployment tool,] it's quite easy to install and use a version that is required by DSpace, and without overwriting the versions provided by the platform. We would still rather be able to support the versions provided by Red Hat, etc., but where we don't it's because we have good reason to require features that are in the newer releases. Regards, G -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 3 Date: Thu, 20 Jan 2011 21:13:57 +0000 From: Graham Triggs <[email protected]> Subject: Re: [Dspace-general] 1.7 discussion Introductions To: Leonie Hayes <[email protected]> Cc: "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1" On 20 January 2011 20:26, Leonie Hayes <[email protected]> wrote: > We don't do much customisation and try to upgrade as quickly as possible, I > spent a lot of time trying to make sure that our metadata was comprehensive > but have always been disappointed with the fact there is no metadata for > separate elements of a citation like volume, issue and s/e pages, also > export to endnote/BibTeX etc and that is something I hope to contribute to > the community for 1.8. > Hi Leonie, I share your pain with this problem - we also have an export mechanism for EndNote, based on parsing the citation field. It works, but without the consistency in the metadata it's impossible to contribute back to the community [and expect it to be reliable]. More recently, we have started implementing a PRISM metadata schema ( http://www.prismstandard.org/) for the discrete metadata fields. PRISM specifies discrete fields for this metadata, plus much more information that publishers have/are interested in, which would naturally support reliable export mechanisms. As this standard has already been adopted by most of the major publishers, they are already in a position to provide that metadata for automated deposit / ingest (where they are prepared to support such services), if the repository community was to agree to also support the standard. I look forward to having further discussions about this. Regards, G -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 4 Date: Thu, 20 Jan 2011 18:41:40 -0500 From: "Platt, Alice" <[email protected]> Subject: Re: [Dspace-general] DSpace 1.7 discussion: more than one DSpace instance To: "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" I realize you are new, so you might not know the nuances to the answer, but I am interested in why the library has four separate repositories. For the group -- does anyone else have more than one DSpace instance at their institution, and why? Alice Platt Digital Initiatives Librarian Shapiro Library Southern New Hampshire University ________________________________________ From: Andrea Schweer [[email protected]] Sent: Thursday, January 20, 2011 3:58 PM To: [email protected] Subject: Re: [Dspace-general] DSpace 1.7 discussion: Introductions Hi all, I'm Andrea Schweer, my official title is Institutional Research Repository Technical Specialist. I'm a software developer based at the University of Waikato in New Zealand; I'm responsible for development and maintenance of four different institutional repositories for the Library Consortium of New Zealand. I haven't been in this role for more than a few months, which means I inherited all four repositories. I think the "older" ones went live around 2008 and the "newest" one early in 2010. Currently, three are on 1.6.1 and the fourth is on 1.6.2; all are on RHEL 5.5. There are no immediate plans to go to 1.7, though an upgrade to 1.7.1 (if it's been released by then) is tentatively scheduled for after Easter. Two of the repositories use XMLUI, the other two use JSPUI. We have a whole bunch of customisations of code and user interface, mostly around embargoes but also for usage statistics. cheers, Andrea -- Andrea Schweer IRR Technical Specialist, ITS Information Systems The University of Waikato, Hamilton, New Zealand ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general Please consider the environment before printing this e-mail. ------------------------------ Message: 5 Date: Fri, 21 Jan 2011 13:01:48 +1300 From: Andrea Schweer <[email protected]> Subject: Re: [Dspace-general] DSpace 1.7 discussion: more than one DSpace instance To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 Hi Alice, On 21/01/11 12:41, Platt, Alice wrote: > > Andrea Schweer wrote: >> I'm responsible for development and maintenance of four different >> institutional repositories for the Library Consortium of New >> Zealand. > > I realize you are new, so you might not know the nuances to the > answer, but I am interested in why the library has four separate > repositories. I see I didn't explain that very well -- each of the four repositories that I'm looking after belongs to a different NZ university or polytechnic. The Library Consortium of New Zealand [1] is a consortium of several university libraries in New Zealand; the institutions whose repositories I'm looking after decided to band together and share some work in setting up and running their repositories. > For the group -- does anyone else have more than one DSpace instance > at their institution, and why? One of the four sites does have several repositories, for historic reasons. Two organisational sub-units had already set up local repositories (both on EPrints) when the university-wide DSpace one went live. Currently all three are running side by side but plans are underway to merge at least one of the EPrints repositories into the university-wide one. cheers, Andrea [1] http://www.lconz.ac.nz/ -- Andrea Schweer IRR Technical Specialist, ITS Information Systems The University of Waikato, Hamilton, New Zealand ------------------------------ ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ------------------------------ _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general End of Dspace-general Digest, Vol 13, Issue 13 ********************************************** ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
