From ruigrokvanderwerven at ubib.eur.nl Wed Jan 4 03:46:07 2006 From: ruigrokvanderwerven at ubib.eur.nl (Jeroen Ruigrok van der Werven) Date: Wed, 04 Jan 2006 09:46:07 +0100 Subject: [Dspace-general] DSpace on BSD Message-ID: <43BB8B4F.3060801@ubib.eur.nl> Hi, a quick question, how many of you are running dspace and accompanying software on BSD, preferably FreeBSD? -- Jeroen Ruigrok van der Werven IT Dept Erasmus University Library From Peter.Kargbo at wlv.ac.uk Wed Jan 4 08:19:17 2006 From: Peter.Kargbo at wlv.ac.uk (Kargbo, Peter) Date: Wed, 4 Jan 2006 13:19:17 -0000 Subject: [Dspace-general] Windows Operating System for Institutional Repository... Message-ID: Hi, Does anyone know of an institution(s) or had experience of using Windows as a platform for their institutional respository? We are thinking of creating a repository for learning objects, corporate records, and research output and there is a strong preference for using a Windows based rather than a UNIX based platform for the proposed IR. We're particularly interested in the pros and cons of using Windows for this type of project. Also appreciate any other OS you can recommend. Thanks for your help Peter Peter Kargbo Resources Librarian (Inspire Project) Harrison Learning Centre University of Wolverhampton Wolverhampton WV1 0NH Tel:01902-322918 Email: peter.kargbo at wlv.ac.uk -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.mit.edu/pipermail/dspace-general/attachments/20060104/1908825b/attachment.htm From fgjohnson at upei.ca Wed Jan 4 15:34:46 2006 From: fgjohnson at upei.ca (Grant Johnson) Date: Wed, 04 Jan 2006 16:34:46 -0400 Subject: [Dspace-general] Group Names Message-ID: <43BC3166.1060307@upei.ca> Hi All: How do I figure out the Group Names and the collections they are linked to. For example: In Group Administration COLLECTION_6_ADMIN (click edit) returns the e-people under "Edit Group : COLLECTION_6_ADMIN (14)" heading I can select a Community (click edit) returns "Edit Community 123456789/6 " Are these collection 6? What's 14? Is there an easy way to identify collection 6 - We are expecting MANY collections/submissions, that all seem to get assigned a different number after the handle. Or is direct db query the only way? Thanks -- F. Grant Johnson 566-0630 / fgjohnson at upei.ca Systems/Web Coordinator RM 285 - Robertson Library University of Prince Edward Island *************** Attitude is IT! From smuir1 at emich.edu Wed Jan 4 16:40:31 2006 From: smuir1 at emich.edu (Scott P. Muir) Date: Wed, 04 Jan 2006 16:40:31 -0500 Subject: [Dspace-general] DSpace Archiving Message-ID: <6.2.3.4.0.20060104162815.01c24f90@mail.emich.edu> I am envisioning the following situation In May Dr. Smith enters a document into the DSpace repository. Over the next few days through a series of edits, Dr. Smith accidentally deletes the document out of DSpace, but isn't aware of the mishap. Dr. Smith then leaves for the summer. In September, Dr. Smith comes back, tries to look at the document and discovers it is not there. Dr. Smith then calls the library demanding to know what happened, and informing the library that the missing document was the only copy. Another scenario could have a document become corrupted through some bad editing, e.g. poor use of find/replace. We are exploring this on two tracks: 1- not letting anyone, but a very few defined number of people, delete or replace documents once they are in the repository or 2) developing a comprehensive long term strategy for retention of backups of the documents, etc, in DSpace so that we could restore a document. Has anyone else discussed this and come up with what you feel is an appropriate solution? Thanks for the input. Scott P Muir Associate University Librarian Bruce T. Halle Library, Room 200F Eastern Michigan University 955 West Circle Drive Ypsilanti, MI 48197-2207 734.487.0020 x2222 (voice) 734.484.1151 (fax) http://www.emich.edu/halle/ mailto:scott.muir at emich.edu From gwiersma at MIT.EDU Wed Jan 4 17:45:00 2006 From: gwiersma at MIT.EDU (Grace Wiersma) Date: Wed, 4 Jan 2006 17:45:00 -0500 Subject: [Dspace-general] DSpace Archiving In-Reply-To: <6.2.3.4.0.20060104162815.01c24f90@mail.emich.edu> Message-ID: <012e01c61180$7ee01aa0$77013312@mitlibraries.ms.mit.edu> Scott, Some discussion relevant to your concern was posted to this list in January 2005 at the thread: >> Ability to replace existing items I hope you'll continue the discussion! Grace Wiersma, MARC Database Quality Technician Cataloging & Metadata Services, MIT Libraries gwiersma at mit.edu (617) 253-0643 -----Original Message----- From: dspace-general-bounces at MIT.EDU [mailto:dspace-general-bounces at MIT.EDU] On Behalf Of Scott P. Muir Sent: Wednesday, January 04, 2006 4:41 PM To: dspace-general at mit.edu Subject: [Dspace-general] DSpace Archiving I am envisioning the following situation In May Dr. Smith enters a document into the DSpace repository. Over the next few days through a series of edits, Dr. Smith accidentally deletes the document out of DSpace, but isn't aware of the mishap. Dr. Smith then leaves for the summer. In September, Dr. Smith comes back, tries to look at the document and discovers it is not there. Dr. Smith then calls the library demanding to know what happened, and informing the library that the missing document was the only copy. Another scenario could have a document become corrupted through some bad editing, e.g. poor use of find/replace. We are exploring this on two tracks: 1- not letting anyone, but a very few defined number of people, delete or replace documents once they are in the repository or 2) developing a comprehensive long term strategy for retention of backups of the documents, etc, in DSpace so that we could restore a document. Has anyone else discussed this and come up with what you feel is an appropriate solution? Thanks for the input. Scott P Muir Associate University Librarian Bruce T. Halle Library, Room 200F Eastern Michigan University 955 West Circle Drive Ypsilanti, MI 48197-2207 734.487.0020 x2222 (voice) 734.484.1151 (fax) http://www.emich.edu/halle/ mailto:scott.muir at emich.edu _______________________________________________ Dspace-general mailing list Dspace-general at mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general From peterwalgemoed at carelliance.com Wed Jan 4 18:31:52 2006 From: peterwalgemoed at carelliance.com (Peter Walgemoed) Date: Thu, 5 Jan 2006 00:31:52 +0100 Subject: [Dspace-general] DSpace Archiving References: <6.2.3.4.0.20060104162815.01c24f90@mail.emich.edu> Message-ID: <034301c61187$0b11f060$0201a8c0@CElaptop> Scott, I recognize your concern and think a lot of it has to do with your institution's policy and who is responsible for providing which service. If the policy is that DSpace is used as a repository for archiving/long term preservation, the policy will likely be that everything that is entered into DSpace can not be deleted/modified. E.g. it is archived and can only be deleted by authorized persons, because of retention times and/or specific (user) requests. In case of Dr. Smith, if he is still working on his document (e.g.. part of the creation process and not yet ready for archiving) he can not blame DSpace/the library when something goes wrong in this part of the process. Of course there can and should be another safety-net provided by the IT department to keep content/files that are under construction available for their users in case a local PC fails or a user makes a mistake. This should be taking care of by the (normal) IT services provided to university users. It will be part of their (server) back-up services, when Dr. Smith works on a IT supported network drive. Hope this helps a bit in your discussion. In any case try to include your local IT department in these discussions and make them feel responsible as well. Regards, Peter ----- Original Message ----- From: Scott P. Muir To: dspace-general at mit.edu Sent: Wednesday, January 04, 2006 10:40 PM Subject: [Dspace-general] DSpace Archiving I am envisioning the following situation In May Dr. Smith enters a document into the DSpace repository. Over the next few days through a series of edits, Dr. Smith accidentally deletes the document out of DSpace, but isn't aware of the mishap. Dr. Smith then leaves for the summer. In September, Dr. Smith comes back, tries to look at the document and discovers it is not there. Dr. Smith then calls the library demanding to know what happened, and informing the library that the missing document was the only copy. Another scenario could have a document become corrupted through some bad editing, e.g. poor use of find/replace. We are exploring this on two tracks: 1- not letting anyone, but a very few defined number of people, delete or replace documents once they are in the repository or 2) developing a comprehensive long term strategy for retention of backups of the documents, etc, in DSpace so that we could restore a document. Has anyone else discussed this and come up with what you feel is an appropriate solution? Thanks for the input. Scott P Muir Associate University Librarian Bruce T. Halle Library, Room 200F Eastern Michigan University 955 West Circle Drive Ypsilanti, MI 48197-2207 734.487.0020 x2222 (voice) 734.484.1151 (fax) http://www.emich.edu/halle/ mailto:scott.muir at emich.edu _______________________________________________ Dspace-general mailing list Dspace-general at mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.mit.edu/pipermail/dspace-general/attachments/20060105/42683873/attachment.htm From omikorn at yahoo.com Thu Jan 5 21:18:07 2006 From: omikorn at yahoo.com (Iulian Surugiu) Date: Fri, 6 Jan 2006 02:18:07 +0000 (GMT) Subject: [Dspace-general] Dspace 1.3.2 and Fedora core 4 Message-ID: <20060106021807.39082.qmail@web36211.mail.mud.yahoo.com> Hi all i followed the steps from the documentation but i can`t get rid of this error. Also i can find preety poor information on google. My operating system is FC4: ant-1.6.2-3jpp_8fc tomcat5-5.0.30-5jpp_6fc java-1.4.2-gcj-compat-1.4.2.0-40jpp_31rh.FC4.2 gcc-java-4.0.2-8.fc4 tomcat5-servlet-2.4-api-javadoc-5.0.30-5jpp_6fc java-1.4.2-gcj-compat-devel-1.4.2.0-40jpp_31rh.FC4.2 What am i missing? [dspace at qualcon-sing dspace-1.3.2-source]$ ant fresh_install Buildfile: build.xml compile: [javac] Compiling 1 source file to /tmp/dspace-1.3.2-source/build/classes [javac] ---------- [javac] 1. ERROR in /tmp/dspace-1.3.2-source/src/org/dspace/app/mediafilter/HTMLFilter.java [javac] (at line 46) [javac] import javax.swing.text.html.HTMLEditorKit; [javac] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [javac] The import javax.swing.text.html.HTMLEditorKit cannot be resolved [javac] ---------- [javac] 2. ERROR in /tmp/dspace-1.3.2-source/src/org/dspace/app/mediafilter/HTMLFilter.java [javac] (at line 98) [javac] HTMLEditorKit kit = new HTMLEditorKit(); [javac] ^^^^^^^^^^^^^ [javac] HTMLEditorKit cannot be resolved to a type [javac] ---------- [javac] 3. ERROR in /tmp/dspace-1.3.2-source/src/org/dspace/app/mediafilter/HTMLFilter.java [javac] (at line 98) [javac] HTMLEditorKit kit = new HTMLEditorKit(); [javac] ^^^^^^^^^^^^^ [javac] HTMLEditorKit cannot be resolved to a type [javac] ---------- [javac] ---------- [javac] 4. WARNING in /tmp/dspace-1.3.2-source/src/org/dspace/content/Item.java [javac] (at line 1613) [javac] Bitstream mybitstream = bs[j]; [javac] ^^^^^^^^^^^ [javac] The local variable mybitstream is never read [javac] ---------- [javac] ---------- [javac] 5. WARNING in /tmp/dspace-1.3.2-source/src/org/dspace/content/Item.java [javac] (at line 1650) [javac] Bitstream mybitstream = bs[j]; [javac] ^^^^^^^^^^^ [javac] The local variable mybitstream is never read [javac] ---------- [javac] ---------- [javac] 6. WARNING in /tmp/dspace-1.3.2-source/src/org/dspace/authorize/AuthorizeException.java [javac] (at line 51) [javac] public class AuthorizeException extends Exception [javac] ^^^^^^^^^^^^^^^^^^ [javac] The serializable class AuthorizeException does not declare a static final serialVersionUID field of type long [javac] ---------- [javac] ---------- [javac] 7. WARNING in /tmp/dspace-1.3.2-source/src/org/dspace/storage/rdbms/DatabaseManager.java [javac] (at line 851) [javac] boolean succeeded = statement.execute(SQL); [javac] ^^^^^^^^^ [javac] The local variable succeeded is never read [javac] ---------- [javac] ---------- [javac] 8. WARNING in /tmp/dspace-1.3.2-source/src/org/dspace/storage/rdbms/DatabaseManager.java [javac] (at line 1351) [javac] PoolableConnectionFactory poolableConnectionFactory = new PoolableConnectionFactory( [javac] ^^^^^^^^^^^^^^^^^^^^^^^^^ [javac] The local variable poolableConnectionFactory is never read [javac] ---------- [javac] ---------- [javac] 9. WARNING in /tmp/dspace-1.3.2-source/src/org/dspace/browse/Browse.java [javac] (at line 769) [javac] Object obj = scope.getScope(); [javac] ^^^ [javac] The local variable obj is never read [javac] ---------- [javac] ---------- [javac] 10. WARNING in /tmp/dspace-1.3.2-source/src/org/dspace/browse/Browse.java [javac] (at line 1492) [javac] private static int firstWhitespace(char[] title) [javac] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [javac] The method firstWhitespace(char[]) from the type NormalizedTitle is never used locally [javac] ---------- [javac] ---------- [javac] 11. WARNING in /tmp/dspace-1.3.2-source/src/org/dspace/history/HistoryManager.java [javac] (at line 302) [javac] List dbobjs = new LinkedList(); [javac] ^^^^^^ [javac] The local variable dbobjs is never read [javac] ---------- [javac] ---------- [javac] 12. WARNING in /tmp/dspace-1.3.2-source/src/org/dspace/eperson/EPersonDeletionException.java [javac] (at line 50) [javac] public class EPersonDeletionException extends Exception [javac] ^^^^^^^^^^^^^^^^^^^^^^^^ [javac] The serializable class EPersonDeletionException does not declare a static final serialVersionUID field of type long [javac] ---------- [javac] ---------- [javac] 13. WARNING in /tmp/dspace-1.3.2-source/src/org/dspace/workflow/WorkflowManager.java [javac] (at line 433) [javac] WorkspaceItem wsi = returnToWorkspace(c, wi); [javac] ^^^ [javac] The local variable wsi is never read [javac] ---------- [javac] ---------- [javac] 14. WARNING in /tmp/dspace-1.3.2-source/src/org/dspace/workflow/WorkflowManager.java [javac] (at line 999) [javac] Bitstream[] bitstreams = myitem.getNonInternalBitstreams(); [javac] ^^^^^^^^^^ [javac] The local variable bitstreams is never read [javac] ---------- [javac] 14 problems (3 errors, 11 warnings) BUILD FAILED /tmp/dspace-1.3.2-source/build.xml:111: Compile failed; see the compiler error output for details. Total time: 3 seconds Best regards, Surugiu Iulian NOC supervisor/lead administrator Security Analyst, Developer, Programmer at Hyperactiv Networks, www.hyperactiv.ro omikorn at yahoo.com +40746472935 --------------------------------- To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.mit.edu/pipermail/dspace-general/attachments/20060106/1de2cd7a/attachment.htm From clive at ce.bromley.ac.uk Fri Jan 6 14:47:06 2006 From: clive at ce.bromley.ac.uk (Clive Gould) Date: Fri, 6 Jan 2006 19:47:06 -0000 (GMT) Subject: [Dspace-general] Dspace 1.3.2 and Fedora core 4 (Iulian Surugiu) In-Reply-To: References: Message-ID: <1112.84.65.38.20.1136576826.squirrel@ce.bromley.ac.uk> Iulian Have you read my DSpace install blog for FC3/CentOS4? http://www.linuxtraining.org.uk/blogger.html My first reaction is that you may have some incompatibilities caused by applications that came pre-installed with FC4. Also it's better to post these requests to the dspace tech mailing list. Good Luck (I've been there, hence the blog!) Clive From alally at u.washington.edu Fri Jan 6 15:14:50 2006 From: alally at u.washington.edu (Ann Lally) Date: Fri, 06 Jan 2006 12:14:50 -0800 Subject: [Dspace-general] Community-level authorization Message-ID: <43BECFBA.70309@u.washington.edu> I have a puzzling problem I hope someone can help with... Our University Archives has a Community in DSpace; the Archivist is able to set up sub-communities; but once he reaches the first level of sub-communities, he is unable to establish further sub-communities or collections. Example: Community: University Archives Sub-Community: Institutional Records (he can go no further than this). As far as I can tell, I (as a system administrator) have given him all the permissions possible for this community (Read, Write, Add, Remove). Has anyone else had this experience? Thanks for any insight! Ann Lally Head, Digital Initiatives University of Washington Libraries From clive at ce.bromley.ac.uk Sun Jan 8 06:54:31 2006 From: clive at ce.bromley.ac.uk (Clive Gould) Date: Sun, 8 Jan 2006 11:54:31 -0000 (GMT) Subject: [Dspace-general] Thumbnails and duplicate image filenames Message-ID: <1528.81.77.75.177.1136721271.squirrel@ce.bromley.ac.uk> Hi I've been uploading some images recently into DSpace and have encountered a problem with the thumbnail images, where two images are different but have an identical filename. This is particularly a problem with images uploaded from a digital camera on a number of separate occasions. In such a case the items are correctly uploaded and independently displayed in DSpace but the thumbnail for each image has the same name and hence both images have an identical thumbnail displayed. An example is shown here: http://hdl.handle.net/2045/39 An exerpt from running the filter-media script illustrates the problem: Format: 'image/png' Filtering Class: 'org.dspace.app.mediafilter.JPEGFilter' FILTERED: bitstream 214 and created 'Picture1.jpg.jpg' SKIPPED: bitstream 213 because 'Picture1.jpg.jpg' already exists This implies that if a number of images from a digital camera are uploaded and if any have identical filenames then the thumbnails will not display correctly. I have a memeber of our media team wishing to upload some images - do I need to make sure he doesn't use any image filenames which are already in use? As the image collection grows this could easily become an administrative burden. Has anyone found a way round this problem? Thanks very much From sdl at aber.ac.uk Mon Jan 9 05:49:41 2006 From: sdl at aber.ac.uk (Stuart David Lewis [sdl]) Date: Mon, 9 Jan 2006 10:49:41 -0000 Subject: [Dspace-general] Community-level authorization Message-ID: <2E32E4049258DA42B884AB8EA753F64C1B4665@issvexch1.staff.aber.ac.uk> Dear Ann, I think the problem is that by default, in DSpace permissions do not trickle down as new items are created. The following patch will solve this: - http://sourceforge.net/tracker/index.php?func=detail&aid=1237589&group_i d=19984&atid=319984 Cheers, Stuart _________________________________________________________________ Datblygydd Cymwysiadau'r We Web Applications Developer Gwasanaethau Gwybodaeth Information Services Prifysgol Cymru Aberystwyth University of Wales Aberystwyth E-bost / E-mail: Stuart.Lewis at aber.ac.uk Ffon / Tel: (01970) 622860 _________________________________________________________________ -----Original Message----- From: dspace-general-bounces at mit.edu [mailto:dspace-general-bounces at mit.edu] On Behalf Of Ann Lally Sent: 06 January 2006 20:15 To: dspace-general at mit.edu Subject: [Dspace-general] Community-level authorization I have a puzzling problem I hope someone can help with... Our University Archives has a Community in DSpace; the Archivist is able to set up sub-communities; but once he reaches the first level of sub-communities, he is unable to establish further sub-communities or collections. Example: Community: University Archives Sub-Community: Institutional Records (he can go no further than this). As far as I can tell, I (as a system administrator) have given him all the permissions possible for this community (Read, Write, Add, Remove). Has anyone else had this experience? Thanks for any insight! Ann Lally Head, Digital Initiatives University of Washington Libraries _______________________________________________ Dspace-general mailing list Dspace-general at mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general From hgxu at hotmail.com Mon Jan 9 14:05:14 2006 From: hgxu at hotmail.com (hong xu) Date: Tue, 10 Jan 2006 03:05:14 +0800 Subject: [Dspace-general] Dspace-general Digest, Vol 30, Issue 6 Message-ID: About the Dspace authorization, I have attached a file to explain the centralization-authorization. >From: dspace-general-request at mit.edu >Reply-To: dspace-general at mit.edu >To: dspace-general at mit.edu >Subject: Dspace-general Digest, Vol 30, Issue 6 >Date: Mon, 09 Jan 2006 12:00:43 -0500 > >Send Dspace-general mailing list submissions to > dspace-general at mit.edu > >To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.mit.edu/mailman/listinfo/dspace-general >or, via email, send a message with subject or body 'help' to > dspace-general-request at mit.edu > >You can reach the person managing the list at > dspace-general-owner at mit.edu > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Dspace-general digest..." > > >Today's Topics: > > 1. Re: Community-level authorization (Stuart David Lewis [sdl]) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Mon, 9 Jan 2006 10:49:41 -0000 >From: "Stuart David Lewis [sdl]" >Subject: Re: [Dspace-general] Community-level authorization >To: "Ann Lally" >Cc: dspace-general at mit.edu >Message-ID: > <2E32E4049258DA42B884AB8EA753F64C1B4665 at issvexch1.staff.aber.ac.uk> >Content-Type: text/plain; charset="us-ascii" > >Dear Ann, > >I think the problem is that by default, in DSpace permissions do not >trickle down as new items are created. The following patch will solve >this: > > - >http://sourceforge.net/tracker/index.php?func=detail&aid=1237589&group_i >d=19984&atid=319984 > >Cheers, > > >Stuart >_________________________________________________________________ > >Datblygydd Cymwysiadau'r We Web Applications Developer >Gwasanaethau Gwybodaeth Information Services >Prifysgol Cymru Aberystwyth University of Wales Aberystwyth > > E-bost / E-mail: Stuart.Lewis at aber.ac.uk > Ffon / Tel: (01970) 622860 >_________________________________________________________________ > > >-----Original Message----- >From: dspace-general-bounces at mit.edu >[mailto:dspace-general-bounces at mit.edu] On Behalf Of Ann Lally >Sent: 06 January 2006 20:15 >To: dspace-general at mit.edu >Subject: [Dspace-general] Community-level authorization > >I have a puzzling problem I hope someone can help with... > >Our University Archives has a Community in DSpace; the Archivist is able > >to set up sub-communities; but once he reaches the first level of >sub-communities, he is unable to establish further sub-communities or >collections. > >Example: >Community: University Archives > Sub-Community: Institutional Records (he can go no further than >this). > >As far as I can tell, I (as a system administrator) have given him all >the permissions possible for this community (Read, Write, Add, Remove). > Has anyone else had this experience? > >Thanks for any insight! > >Ann Lally >Head, Digital Initiatives >University of Washington Libraries >_______________________________________________ >Dspace-general mailing list >Dspace-general at mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general > > > >------------------------------ > >_______________________________________________ >Dspace-general mailing list >Dspace-general at mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general > > >End of Dspace-general Digest, Vol 30, Issue 6 >********************************************* -------------- next part -------------- A non-text attachment was scrubbed... Name: Starchive Authorization.ppt Type: application/vnd.ms-powerpoint Size: 17408 bytes Desc: not available Url : http://mailman.mit.edu/pipermail/dspace-general/attachments/20060110/5b02ef8e/attachment.ppt From fgjohnson at upei.ca Tue Jan 10 14:50:43 2006 From: fgjohnson at upei.ca (Grant Johnson) Date: Tue, 10 Jan 2006 15:50:43 -0400 Subject: [Dspace-general] Changing Access Message-ID: <43C41013.8060908@upei.ca> I have setup a Community with Collections. It's not open to global access. I would now like to make the submissions in one of these collections open for anonymous access. Can this be done? I have tried without success. I feel dazed and confused!!! Perhap's I'm having a low bio-rhythm week. Thanks in advance. F. Grant Johnson 566-0630 / fgjohnson at upei.ca Systems/Web Coordinator RM 285 - Robertson Library University of Prince Edward Island *************** Attitude is IT! From richard.jones at ub.uib.no Thu Jan 12 11:20:07 2006 From: richard.jones at ub.uib.no (Richard Jones) Date: Thu, 12 Jan 2006 17:20:07 +0100 Subject: [Dspace-general] The Institutional Repository Message-ID: <1137082807.4574.123.camel@ubbtilv067115> Hi Folks, Apologies for cross posting. I just wanted to proudly announce the publication of a book that I have co-authored with Theo Andrew and John MacColl of Edinburgh University Library entitled "The Institutional Repository". The publisher's site can be found here: http://www.chandospublishing.com/catalogue/record_detail.php?recordID=76 And we have archived chapters 1 and 7 (Introduction and Case Study) in the Edinburgh Research Archive: http://www.era.lib.ed.ac.uk/handle/1842/858 http://www.era.lib.ed.ac.uk/handle/1842/859 I would like, also, to thank a number of people from the DSpace community who have helped us out on this: MacKenzie Smith: MacKenzie contributed the excellent package profile on DSpace which appears in the Appendices to the book alongside profiles from other major IR systems such as EPrints.org. Jim Downing: Jim very kindly acted as a reviewer for my chapter covering some technical issues with repositories, and his comments were totally invaluable. William Nixon and Morag Greig: William and Morag, from Glasgow University Library, acted as reviewers for my chapter covering workflow and administration issues for IRs. Again, without their comments this chapter would not have taken shape. I hope, if you do take a look at it, that you enjoy it and find it useful. Cheers, -- Richard ------- Richard Jones | Overingeni?r | Senior Engineer Universitetsbiblioteket i Bergen | University of Bergen Library e: richard.jones at ub.uib.no t: +47 55 58 25 37 BORA: http://bora.uib.no/ From fgjohnson at upei.ca Fri Jan 13 16:11:25 2006 From: fgjohnson at upei.ca (Grant Johnson) Date: Fri, 13 Jan 2006 17:11:25 -0400 Subject: [Dspace-general] DSpace assetstore Message-ID: <43C8177D.6060401@upei.ca> Hi All, I have withdrawn(and expunged) ALL of my test communities and Collections. Organizing the archivists to "build" their space. However - "old" documents, images etc...still exist in the ../dspace/assetstore. I had some "errors" and perused catalina.out to discover the item ID of a few entries to get rid of them. Question: How do I deal- properly - with this unwanted data? 1. Can I delete these the folders and files? (old ID #.s) and re vaccuum the dbase? 2. Should I delete the database, remove the webapp, rebuild and copy the new wars into Tomcat? Seems excessive! I'm using Postgresql and can access the database through PGAdmin. Thanks in advance. -- F. Grant Johnson 566-0630 / fgjohnson at upei.ca Systems/Web Coordinator RM 285 - Robertson Library University of Prince Edward Island *************** Attitude is IT! From faritos at gmail.com Sat Jan 14 00:04:42 2006 From: faritos at gmail.com (=?ISO-8859-1?Q?Ricardo_Beltr=E1n?=) Date: Fri, 13 Jan 2006 23:04:42 -0600 Subject: [Dspace-general] Soon a new DSpace Installation in Mexico Message-ID: <43C8866A.2020803@gmail.com> Hi everybody, I'm just writing to announce that an Education and Research Institution in Mexico called CIDE (www.cide.edu) will begin in February the creation of its IR with DSpace, I've kept an eye in DSpace for some months and I'm quite impressed with this project, thanks to the people that made this possible and open source. The DSpace at CIDE will start with a collection of polls (polls and data sets) that were made from 1988 to 2000 by the Office of the President of Mexico. Just to start we have around 5,000 items that will be uploaded during the following six months and are without any doubt the most valuable collection of public opinion research in Mexico. Later we'll include more collections as well as magazines, papers, syllabus, etc. Thanks in advance for the help that you will provide me to reach these goals. Best regards. Ricardo Beltran ricardobeltran at ieee.org From richard.jones at ub.uib.no Mon Jan 16 03:59:53 2006 From: richard.jones at ub.uib.no (Richard Jones) Date: Mon, 16 Jan 2006 09:59:53 +0100 Subject: [Dspace-general] DSpace User Group Meeting, Bergen, April 2006: Call for Papers Message-ID: <1137401993.30454.58.camel@ubbtilv067115> DSpace User Group Meeting, Bergen 2006 "Dugnad" among the fjords 19 April (IR workshop), 20-21 April 2006 (DSUG) -------------------------------------------------------------------- Call for Papers =============== The Program Committee of the DSUG 2006, Bergen meeting is pleased to invite you to submit proposals for presentations at this meeting. Authors may submit abstracts for one of the following presentation formats: -Long Presentation -Short Presentation -Poster -Workshop or tutorial The general focus of the meeting is on tools to aid embedding into institutional systems both internal and external, and the use of DSpace in different areas of institutional activity (for example, Records Management). Nonetheless, any topic relevant to DSpace (both technical and administrative) is welcomed. Abstracts should be of approximately 200 words and should be submitted by 15 February 2006 by email to dsug2006 at uib.no. All presentations should be delivered in English. Presentation format ------------------- Long presentations will take place in the main conference hall, and should be approximately 25 minutes in length, followed by 5 minutes for questions and discussion. Short presentations will take place during break-out sessions, and should be approximately 10 minutes in length and will act as catalysts for the discussions which will take place in those sessions. There will be break-out sessions on both technical and administrative issues. Posters will be presented during coffee breaks, and will be available in the conference venue for the duration of the event. There will be an allocated time for presenters to stand by their poster for discussion. Workshops and tutorials will be provided on both technical and administrative aspects of DSpace, and abstracts for these should include the topic and a guide to how the session should be run. If the workshop or tutorial is to be interactive we can offer assistance in organising and running it. Evaluation ---------- Abstracts will be reviewed and evaluated by the Program Committee. Confirmation of acceptance or rejection will be provided by 10 March 2006. Critical Dates -------------- 15 February 2006 - deadline for submission of abstracts 10 March 2006 - confirmation of accepted papers 19 April 2006 - Institutional Repository workshop 20-21 April 2006 - DSpace User Group Meeting Suggested and Example Topics ---------------------------- -Presentations +Multiple instances of DSpace and their uses +DSpace interacting with internal and external research tools +Services employing parts of DSpace, or derived software +Custom developments to meet local needs -Posters +DSpace based services introduced +Research or development projects involving DSpace -Workshops and Tutorials +Writing local customisations for DSpace +Writing patches or addons for DSpace +Developing administrative procedures +Advanced configuration of DSpace (custom forms, LDAP integration, etc.) +Selling DSpace and IRs to management This call for papers is available online at: http://dsug2006.uib.no/index.php?p=call Best wishes, -- Richard ------- Richard Jones | Overingeni?r | Senior Engineer Universitetsbiblioteket i Bergen | University of Bergen Library e: richard.jones at ub.uib.no t: +47 55 58 25 37 BORA: http://bora.uib.no/ From jim.ottaviani at umich.edu Mon Jan 16 14:36:18 2006 From: jim.ottaviani at umich.edu (Jim Ottaviani) Date: Mon, 16 Jan 2006 14:36:18 -0500 (EST) Subject: [Dspace-general] Tombstones for withdrawn items -- how to add, customize? In-Reply-To: References: Message-ID: Hello all, In the DSpace documentation at http://www.dspace.org/technology/system-docs/functional.html I see the following: "[Items] may be 'withdrawn', which means they remain in the archive but are completely hidden from view. In this case, if an end-user attempts to access the withdrawn item, they are presented with a 'tombstone,' that indicates the item has been removed. For whatever reason, an item may also be 'expunged' if necessary, in which case all traces of it are removed from the archive." I have a few questions about this very desirable feature: 1) Items I've withdrawn do not appear to have tombstones. How do we make this happen as a matter of course? 2) Can we present the administrator with a menu of tombstone wordings? I note that MIT has a number of good suggestions for this at http://libraries.mit.edu/dspace-mit/build/policies/community-collection.html and we'd like to do something similar. 3) Can we place tombstones on items that are expunged? I suspect I'm missing something obvious in the documentation, but I just can't seem to find it... Thanks! Jim ____________________________________ Jim Ottaviani +1 734-763-4835 University of Michigan Library Coordinator, Deep Blue pilot project http://deepblue.lib.umich.edu Quis custodiet ipsos custodes --Juvenal, Satires VI, 347 From scott.yeadon at anu.edu.au Mon Jan 16 22:53:02 2006 From: scott.yeadon at anu.edu.au (Scott Yeadon) Date: Tue, 17 Jan 2006 14:53:02 +1100 Subject: [Dspace-general] Open Repositories 2006 - DSpace User Group Meeting Program Message-ID: <43CC6A1E.3020404@anu.edu.au> All, The program for the DSpace User Group Meeting, Sydney 2006 - "Building Communities with DSpace" is now available and can be accessed from http://www.apsr.edu.au/Open_Repositories_2006/program.htm. Please refer any queries about the program to dspace2006 at apsr.edu.au. If you wish to register for the DSpace User Group Meeting and/or other Open Repositories conferences, you can still register by visiting http://apsr.anu.edu.au/Open_Repositories_2006/DSpace06.htm and clicking on the "Registration" link on the left-hand side of the page. Looking forward to seeing you there, The DSpace User Group Programme Committee From emorgan at nd.edu Tue Jan 17 12:21:31 2006 From: emorgan at nd.edu (Eric Lease Morgan) Date: Tue, 17 Jan 2006 12:21:31 -0500 Subject: [Dspace-general] author bios and pictures In-Reply-To: References: Message-ID: Has anybody here incorporated author bios and accompanying pictures into their DSpace implementation, and if so, then how? We are using DSpace, in conjunction with other pieces of software, to create an institutional repository. As I go around campus trying to build interest in the idea many people express the need/desire to accompany lists of their works with a biographical sketch and photograph. Is there any way I can create DSpace (authority) records and include in those records an author's biographical sketch and photograph? -- Eric Lease Morgan Head, Digital Access and Information Architecture Department University Libraries of Notre Dame (574) 631-8604 From robert.tansley at hp.com Tue Jan 17 14:49:14 2006 From: robert.tansley at hp.com (Tansley, Robert) Date: Tue, 17 Jan 2006 14:49:14 -0500 Subject: [Dspace-general] Tombstones for withdrawn items -- how to add, customize? Message-ID: <19ADCC0B9D4CAD4582BB9900BBCE357401AA10C4@tayexc13.americas.cpqcorp.net> Hi Jim, > In the DSpace documentation at > http://www.dspace.org/technology/system-docs/functional.html > I see the following: > > "[Items] may be 'withdrawn', which means they remain in the > archive but > are completely hidden from view. In this case, if an end-user > attempts > to access the withdrawn item, they are presented with a 'tombstone,' > that indicates the item has been removed. For whatever > reason, an item > may also be 'expunged' if necessary, in which case all traces > of it are > removed from the archive." > > I have a few questions about this very desirable feature: > > 1) Items I've withdrawn do not appear to have tombstones. How > do we make > this happen as a matter of course? What happens when you try to access the item page for one of the withdrawn items? (I did notice that if you directly try to access one of the files in a withdrawn item, it just downloads as before, which is a bug -- a report has been filed). > 2) Can we present the administrator with a menu of tombstone > wordings? I > note that MIT has a number of good suggestions for this at > > http://libraries.mit.edu/dspace-mit/build/policies/community-collection. html > and we'd like to do something similar. That's a good idea but would require some development work. From my point of view, the ideal situation would be that you get someone at Michigan to make this change and contribute it back to the open source code base; if this isn't an option, you could try asking on this list and the dspace-tech list to see if anyone has similar needs and/or is interested in doing the necessary development work (which would be pretty small). > 3) Can we place tombstones on items that are expunged? Not with the current functionality. The initial thinking (back in 2001/2002) was that 'expunge' should leave no (external) trace that the object ever existed; a 'tombstone' would be evidence that the object existed at some point. To maintain a tombstone would mean maintaining some information about the object in the repository (even if just the identifier), but right now 'expunge' blows away *everything*. So again, some minor development work would be need to achieve an 'expunge but leave tombstone' feature. Robert TANSLEY / HP Labs / MIT Visiting Researcher http://www.hpl.hp.com/personal/Robert_Tansley/ From robert.tansley at hp.com Tue Jan 17 14:56:20 2006 From: robert.tansley at hp.com (Tansley, Robert) Date: Tue, 17 Jan 2006 14:56:20 -0500 Subject: [Dspace-general] DSpace assetstore Message-ID: <19ADCC0B9D4CAD4582BB9900BBCE357401AA10C5@tayexc13.americas.cpqcorp.net> Hi Grant, For future reference, the 'dspace-tech' list (https://sourceforge.net/mail/?group_id=19984) is probably the best forum for mails of a technical nature like this. > I have withdrawn(and expunged) ALL of my test communities and > Collections. > Organizing the archivists to "build" their space. > However - "old" documents, images etc...still exist in the > ../dspace/assetstore. When a bitstream is 'deleted' in DSpace, it's actually just tagged 'deleted'; the original file isn't immediately removed from the file system. This allows 'rollback' functionality and is intended to help prevent some nasty mistakes being made! In order to actually delete files, the 'cleanup' script (by default, /dspace/bin/cleanup) should be run. This should clear out the 'deleted' files. If desired, this can be configured to run automatically every night, weekend, month etc. as a 'cron' job on Unix/Linux or a Scheduled Task on Windows XP. Robert TANSLEY / HP Labs / MIT Visiting Researcher http://www.hpl.hp.com/personal/Robert_Tansley/ From jim.ottaviani at umich.edu Tue Jan 17 16:48:30 2006 From: jim.ottaviani at umich.edu (Jim Ottaviani) Date: Tue, 17 Jan 2006 16:48:30 -0500 (EST) Subject: [Dspace-general] Tombstones for withdrawn items -- how to add, customize? In-Reply-To: <19ADCC0B9D4CAD4582BB9900BBCE357401AA10C4@tayexc13.americas.cpqcorp.net> References: <19ADCC0B9D4CAD4582BB9900BBCE357401AA10C4@tayexc13.americas.cpqcorp.net> Message-ID: Thanks Robert, > What happens when you try to access the item page for one of the > withdrawn items? (I did notice that if you directly try to access one > of the files in a withdrawn item, it just downloads as before, which is > a bug -- a report has been filed). While it hasn't come up yet, that's an important feature we've been promising our users, so thanks for getting things going on fixing this. Unfortunately, we can't see that behavior right now. When I go to a withdrawn item, I get the following: "Item Withdrawn The item you are trying to access has been withdrawn from Deep Blue. If you have any questions, please contact the administrators." followed by contact information for the administrators. In other words, I don't see the metadata, much less the file. If you'd like to verify you can head over to http://hdl.handle.net/2027.42/13910 Per the documentation, I expected to get the metadata for the item along with a (deadened) link to the bitstream. Do we need to do some additional configuration for this to occur? Also, during the two-step withdrawal process, I didn't see a prompt at either step for adding a note to the field. I had assumed that the person withdrawing the item would be prompted to enter something there. Here again, did I/we miss something in our setup or configuration? I'll skip the other questions, since these are development ideas that we may indeed want to work on, but until we do may not be of general interest to the group as a whole...unless someone is already doing this, in which case it would be great to hear about it! Thanks again, Jim ____________________________________ Jim Ottaviani +1 734-763-4835 University of Michigan Library Coordinator, Deep Blue pilot project http://deepblue.lib.umich.edu Quis custodiet ipsos custodes --Juvenal, Satires VI, 347 From emorgan at nd.edu Wed Jan 18 08:23:58 2006 From: emorgan at nd.edu (Eric Lease Morgan) Date: Wed, 18 Jan 2006 08:23:58 -0500 Subject: [Dspace-general] author bios and pictures In-Reply-To: References: Message-ID: <578BD155-DF04-47C3-A1ED-5A7FE6E35EF5@nd.edu> On Jan 17, 2006, at 6:02 PM, Jennifer Ward wrote: > If I'm not mistaken, Rochester had a way of creating "faculty" > pages that > were populated with works in DSpace and had a photo, bio, etc. I don't > know that their implementation was ever put back into the DSpace > code, but > Susan should be able to clear up any misconceptions I have. > > Jennifer Ward > Head, Web Services > Information Technology Services > University of Washington Libraries > phone: 206.685.3121 Thank you for the reply. Yep, yesterday I chatted with a man named Nathan Sarr of Rochester who described their solution. If I am not mistaken, Nathan wrote a sort of add-on to DSpace. It allows authors to fill in a Web form complete with photograph and links. He saves this content in the DSpace database. He then provides a URL for people to access that returns the photograph and links as a nicely formatted HTML page. See: https://urresearch.rochester.edu/researcher? action=viewResearcherPage&researcherId=5 http://sourceforge.net/tracker/? func=detail&aid=1338741&group_id=19984&atid=319984 Since we are weak on Java skills, I think we are going to take a different tack. Specifically, we will either: 1. Create "authority" files in DSpace and denote them as such with locally developed tags saved in subject fields. 2. Alternatively, we will create a system much like Nathan's but use MyLibrary as the back-end. In either case we will then harvest the content from DSpace using OAI and cache it centrally to our MyLibrary database. We will then syndicate the content from the MyLibrary to many different venues formatted in a variety of ways. In-house software development is a good thing. It empowers people. Again, thanks for the pointer. -- Eric Lease Morgan Head, Digital Access and Information Architecture Department University Libraries of Notre Dame (574) 631-8604 From jhwalker at MIT.EDU Wed Jan 18 11:11:02 2006 From: jhwalker at MIT.EDU (Julie Harford Walker) Date: Wed, 18 Jan 2006 11:11:02 -0500 Subject: [Dspace-general] DSpace Governance Advisory Board Formed Message-ID: <5.2.1.1.2.20060116135231.02c96910@po10.mit.edu> ***************************************************************** DSpace Federation Governance Advisory Board Formed http://wiki.dspace.org/DSpaceGovernance ***************************************************************** It is with great pleasure that MIT Libraries and HP Labs announce the formation of the DSpace Federation Governance Advisory Board. This ad hoc board is being convened to draft a recommendation for governance and funding mechanisms to advance the DSpace community. The Board, nominated from the community and invited by MIT and HP, is comprised of leaders from higher education and industry that are stakeholders in the DSpace community as well as experts on open source software. The members of the board are: Mr. Chris Rusbridge, Chair (Director, Digital Curation Centre, UK) Dr. Adrian Burton (Project Leader, Australian Partnership for Sustainable Repositories) Dr. Matthew Cockerill (Publisher, BioMed Central) Ms. Susan Gibbons (Assistant Dean for Public Services & Collection Development, University of Rochester) Ms. Geneva Henry (Executive Director, Digital Library Initiative, Rice University) Dr. James Hilton (Associate Provost for Academic, Information & Instructional Technology Affairs, University of Michigan) Dr. Clifford Lynch (Executive Director, Coalition for Networked Information) Ms. Carole Moore (University Chief Librarian, University of Toronto) Dr. Siobhan O'Mahony (Assistant Professor of Business Administration, Harvard Business School) Dr. A.R.D. Prasad (Associate Professor, Documentation and Research Training Centre, Indian Statistical Institute) Mr. Nick Wainwright (Research Director, Digital Media System Department, HP Labs) Mr. Peter Walgemoed (Director, Carelliance BV, Netherlands) Ms. Ann Wolpert (Director, MIT Libraries) It was agreed at the 2005 User Group meeting at Cambridge University that the growing DSpace community has reached a critical inflection point where it may benefit from some central organization and decision-making beyond the efforts of HP and MIT, with formal participation from the broader community. Establishing governance and, possibly, funding mechanisms for the DSpace open source community will help to ensure that the technology platform remains sound, protecting the investment that institutions have made. There are no proven sustainability models, however, as open source software is relatively new and a disruptive force within the software industry. The challenge for this board is to provide feedback to HP and MIT on the options for an innovative, but practical, plan for DSpace that fosters its active, decentralized community of users and contributors while providing an appropriate level of centralized support and guidance. The advisory board will meet in-person once, on March 30-31, 2006 at MIT. The group will continue to meet via conference calls, if necessary, to expand upon or resolve any outstanding issues. In keeping with the open source software philosophy, the proceedings and recommendations of the advisory board will be shared with the entire community and your input will be solicited throughout the process. Given the emerging significance of open source software, this board will be tackling a timely and important subject. Updates will be sent to DSpace-general and posted on http://wiki.dspace.org/DSpaceGovernance. Stay tuned for more news about this ground-breaking activity! Sincerely, Julie Walker Senior Business Strategist MIT Libraries jhwalker at mit.edu From jhwalker at MIT.EDU Wed Jan 18 13:39:54 2006 From: jhwalker at MIT.EDU (Julie Harford Walker) Date: Wed, 18 Jan 2006 13:39:54 -0500 Subject: [Dspace-general] REMINDER TO REGISTER YOUR DSPACE SITE Message-ID: <5.2.1.1.2.20060117221003.02f89bd8@po10.mit.edu> ==================================== REMINDER TO REGISTER YOUR DSPACE SITE ==================================== Hello DSpace users, This is a reminder (a plea!) to register your DSpace site on the DSpace wiki, if you haven't already. An up-to-date listing of the members of the DSpace community will provide a more accurate picture of the size and characteristics of the community and help projects learn about each other. This information also will be valuable in preparation for the March 30-31 meeting of the DSpace Federation Governance Advisory Board, an ad hoc board being convened to draft a recommendation for governance and funding mechanisms to advance the DSpace community. (Please see the earlier announcement distributed on DSpace-General for more information.) Instructions for editing the DSpace Wiki can be found at http://wiki.dspace.org/HelpContents. It's easy and will only take a few minutes! For those institutions that have not registered your DSpace site, you can add your URL at http://wiki.dspace.org/DspaceInstances. Those that are interested in having your DSpace metadata harvested, list your OAI PMH base URL at http://wiki.dspace.org/OaiInstallations. While you are visiting the wiki, consider updating other areas of the site, as appropriate: If you are planning a DSpace event that you want others to know about, post that to http://wiki.dspace.org/DspaceEvents. If you are working on a DSpace development project that may have broader use in the community, please post information about it to http://wiki.dspace.org/DspaceProjects, so that others can learn about it. If you are offering services and support to the DSpace community, let us know by listing yourself or your company at http://wiki.dspace.org/ServiceProviders. Finally, if you've seen an article about DSpace or read some interesting related news, share it with the community by adding it to http://wiki.dspace.org/DspaceNews. Thanks!! From jim.ottaviani at umich.edu Fri Jan 20 15:07:53 2006 From: jim.ottaviani at umich.edu (Jim Ottaviani) Date: Fri, 20 Jan 2006 15:07:53 -0500 (EST) Subject: [Dspace-general] Dublin Core Registry quesion: creator, contributor.author, etc. Message-ID: Hello to the list, and particularly the folks who initially created the DC Registry for DSpace: I have a Dublin Core related question: Why was "creator" (creator.null) reserved only for use by harvested metadata? It seems to me, based on DC recommendatiosn, that in most cases "creator" (qualified or not) would be the appropriate place to put information that is currently recommended by DSpace (not DC) to go in e.g. the contributor.author fields. Our concern is this: In DSpace the author browse and other functions depend on looking at, and subsequently displaying, data in all fields tagged with "contributor". We don't want that to break! But as we add author affiliations to a locally-created contributor.affiliation field (as per DC's recommendations) we start to see extra information in some of the displays. (For example our author display after a search can get very long and unwieldy, what with their contributor.affiliation also appearing. Thanks, Jim ____________________________________ Jim Ottaviani +1 734-763-4835 University of Michigan Library Coordinator, Deep Blue pilot project http://deepblue.lib.umich.edu Quis custodiet ipsos custodes --Juvenal, Satires VI, 347 From robert.tansley at hp.com Fri Jan 20 17:04:05 2006 From: robert.tansley at hp.com (Tansley, Robert) Date: Fri, 20 Jan 2006 17:04:05 -0500 Subject: [Dspace-general] Dublin Core Registry quesion: creator, contributor.author, etc. Message-ID: <19ADCC0B9D4CAD4582BB9900BBCE357401AA10FE@tayexc13.americas.cpqcorp.net> > Hello to the list, and particularly the folks who initially > created the > DC Registry for DSpace: > > I have a Dublin Core related question: Why was "creator" > (creator.null) > reserved only for use by harvested metadata? Ah, this old chestnut! :-) The reason contributor.author is used by default is that the DSpace (as shipped) DC profile was based on an early draft of the DC Library Application Profile (DC-LAP, http://www.dublincore.org/documents/2004/09/10/library-application-profi le/) which recommended using contributor.XXX instead of creator for the primary author. I believe (I could be wrong) the initial reasoning behind this was that often, the *author* of the work (the person who wrote the words) might be different from the *primary creator of the electronic resource*, for example the PDF, the scan of the photograph etc. However in later versions of the profile, usage of creator was brought more in line with expectations and its uses in other profiles. We should probably fix it so that DSpace as shipped uses the up-to-date library application profile. For existing installations, it will be a little trickier to migrate/crosswalk metadata in their current profiles to a newer version of the profile. Many people have added their own extensions to the shipped DSpace profile, so writing a universal migration tool isn't easy -- such a tool needs to be very configurable. In any case, the situation will be better in DSpace 1.4 for a number of reasons: - All of the fields used in submission, search, browse and item metadata display views will be fully configurable, so for new installations you are free to determine and use your own profile or the most up-to-date LAP, and decide which fields appear as 'author' etc. - Descriptive metadata can now be added for any flat schema/namespace, and configured as described above. Although this doesn't enable "structured" metadata (for which storing in XML bitstreams is still the recommended approach), it does mean that when people have extra metadata requirements that aren't met by DC-LAP, they can pick elements from other namespaces or create their own namespaces, so that non-standard metadata elements can be distinguished from standard DC-LAP elements. So all we need is a volunteer to create a configurable tool to crosswalk metadata in live installations to a more recent/standard profile! Rob From blancoj at umich.edu Mon Jan 23 10:04:31 2006 From: blancoj at umich.edu (Jose Blanco) Date: Mon, 23 Jan 2006 10:04:31 -0500 Subject: [Dspace-general] Dublin Core Registry quesion: creator, contributor.author, etc. In-Reply-To: <19ADCC0B9D4CAD4582BB9900BBCE357401AA10FE@tayexc13.americas.cpqcorp.net> Message-ID: <200601231502.k0NF2fnY000618@playinggod.mr.itd.umich.edu> So the question now is, when is 1.4 going to become available? I just searched the tech archive and could not find an answer. Any idea? Thanks! -----Original Message----- From: dspace-general-bounces at mit.edu [mailto:dspace-general-bounces at mit.edu] On Behalf Of Tansley, Robert Sent: Friday, January 20, 2006 5:04 PM To: Jim Ottaviani; dspace-general at mit.edu Subject: Re: [Dspace-general] Dublin Core Registry quesion: creator,contributor.author, etc. > Hello to the list, and particularly the folks who initially > created the > DC Registry for DSpace: > > I have a Dublin Core related question: Why was "creator" > (creator.null) > reserved only for use by harvested metadata? Ah, this old chestnut! :-) The reason contributor.author is used by default is that the DSpace (as shipped) DC profile was based on an early draft of the DC Library Application Profile (DC-LAP, http://www.dublincore.org/documents/2004/09/10/library-application-profi le/) which recommended using contributor.XXX instead of creator for the primary author. I believe (I could be wrong) the initial reasoning behind this was that often, the *author* of the work (the person who wrote the words) might be different from the *primary creator of the electronic resource*, for example the PDF, the scan of the photograph etc. However in later versions of the profile, usage of creator was brought more in line with expectations and its uses in other profiles. We should probably fix it so that DSpace as shipped uses the up-to-date library application profile. For existing installations, it will be a little trickier to migrate/crosswalk metadata in their current profiles to a newer version of the profile. Many people have added their own extensions to the shipped DSpace profile, so writing a universal migration tool isn't easy -- such a tool needs to be very configurable. In any case, the situation will be better in DSpace 1.4 for a number of reasons: - All of the fields used in submission, search, browse and item metadata display views will be fully configurable, so for new installations you are free to determine and use your own profile or the most up-to-date LAP, and decide which fields appear as 'author' etc. - Descriptive metadata can now be added for any flat schema/namespace, and configured as described above. Although this doesn't enable "structured" metadata (for which storing in XML bitstreams is still the recommended approach), it does mean that when people have extra metadata requirements that aren't met by DC-LAP, they can pick elements from other namespaces or create their own namespaces, so that non-standard metadata elements can be distinguished from standard DC-LAP elements. So all we need is a volunteer to create a configurable tool to crosswalk metadata in live installations to a more recent/standard profile! Rob _______________________________________________ Dspace-general mailing list Dspace-general at mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general From richard.jones at ub.uib.no Mon Jan 23 10:55:42 2006 From: richard.jones at ub.uib.no (Richard Jones) Date: Mon, 23 Jan 2006 16:55:42 +0100 Subject: [Dspace-general] DSpace User Group Meeting, Bergen 2006: Registration open Message-ID: <1138031743.11862.210.camel@ubbtilv067115> DSpace User Group Meeting, Bergen, 2006 "Dugnad" among the fjords 19 April (IR workshop), 20-21 April 2006 (DSUG) ------------------------------------------------------------------------ The Program Committee for the DSpace User Group Meeting, Bergen, 2006 is pleased to announce the opening of registration for this event and the associated Institutional Repositories workshop. The theme of the meeting is to look at developments that have allowed DSpace to be embedded into institutional systems and practices, and what other uses DSpace has found for itself in the institution. There will be short and long presentations with break-out sessions to discuss both technical and administrative issues, as well as poster space and workshops and tutorials in areas of DSpace that are of interest to attendees. Accompanying this will be a satellite Institutional Repository workshop on 19 April 2006, which will address policy, advocacy and open access concerns for institutions working on IRs. This meeting can be attended independently of the main user group meeting. The meetings will be held at the Scandic Bergen City hotel in the city centre. Full information on the proceedings can be found at: http://dsug2006.uib.no/ The cost of each of the three days is 800 NOK (approximately US$120 / ?99 / ?68) Registration includes the following: -Participation in the selected days -Coffee/Tea and snacks during the conference -All lunches during the conference -The drinks reception on Day 1 (For all attendees of the IR Workshop and the DSpace User Group Meeting) -Transport and Dinner on Day 2 (For attendees of the DSpace User Group Meeting) -All documentation and hand-outs from the conference Registration for this event can be done via the conference website at: http://dsug2006.uib.no/index.php?p=reg The call for papers for this event is also still open, so if you have something you would like to present please look at the following page for more information: http://dsug2006.uib.no/index.php?p=call We hope to see you in the spring. Best wishes, -- Richard ------- Richard Jones | Overingeni?r | Senior Engineer Universitetsbiblioteket i Bergen | University of Bergen Library e: richard.jones at ub.uib.no t: +47 55 58 25 37 BORA: http://bora.uib.no/ From robert.tansley at hp.com Mon Jan 23 18:21:42 2006 From: robert.tansley at hp.com (Tansley, Robert) Date: Mon, 23 Jan 2006 18:21:42 -0500 Subject: [Dspace-general] Dublin Core Registry quesion: creator, contributor.author, etc. Message-ID: <19ADCC0B9D4CAD4582BB9900BBCE357401AA1101@tayexc13.americas.cpqcorp.net> > So the question now is, when is 1.4 going to become available? I just > searched the tech archive and could not find an answer. Any idea? Hi Jose, As you've probably noticed, DSpace doesn't really have a formally specified release schedule now! That's largely because the release cycle depends on some unpredictable factors: - How much time the committers have to put in patches, liaise with contributors - How many features we think we can get into the next release. This is a case of drawing a line in the sand somewhere -- there are always new features we could include in the next release but each new feature added pushes the release cycle further back. - How long testing, bug fixing and documentation takes after a 'feature freeze' Right now, we're approaching a feature freeze; one last thing we (the committers) are really hoping to get in is an improved and documented add-on mechanism. As soon as that's done we'll release an alpha. Once things have stablised a bit we'll go beta, and once enough QA has been done and documentation ready, we'll release the full version. I'm guessing the full release will be some time in March now, but that depends on how much the community mucks in to help out with the testing, bug reporting/fixing and so forth, so you can speed up the process by getting involved in that! Robert TANSLEY / HP Labs / MIT Visiting Researcher http://www.hpl.hp.com/personal/Robert_Tansley/ > -----Original Message----- > From: dspace-general-bounces at mit.edu > [mailto:dspace-general-bounces at mit.edu] > On Behalf Of Tansley, Robert > Sent: Friday, January 20, 2006 5:04 PM > To: Jim Ottaviani; dspace-general at mit.edu > Subject: Re: [Dspace-general] Dublin Core Registry quesion: > creator,contributor.author, etc. > > > Hello to the list, and particularly the folks who initially > > created the > > DC Registry for DSpace: > > > > I have a Dublin Core related question: Why was "creator" > > (creator.null) > > reserved only for use by harvested metadata? > > Ah, this old chestnut! :-) > > The reason contributor.author is used by default is that the > DSpace (as > shipped) DC profile was based on an early draft of the DC Library > Application Profile (DC-LAP, > http://www.dublincore.org/documents/2004/09/10/library-applica > tion-profi > le/) which recommended using contributor.XXX instead of > creator for the > primary author. I believe (I could be wrong) the initial reasoning > behind this was that often, the *author* of the work (the person who > wrote the words) might be different from the *primary creator of the > electronic resource*, for example the PDF, the scan of the photograph > etc. However in later versions of the profile, usage of creator was > brought more in line with expectations and its uses in other profiles. > > We should probably fix it so that DSpace as shipped uses the > up-to-date > library application profile. For existing installations, it will be a > little trickier to migrate/crosswalk metadata in their > current profiles > to a newer version of the profile. Many people have added their own > extensions to the shipped DSpace profile, so writing a universal > migration tool isn't easy -- such a tool needs to be very > configurable. > > In any case, the situation will be better in DSpace 1.4 for a > number of > reasons: > > - All of the fields used in submission, search, browse and > item metadata > display views will be fully configurable, so for new installations you > are free to determine and use your own profile or the most up-to-date > LAP, and decide which fields appear as 'author' etc. > > - Descriptive metadata can now be added for any flat schema/namespace, > and configured as described above. Although this doesn't enable > "structured" metadata (for which storing in XML bitstreams is > still the > recommended approach), it does mean that when people have > extra metadata > requirements that aren't met by DC-LAP, they can pick elements from > other namespaces or create their own namespaces, so that non-standard > metadata elements can be distinguished from standard DC-LAP elements. > > So all we need is a volunteer to create a configurable tool > to crosswalk > metadata in live installations to a more recent/standard profile! > > Rob > > _______________________________________________ > Dspace-general mailing list > Dspace-general at mit.edu > http://mailman.mit.edu/mailman/listinfo/dspace-general > > > > From m.altheim at open.ac.uk Mon Jan 23 19:06:43 2006 From: m.altheim at open.ac.uk (Murray Altheim) Date: Tue, 24 Jan 2006 00:06:43 +0000 Subject: [Dspace-general] Dublin Core Registry quesion: creator, contributor.author, etc. In-Reply-To: <19ADCC0B9D4CAD4582BB9900BBCE357401AA1101@tayexc13.americas.cpqcorp.net> References: <19ADCC0B9D4CAD4582BB9900BBCE357401AA1101@tayexc13.americas.cpqcorp.net> Message-ID: <43D56F93.10400@open.ac.uk> Tansley, Robert wrote: >>So the question now is, when is 1.4 going to become available? I just >>searched the tech archive and could not find an answer. Any idea? > > Hi Jose, > > As you've probably noticed, DSpace doesn't really have a formally > specified release schedule now! That's largely because the release > cycle depends on some unpredictable factors: > > - How much time the committers have to put in patches, liaise with > contributors > > - How many features we think we can get into the next release. This is > a case of drawing a line in the sand somewhere -- there are always new > features we could include in the next release but each new feature added > pushes the release cycle further back. > > - How long testing, bug fixing and documentation takes after a 'feature > freeze' > > Right now, we're approaching a feature freeze; one last thing we (the > committers) are really hoping to get in is an improved and documented > add-on mechanism. As soon as that's done we'll release an alpha. Once > things have stablised a bit we'll go beta, and once enough QA has been > done and documentation ready, we'll release the full version. I'm > guessing the full release will be some time in March now, but that > depends on how much the community mucks in to help out with the testing, > bug reporting/fixing and so forth, so you can speed up the process by > getting involved in that! Robert, One question that is sometimes not asked about a project: when does one declare it completed? It's possible to continue to add features ad infinitum, and as with many software projects -- particularly open source ones managed by many -- they bloat out way beyond their initial requirements. Is there some sense of a completion schedule for DSPace, or is it expected to continually enlarge its code base until it has passed into the great software heaven in the sky (where all the good software goes), or does it finally end up in software hell, after that one wafer thin line of code too many? It would seem that there would reach a point of diminishing returns regarding features, when consolidation, documentation, and reaching a point of code stability might be in order. Is there some point in mind for DSpace? Thanks very much, Murray ...................................................................... Murray Altheim http://www.altheim.com/murray/ Strategic Systems Development Manager The Open University Library and Learning Resources Centre The Open University, Milton Keynes, Bucks, MK7 6AA, UK . Short of taking the current president of the United States by the scruff of the neck and dunking his head deep into the rapidly melting Arctic ice cap, what more did the Earth need to do to make someone listen to its cry for help? -- Simon Schama, The Story So Far http://www.guardian.co.uk/g2/story/0,3604,1675173,00.html From robert.tansley at hp.com Tue Jan 24 11:34:37 2006 From: robert.tansley at hp.com (Tansley, Robert) Date: Tue, 24 Jan 2006 11:34:37 -0500 Subject: [Dspace-general] Scope of DSpace (Was: Dublin Core Registry question) Message-ID: <19ADCC0B9D4CAD4582BB9900BBCE357401AA1108@tayexc13.americas.cpqcorp.net> Hi Murray, > One question that is sometimes not asked about a project: when does > one declare it completed? It's possible to continue to add features > ad infinitum, and as with many software projects -- particularly open > source ones managed by many -- they bloat out way beyond their initial > requirements. Is there some sense of a completion schedule for DSPace, > or is it expected to continually enlarge its code base until it has > passed into the great software heaven in the sky (where all the good > software goes), or does it finally end up in software hell, after > that one wafer thin line of code too many? > > It would seem that there would reach a point of diminishing returns > regarding features, when consolidation, documentation, and reaching > a point of code stability might be in order. Is there some point in > mind for DSpace? Great questions. In fact it touches on a theme I'm hoping to cover and start discussion around in presentations I'm giving at the DSpace user group meeting in Sydney next week. It's true that DSpace can't simply keep growing in all directions, encompassing thousands of features. However, I don't think we yet know enough about exactly what we need out of systems like DSpace. That was one of the reasons for releasing it as open source in the first place: the idea was to get something out there, and let the community mould it to its emerging needs, rather than to try and decide a priori/in isolation what was needed. The questions "what should DSpace be? What should it do? What shouldn't it do? How should it fit in with other systems/technologies/servces?" are interesting questions in their own right, as interesting to me as research questions as many of the more technical decisions made when developing the system. DSpace clearly can't be all things to all people, so we need to decide where it sits in the ecosystem of tools, technologies and services out there in this space. However this should be a conclusion arrived at by the community as a whole -- HP (and I believe MIT) don't believe it's our place or would be the best approach to dictate this to everyone else. It's precisely this uncertainty in exactly what's required and possible in terms of technologies and services that makes DSpace such an interesting project and why open source is the right vehicle for it. Until now, the majority of work on DSpace has been in the area of user interface functionality. I think that's been for two reasons: - UI changes are easy to demonstrate and show to those holding the purse strings - For the majority, it seems the most immediate problem is how to get actual content into their repositories, and additional features that give faculty members utility and demonstrate increased impact of their work are a way to entice them. Moving forward, we definitely need some consolidation, documentation and so forth. This has been the hardest thing to get wider community involvement in: it seems people like creating new features, but don't like the attendant bug fixing, QA, documentation and other 'weeding' tasks (and/or they perceive this as the committer group's task.) So, what I've been trying to push for moving forward is: - More community involvement in the 'weeding' - Decoupling parts of the system (modularising) so that complexity can be contained. I envisage DSpace having a core set of functionality, with a rich selection of add-ons, many of which might not be required by everyone - Trying to start conversations about this very topic! As for DSpace being 'complete', actually I hope that will never happen :-) Software is like biology, in that there is a common word used to describe a completely stable object: "Dead". Robert TANSLEY / HP Labs / MIT Visiting Researcher http://www.hpl.hp.com/personal/Robert_Tansley/ From sandy.mackenzie at imperial.ac.uk Tue Jan 24 13:11:28 2006 From: sandy.mackenzie at imperial.ac.uk (MacKenzie, Sandy) Date: Tue, 24 Jan 2006 18:11:28 -0000 Subject: [Dspace-general] Vacancy for DSpace technical position Message-ID: Hi, We have a vacancy for soemone with developer skills, tomcat, jsp etc along with postrgresql knowledge to work on our DSpace project. Please follow the link to our "Web and Database Technology Specialist" if interested. Sandy MacKenzie Imperial College London From blancoj at umich.edu Tue Jan 24 16:19:07 2006 From: blancoj at umich.edu (Jose Blanco) Date: Tue, 24 Jan 2006 16:19:07 -0500 Subject: [Dspace-general] Dublin Core Registry quesion: creator, contributor.author, etc. In-Reply-To: <19ADCC0B9D4CAD4582BB9900BBCE357401AA1101@tayexc13.americas.cpqcorp.net> Message-ID: <200601242120.k0OLKCnY030265@playinggod.mr.itd.umich.edu> Rob: I've got one more questions on this: > - All of the fields used in submission, search, browse and item > metadata display views will be fully configurable, so for new > installations you are free to determine and use your own profile or > the most up-to-date LAP, and decide which fields appear as 'author' > etc. Will this configuration be done on a collection basis or for the entire instance? And I assume that with version 1.4 I can setup the browse for author to use any dc value. I'm thinking in particular of creator.author? Thank you! Jose -----Original Message----- From: Tansley, Robert [mailto:robert.tansley at hp.com] Sent: Monday, January 23, 2006 6:22 PM To: Jose Blanco; Jim Ottaviani; dspace-general at mit.edu Subject: RE: [Dspace-general] Dublin Core Registry quesion: creator,contributor.author, etc. > So the question now is, when is 1.4 going to become available? I just > searched the tech archive and could not find an answer. Any idea? Hi Jose, As you've probably noticed, DSpace doesn't really have a formally specified release schedule now! That's largely because the release cycle depends on some unpredictable factors: - How much time the committers have to put in patches, liaise with contributors - How many features we think we can get into the next release. This is a case of drawing a line in the sand somewhere -- there are always new features we could include in the next release but each new feature added pushes the release cycle further back. - How long testing, bug fixing and documentation takes after a 'feature freeze' Right now, we're approaching a feature freeze; one last thing we (the committers) are really hoping to get in is an improved and documented add-on mechanism. As soon as that's done we'll release an alpha. Once things have stablised a bit we'll go beta, and once enough QA has been done and documentation ready, we'll release the full version. I'm guessing the full release will be some time in March now, but that depends on how much the community mucks in to help out with the testing, bug reporting/fixing and so forth, so you can speed up the process by getting involved in that! Robert TANSLEY / HP Labs / MIT Visiting Researcher http://www.hpl.hp.com/personal/Robert_Tansley/ > -----Original Message----- > From: dspace-general-bounces at mit.edu > [mailto:dspace-general-bounces at mit.edu] > On Behalf Of Tansley, Robert > Sent: Friday, January 20, 2006 5:04 PM > To: Jim Ottaviani; dspace-general at mit.edu > Subject: Re: [Dspace-general] Dublin Core Registry quesion: > creator,contributor.author, etc. > > > Hello to the list, and particularly the folks who initially > > created the > > DC Registry for DSpace: > > > > I have a Dublin Core related question: Why was "creator" > > (creator.null) > > reserved only for use by harvested metadata? > > Ah, this old chestnut! :-) > > The reason contributor.author is used by default is that the > DSpace (as > shipped) DC profile was based on an early draft of the DC Library > Application Profile (DC-LAP, > http://www.dublincore.org/documents/2004/09/10/library-applica > tion-profi > le/) which recommended using contributor.XXX instead of > creator for the > primary author. I believe (I could be wrong) the initial reasoning > behind this was that often, the *author* of the work (the person who > wrote the words) might be different from the *primary creator of the > electronic resource*, for example the PDF, the scan of the photograph > etc. However in later versions of the profile, usage of creator was > brought more in line with expectations and its uses in other profiles. > > We should probably fix it so that DSpace as shipped uses the > up-to-date > library application profile. For existing installations, it will be a > little trickier to migrate/crosswalk metadata in their > current profiles > to a newer version of the profile. Many people have added their own > extensions to the shipped DSpace profile, so writing a universal > migration tool isn't easy -- such a tool needs to be very > configurable. > > In any case, the situation will be better in DSpace 1.4 for a > number of > reasons: > > - All of the fields used in submission, search, browse and > item metadata > display views will be fully configurable, so for new installations you > are free to determine and use your own profile or the most up-to-date > LAP, and decide which fields appear as 'author' etc. > > - Descriptive metadata can now be added for any flat schema/namespace, > and configured as described above. Although this doesn't enable > "structured" metadata (for which storing in XML bitstreams is > still the > recommended approach), it does mean that when people have > extra metadata > requirements that aren't met by DC-LAP, they can pick elements from > other namespaces or create their own namespaces, so that non-standard > metadata elements can be distinguished from standard DC-LAP elements. > > So all we need is a volunteer to create a configurable tool > to crosswalk > metadata in live installations to a more recent/standard profile! > > Rob > > _______________________________________________ > Dspace-general mailing list > Dspace-general at mit.edu > http://mailman.mit.edu/mailman/listinfo/dspace-general > > > > From m.altheim at open.ac.uk Tue Jan 24 20:25:08 2006 From: m.altheim at open.ac.uk (Murray Altheim) Date: Wed, 25 Jan 2006 01:25:08 +0000 Subject: [Dspace-general] Scope of DSpace (Was: Dublin Core Registry question) In-Reply-To: <19ADCC0B9D4CAD4582BB9900BBCE357401AA1108@tayexc13.americas.cpqcorp.net> References: <19ADCC0B9D4CAD4582BB9900BBCE357401AA1108@tayexc13.americas.cpqcorp.net> Message-ID: <43D6D374.5090204@open.ac.uk> Tansley, Robert wrote: > Hi Murray, > >>One question that is sometimes not asked about a project: when does >>one declare it completed? It's possible to continue to add features >>ad infinitum, and as with many software projects -- particularly open >>source ones managed by many -- they bloat out way beyond their initial >>requirements. Is there some sense of a completion schedule for DSPace, >>or is it expected to continually enlarge its code base until it has >>passed into the great software heaven in the sky (where all the good >>software goes), or does it finally end up in software hell, after >>that one wafer thin line of code too many? >> >>It would seem that there would reach a point of diminishing returns >>regarding features, when consolidation, documentation, and reaching >>a point of code stability might be in order. Is there some point in >>mind for DSpace? > > Great questions. In fact it touches on a theme I'm hoping to cover and > start discussion around in presentations I'm giving at the DSpace user > group meeting in Sydney next week. Sad I won't have a chance to be there. Hopefully any papers or transcripts will be posted and announced to this list (hint: that would be valuable and appreciated). > It's true that DSpace can't simply keep growing in all directions, > encompassing thousands of features. However, I don't think we yet know > enough about exactly what we need out of systems like DSpace. That was > one of the reasons for releasing it as open source in the first place: > the idea was to get something out there, and let the community mould it > to its emerging needs, rather than to try and decide a priori/in > isolation what was needed. Certainly -- the field is very new and as far as I'm concerned, this will likely be among the hottest areas for IT development for the next decade. We live in a world of disordered information, and don't often have ready and convenient access to digital content online, at least the kinds of content that we'll increasingly be seeing in what we're now calling digital libraries. The software that provides us with the foundation for our research into the field and into how we can better serve peoples' needs will certainly change over time, likely very rapidly. > The questions "what should DSpace be? What should it do? What > shouldn't it do? How should it fit in with other > systems/technologies/servces?" are interesting questions in their own > right, as interesting to me as research questions as many of the more > technical decisions made when developing the system. DSpace clearly > can't be all things to all people, so we need to decide where it sits in > the ecosystem of tools, technologies and services out there in this > space. However this should be a conclusion arrived at by the community > as a whole -- HP (and I believe MIT) don't believe it's our place or > would be the best approach to dictate this to everyone else. It's > precisely this uncertainty in exactly what's required and possible in > terms of technologies and services that makes DSpace such an interesting > project and why open source is the right vehicle for it. Rather than trying to make decisions, or suggest decisions be made by the DSpace community, might I suggest a path? Modularization. As much as is reasonable, DSpace features should be modularized, so that there is a core DSpace engine, with almost all services plug-and-play. In this way it permits the community to deliberately fragment into interest areas, building the modular tools the subcommunities are interested in, and allowing implementors to create installations that suit their needs without overburdening them with an enormously complex base package. E.g., so if somebody doesn't need OAI features, or they want a local system rather than an online one, they choose the modules they need (or there is an install system to permit them to do so easily). I realize this takes a higher level architectural approach, one that is sometimes difficult in a rather amorphous, fast-moving development like DSpace. And I confess -- there might already be modularization efforts going on in DSpace that I'm not aware of -- I haven't spent much time with the code myself. > Until now, the majority of work on DSpace has been in the area of user > interface functionality. I think that's been for two reasons: > > - UI changes are easy to demonstrate and show to those holding the purse > strings > > - For the majority, it seems the most immediate problem is how to get > actual content into their repositories, and additional features that > give faculty members utility and demonstrate increased impact of their > work are a way to entice them. In my own work (which is currently somewhere around 150K linesof Java code), I'd say that the majority of my time has been spent in similar fashion. Anyone who's done UI work would attest to it being as close to hell as one can get in software development. Tedious work. But it's where the rubber meets the road, if one's users are the rubber or the road (some of these metaphors have limited usefulness). > Moving forward, we definitely need some consolidation, documentation and > so forth. This has been the hardest thing to get wider community > involvement in: it seems people like creating new features, but don't > like the attendant bug fixing, QA, documentation and other 'weeding' > tasks (and/or they perceive this as the committer group's task.) Well, this is true in professional corporate environments too. Everyone wants to be an architect and designer; nobody wants to sit in the back room and do QA, fixing other people's bugs. And a good documentation person is like finding a good bass player. Everybody wants to wear spandex and stand at the front of the stage playing guitar. We all know who Pete Townsend and Keith Richards are, but how many have heard of John Entwhistle or Bill Wyman? The latter two are QA guys. The trick is to locate people who like standing in the back and providing the foundation. They're hard to find, but HP and MIT might be able to help here, dunno. > So, what I've been trying to push for moving forward is: > > - More community involvement in the 'weeding' > > - Decoupling parts of the system (modularising) so that complexity can > be contained. I envisage DSpace having a core set of functionality, > with a rich selection of add-ons, many of which might not be required by > everyone I should have read ahead. I see we agree... > - Trying to start conversations about this very topic! Glad to be of any help in that regard. > As for DSpace being 'complete', actually I hope that will never happen > :-) Software is like biology, in that there is a common word used to > describe a completely stable object: "Dead". I agree, but death can also happen when the lake fills up with algae. Modularization is one good solution to that, and I'm happy to see you mention it. Any on this list who might know me know I've long been a big fan of modularization. Robert, thanks very much. In looking across the DL space right now things are changing fast, and DSpace is poised to inhabit a great niche within that, particularly if the package is flexible enough to be used in varying applications. I look forward to watching things grow, and as I'm able in the future to participate in design and coding. And yes, I've played both guitar and bass before. Murray ...................................................................... Murray Altheim http://www.altheim.com/murray/ Strategic Systems Development Manager The Open University Library and Learning Resources Centre The Open University, Milton Keynes, Bucks, MK7 6AA, UK . Short of taking the current president of the United States by the scruff of the neck and dunking his head deep into the rapidly melting Arctic ice cap, what more did the Earth need to do to make someone listen to its cry for help? -- Simon Schama, The Story So Far http://www.guardian.co.uk/g2/story/0,3604,1675173,00.html From richard.jones at ub.uib.no Wed Jan 25 04:35:54 2006 From: richard.jones at ub.uib.no (Richard Jones) Date: Wed, 25 Jan 2006 10:35:54 +0100 Subject: [Dspace-general] Scope of DSpace (Was: Dublin Core Registry question) In-Reply-To: <43D6D374.5090204@open.ac.uk> References: <19ADCC0B9D4CAD4582BB9900BBCE357401AA1108@tayexc13.americas.cpqcorp.net> <43D6D374.5090204@open.ac.uk> Message-ID: <1138181754.11862.336.camel@ubbtilv067115> Hi Folks, I've CC'd this to dspace-tech, as it seems appropriate for there also > Rather than trying to make decisions, or suggest decisions be made by > the DSpace community, might I suggest a path? Modularization. As much > as is reasonable, DSpace features should be modularized, so that there > is a core DSpace engine, with almost all services plug-and-play. In > this way it permits the community to deliberately fragment into > interest areas, building the modular tools the subcommunities are > interested in, and allowing implementors to create installations that > suit their needs without overburdening them with an enormously complex > base package. E.g., so if somebody doesn't need OAI features, or they > want a local system rather than an online one, they choose the modules > they need (or there is an install system to permit them to do so easily). Hopefully the AddOn Mech should make this process easier, and if you are interested in helping out or having a look at it at least, you could start with: http://wiki.dspace.org/AddOnMechanism Anyway, I have a crazy idea with regard to modularising the DSpace code base. It's maybe a bit extreme in terms of organisation, but here it is: Would it be sensible/useful to organise at some point a "Developer Camp", where those of us who wanted to could get together for anything up to a week at a host institution with a pile of computers and as much of our own code as we want to bring and actually physically start to pull the codebase appart into a series of modules? It may be unworkable, but the way I see it is that this sort of effort is quite large, and requires some commitment from those undertaking it. Since we all have day jobs I worry that the impetus/resources to actually make a start is lacking. A blitz /may/ overcome that. Or we might end up with a pile of broken code ;) Just a thought. Cheers, -- Richard ------- Richard Jones | Overingeni?r | Senior Engineer Universitetsbiblioteket i Bergen | University of Bergen Library e: richard.jones at ub.uib.no t: +47 55 58 25 37 BORA: http://bora.uib.no/ From kenzie at MIT.EDU Wed Jan 25 12:34:27 2006 From: kenzie at MIT.EDU (MacKenzie Smith) Date: Wed, 25 Jan 2006 12:34:27 -0500 Subject: [Dspace-general] Scope of DSpace In-Reply-To: <1138181754.11862.336.camel@ubbtilv067115> References: <43D6D374.5090204@open.ac.uk> <19ADCC0B9D4CAD4582BB9900BBCE357401AA1108@tayexc13.americas.cpqcorp.net> <43D6D374.5090204@open.ac.uk> Message-ID: <5.2.1.1.2.20060125122414.011fbc68@hesiod> At 10:35 AM 1/25/2006 +0100, Richard Jones wrote: >Anyway, I have a crazy idea with regard to modularising the DSpace code >base. It's maybe a bit extreme in terms of organisation, but here it >is: Would it be sensible/useful to organise at some point a "Developer >Camp", where those of us who wanted to could get together for anything up >to a week at a host institution with a pile of computers and as much of >our own code as we want to bring and actually physically start to pull the >codebase appart into a series of modules? Not crazy, this is on the agenda to try to do this year, but it's a long agenda with many moving parts. Here's the plan: -- we're having the discussion with an advisory board in late March about "community governance and resource planning" -- that will lead to some direction/decisions about whether to generate more resources (i.e. people and/or money) to do things like QA, release management, and organizing/running developers meetings so we can make faster progress on these critical questions The advisory board will consider both the what and the how... what central support and/or infrastructure does this community need to thrive, if any, and how should we pay for that. I'm pretty optimistic that the outcome (hopefully with input from the rest of the DSpace community) will allow us to move ahead with things like annual user group meetings in relevant geographic areas, more predictable release planning, and developer forums on a regular basis. Until then, I believe you're right -- having these discussions online is useful, but it's too hard to come to closure and we need more resources (mainly people's time) to get beyond this stage. MacKenzie MacKenzie Smith Associate Director for Technology MIT Libraries Building E25-131d 77 Massachusetts Avenue Cambridge, MA 02139 (617)253-8184 kenzie at mit.edu From hussein at cs.uct.ac.za Wed Jan 25 15:06:19 2006 From: hussein at cs.uct.ac.za (Hussein Suleman) Date: Wed, 25 Jan 2006 22:06:19 +0200 Subject: [Dspace-general] Scope of DSpace (Was: Dublin Core Registry question) In-Reply-To: <1138181754.11862.336.camel@ubbtilv067115> References: <19ADCC0B9D4CAD4582BB9900BBCE357401AA1108@tayexc13.americas.cpqcorp.net> <43D6D374.5090204@open.ac.uk> <1138181754.11862.336.camel@ubbtilv067115> Message-ID: <43D7DA3B.4020901@cs.uct.ac.za> hi just to add my support for this idea, i think modularisation is definitely the way to go! but i hope people think of modularisation beyond just the DSpace JARs and build system. if you are following Greenstone3, you will know they are modularising around some kind of Web Services architecture. if DSpace did something similar then we may one day be able to distribute software with specialised services that can plug into more than one digital library base system. then it will be much more useful for anyone who produces interesting services (like an exotic recommender) to make them modular and available to the community at large ... and a lot more cool stuff will become possible too :) ttfn, ----hussein ===================================================================== hussein suleman ~ hussein at cs.uct.ac.za ~ http://www.husseinsspace.com ===================================================================== Richard Jones wrote: > Hi Folks, > > I've CC'd this to dspace-tech, as it seems appropriate for there also > > >>Rather than trying to make decisions, or suggest decisions be made by >>the DSpace community, might I suggest a path? Modularization. As much >>as is reasonable, DSpace features should be modularized, so that there >>is a core DSpace engine, with almost all services plug-and-play. In >>this way it permits the community to deliberately fragment into >>interest areas, building the modular tools the subcommunities are >>interested in, and allowing implementors to create installations that >>suit their needs without overburdening them with an enormously complex >>base package. E.g., so if somebody doesn't need OAI features, or they >>want a local system rather than an online one, they choose the modules >>they need (or there is an install system to permit them to do so easily). > > > Hopefully the AddOn Mech should make this process easier, and if you are > interested in helping out or having a look at it at least, you could > start with: > > http://wiki.dspace.org/AddOnMechanism > > Anyway, I have a crazy idea with regard to modularising the DSpace code > base. It's maybe a bit extreme in terms of organisation, but here it > is: Would it be sensible/useful to organise at some point a "Developer > Camp", where those of us who wanted to could get together for anything > up to a week at a host institution with a pile of computers and as much > of our own code as we want to bring and actually physically start to > pull the codebase appart into a series of modules? It may be > unworkable, but the way I see it is that this sort of effort is quite > large, and requires some commitment from those undertaking it. Since we > all have day jobs I worry that the impetus/resources to actually make a > start is lacking. A blitz /may/ overcome that. Or we might end up with > a pile of broken code ;) > > Just a thought. > > Cheers, > From harnad at ecs.soton.ac.uk Thu Jan 26 23:26:19 2006 From: harnad at ecs.soton.ac.uk (Stevan Harnad) Date: Fri, 27 Jan 2006 04:26:19 +0000 (GMT) Subject: [Dspace-general] Newly enhanced Registry of Open Access Repositories (ROAR) Message-ID: For researchers or OA advocates (or detractors!) who are interested in the current state, growth rate and distribution of Open Access Repositories (or Archives) worldwide, ROAR http://archives.eprints.org/ the Registry of Open Access Repositories (created by Southampton doctoral student Tim Brody) allows anyone to generate growth charts by archive type, or by individual archive. It can also rank-order archives by the number of OAI records they currently contain (i.e., their size) ROAR is a gold-mine of current, cumulating data, ripe for anyone enterprising enough to want to report an up-to-date quantitative analysis of how OA IRs are progressing today, and where. I also take this opportunity to remind all OA Archives and OA IRs to please *register* with ROAR so you too can be counted, and your content growth tracked. (If your archive is registered, but is not being picked up by celestial, please add your OAI Base URL.) http://archives.eprints.org/index.php?action=add The size and growth data are classified by the type of Archive: (i) Distributed Institutional/Departmental Pre-/Postprint Archives (284), (ii) Central Cross- Discipline Research Archives (69) (iii) Dissertation Archives (e-theses) (62) as well as (iv) database Archives (e.g. research data) (10) (v) e-journal/e-publishing Archives (56) (vi) demonstration Archives (not yet operational) (25) (vii) "other" Archives (non-OA content of various kinds) (81) The archives can also be classified by country, and by the software they use (BePress/ProQuest 25, Dspace 124, Eprints 196, etc.) One caveat: The number of OAI records does not necessarily correspond to the actual number of full-text articles or dissertations in the IR! For many archives the records are still only the metadata (author, title, etc.), not the full-texts themselves. ROAR will soon have a way of counting only full-texts, separately (for Eprints it already does so.) Meanwhile, contents will have to be sampled to estimate what percentage of the records are just metadata and what percentage are full-texts. (Some of the central archives are full-text only, and many of the advanced institutional archives, especially the ones with self-archiving mandates, are also mostly full-text.) Even among full-texts, not all may be OA's target contents (journal article postprints and preprints plus dissertations). They may be documents of other kinds (teaching materials, multimedia, "gray literature," even administrative records). ROAR does not register archives that *only* contain metadata; among archive types (i)-(iii), ROAR also does not register archives that do not target OA content -- preprints, postprints, theses -- at all. Prior Amsci Topic Thread: Newly enhanced Registry of Open Access Repositories (ROAR) (June, 2005) http://www.ecs.soton.ac.uk/~harnad/Hypermail/Amsci/4586.html Stevan Harnad From gbunton at odu.edu Fri Jan 27 12:19:52 2006 From: gbunton at odu.edu (Glenn Bunton) Date: Fri, 27 Jan 2006 12:19:52 -0500 Subject: [Dspace-general] Newbie questions Message-ID: Hello to all, We are just beginning our exploration of Dspace and I'm hoping to find some guidance towards helpful instructional resources. Has anyone created any tutorials for how to effectively use dspace? Any other suggestions regarding best ways of learning how to use the system? Thanks. ================================== Mr. Glenn Bunton Head of Systems Development Old Dominion University Libraries Norfolk, Virginia 23529 gbunton at odu.edu (757) 683-5952 =================================== From adavidow at jwa.org Fri Jan 27 17:35:53 2006 From: adavidow at jwa.org (Ari Davidow) Date: Fri, 27 Jan 2006 17:35:53 -0500 Subject: [Dspace-general] Jewish Women's Archive RFP for Online Collecting In-Reply-To: <5.2.1.1.2.20060125122414.011fbc68@hesiod> Message-ID: <00b401c62392$08a58360$e1000d0a@JWA.local> Hi all, I hope that this is an appropriate place to post this RFP. The Jewish Women's Archive has a Java/Oracle custom-coded Virtual Archive at http://www.jwa.org. We are currently looking at an Online Collecting tool, and are very interested in having that built on top of DSpace (Java/PostgreSQL?). Longer-term, once DSpace is installed, we'd like to migrate our existing archive to DSpace. I am hoping that someone on this list works for a vendor with significant DSpace savvy, as well as the requisite interface, web 2.0 (for buzzword compliance and tagging), and project management experience to ensure that this project is as fun as it should be. The RFP, including a short description of the JWA, can be accessed at http://dev.jwa.org/rfp/060127_online_collecting.html Please do contact me with questions, comments, and proposals. Do feel free to pass this on to relevant interested parties. Many thanks, Ari Ari Davidow Director for Online Strategy Jewish Women's Archive adavidow at jwa.org tel: 617 383 6766 / cell: 617 413 0425 From harnad at ecs.soton.ac.uk Sat Jan 28 12:19:44 2006 From: harnad at ecs.soton.ac.uk (Stevan Harnad) Date: Sat, 28 Jan 2006 17:19:44 +0000 (GMT) Subject: [Dspace-general] Bronze release of RAE software for OA repositories Message-ID: (excerpt below is from Peter Suber's Open Access News) Note: "RAE" = "Research Assessment Exercise" in which each department of each UK university is evaluated for its research performance every four years. http://www.rae.ac.uk/ Australia is planning a similar exercise, the RQF ("Research Quality Framework"), to which this announcement is also pertinent. http://www.dest.gov.au/sectors/research_sector/policies_issues_reviews/key_issues/research_quality_framework/ ------------- Bronze release of RAE software for OA repositories The Institutional Repository and Research Assessment (IRRA) has issued the bronze release of its EPrints and DSpace RAE Software. http://irra.eprints.org/index.html http://irra.eprints.org/software/bronze/ From the site: The software to allow EPrints and DSpace institutional repositories http://archives.eprints.org/?page=all&type=&version=eprints2&country=uk http://archives.eprints.org/?page=all&type=&version=dspace&country=uk to be used for RAE 2008 is now available in Bronze release form. This means that it has been adopted internally on the test institutions and has undergone some months of testing. It is now being made avalable to the UK academic community for repository managers to gain the experience of fitting it into their Institutional RAE processes. Support for this software is provided through the IRRA mailing list in the first instance. To sign up, please add your details to the IRRA wiki. http://wiki.eprints.org/w/IRRA/TheRegister http://www.earlham.edu/~peters/fos/2006_01_22_fosblogarchive.html#113845990263743624 ----------- Harnad, S., Carr, L., Brody, T. and Oppenheim, C. (2003) Mandated online RAE CVs Linked to University Eprint Archives. Ariadne 35. http://www.ariadne.ac.uk/issue35/harnad/ From andrew.nagy at villanova.edu Mon Jan 30 16:48:44 2006 From: andrew.nagy at villanova.edu (Andrew Nagy) Date: Mon, 30 Jan 2006 16:48:44 -0500 Subject: [Dspace-general] New Installation: Collection Permissions from LDAP Message-ID: <43DE89BC.2090600@villanova.edu> Hello, we are planning to launch our DSpace installation soon to allow faculty members to add content. I was wondering if anyone could tell me how to automatically allow users who have logged in with their LDAP information to automatically have "write" level access to a collection? Thanks for the help Andrew Nagy From vrasero at db.uc3m.es Tue Jan 31 06:23:30 2006 From: vrasero at db.uc3m.es (Victoria Rasero Merino) Date: Tue, 31 Jan 2006 12:23:30 +0100 Subject: [Dspace-general] Metadata Migration Message-ID: <43DF48B2.7050008@db.uc3m.es> We have many MARC records and we'd like to migrate to our DSpace archive. Someone has experience in this? Many thanks ---------------------------------------------- Victoria Rasero Biblioteca. Gesti?n de Recursos de Informaci?n Universidad Carlos III de Madrid ---------------------------------------------- From blancoj at umich.edu Tue Jan 31 09:56:24 2006 From: blancoj at umich.edu (Jose Blanco) Date: Tue, 31 Jan 2006 09:56:24 -0500 Subject: [Dspace-general] Metadata Migration In-Reply-To: <43DF48B2.7050008@db.uc3m.es> Message-ID: <200601311456.k0VEuRt5005186@playinggod.mr.itd.umich.edu> Victoria: If I were going to do this I would do the following: 1. Convert the marc records to xml. There are tools out there to do this. 2. Write a script ( I do mine in perl ), to get the data in the format needed for the ItemImport routine using the xml files. Here is the section on doing this from the DSpace documentation: http://dspace.org/technology/system-docs/application.html#itemimporter 3. Then create a collection and run the ItemImport routine. Jose -----Original Message----- From: dspace-general-bounces at mit.edu [mailto:dspace-general-bounces at mit.edu] On Behalf Of Victoria Rasero Merino Sent: Tuesday, January 31, 2006 6:24 AM To: dspace-general at mit.edu Subject: [Dspace-general] Metadata Migration We have many MARC records and we'd like to migrate to our DSpace archive. Someone has experience in this? Many thanks ---------------------------------------------- Victoria Rasero Biblioteca. Gesti?n de Recursos de Informaci?n Universidad Carlos III de Madrid ---------------------------------------------- _______________________________________________ Dspace-general mailing list Dspace-general at mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general