From gomez@insa-lyon.fr Mon Aug 25 05:28:01 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p1/8.12.8) with ESMTP id h7P9S1k0023809 for ; Mon, 25 Aug 2003 05:28:01 -0400 (EDT) Received: from mail.insa-lyon.fr (webmail.insa-lyon.fr [134.214.79.204]) h7P9S0rv028672 for ; Mon, 25 Aug 2003 05:28:00 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.insa-lyon.fr (Postfix) with ESMTP id CF4FB4C70A for ; Mon, 25 Aug 2003 11:27:42 +0200 (CEST) Received: from pcdoc-69.insa-lyon.fr (pcdoc-44.insa-lyon.fr [134.214.81.24]) by mail.insa-lyon.fr (Postfix) with ESMTP id 654F74C704 for ; Mon, 25 Aug 2003 11:27:41 +0200 (CEST) Message-Id: <5.0.2.1.2.20030825112749.009f65e0@insa.insa-lyon.fr> X-Sender: gomez@insa.insa-lyon.fr X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Mon, 25 Aug 2003 11:29:01 +0200 To: dspace-general@mit.edu From: Rosa =?iso-8859-1?Q?Mar=EDa?= =?iso-8859-1?Q?_G=F3mez?= de Regil Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed X-Virus-Scanned: by amavisd 0.1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id h7P9S1k0023809 Subject: [Dspace-general] Metadata Question X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 25 Aug 2003 09:28:02 -0000 Hello, I'm working in metadata standards choices that experts made for educational digital repositories. I would like to know which are some reasons that motivated Dspace creators to choose Dublin Core Metadata instead of Learning Object Metadata for Dspace. Thanks Rosa María Gómez de Regil Rosa María Gómez de Regil Doc'INSA Tél. 04 72 43 87 60 E-Mail. gomez@insa-lyon.fr From kenzie@MIT.EDU Mon Aug 25 14:53:06 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p1/8.12.8) with ESMTP id h7PIr6k0029282 for ; Mon, 25 Aug 2003 14:53:06 -0400 (EDT) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72])h7PIr5vc015373; Mon, 25 Aug 2003 14:53:05 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])h7PIr4pL005773; Mon, 25 Aug 2003 14:53:04 -0400 (EDT) Received: from ADTPA.mit.edu (ADTPA.MIT.EDU [18.51.1.92]) ) h7PIr2Gs007809; Mon, 25 Aug 2003 14:53:04 -0400 (EDT) Message-Id: <5.0.2.1.2.20030825144533.037f3540@hesiod> X-Sender: kenzie@hesiod (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Mon, 25 Aug 2003 14:51:42 -0400 To: Rosa =?iso-8859-1?Q?Mar=EDa?= =?iso-8859-1?Q?_G=F3mez?= de Regil , dspace-general@MIT.EDU From: MacKenzie Smith Subject: Re: [Dspace-general] Metadata Question In-Reply-To: <5.0.2.1.2.20030825112749.009f65e0@insa.insa-lyon.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id h7PIr6k0029282 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 25 Aug 2003 18:53:06 -0000 Hi Rosa, I would say the main reason for this is that DSpace is not limited to being a learning object repository. In fact, here at MIT, and at most of the other institutions using it now, none of the content is teaching material so the LOM metadata would be completely inappropriate. Dublin Core was an obvious choice because it handles a wide range of content types, including documents (most of our current content), images, multimedia material, datasets, etc. *and* learning objects. The LOM metadata specification is what I would call a "domain specific" standard, much like MARC for library material, VRA Core for visual images, or FGDC for geospatial datasets. There is a research project here at MIT called SIMILE which is investigating the use of new technologies to support these domain specific schemas in DSpace (see http://web.mit.edu/simile/www/) but in the meantime we had to select *one* schema, and it had to be very all-purpose. I hope this helps, MacKenzie/ At 11:29 AM 8/25/2003 +0200, Rosa María Gómez de Regil wrote: >Hello, > >I'm working in metadata standards choices that experts made for >educational digital repositories. > >I would like to know which are some reasons that motivated Dspace creators >to choose Dublin Core Metadata instead of Learning Object Metadata for Dspace. > >Thanks > >Rosa María Gómez de Regil > >Rosa María Gómez de Regil >Doc'INSA >Tél. 04 72 43 87 60 >E-Mail. >gomez@insa-lyon.fr > > >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general MacKenzie Smith Associate Director for Technology MIT Libraries Building 14S-208 77 Massachusetts Avenue Cambridge, MA 02139 (617)253-8184 kenzie@mit.edu From jhwalker@MIT.EDU Tue Aug 26 16:42:04 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p1/8.12.8) with ESMTP id h7QKg4k0013046 for ; Tue, 26 Aug 2003 16:42:04 -0400 (EDT) Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82])h7QKg4M0015620; Tue, 26 Aug 2003 16:42:04 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])h7QKg3b2001695; Tue, 26 Aug 2003 16:42:03 -0400 (EDT) Received: from adtpa-v.mit.edu (ADTPA-V.MIT.EDU [18.51.1.169]) ) h7QKg2Gs006154; Tue, 26 Aug 2003 16:42:02 -0400 (EDT) Message-Id: <5.1.0.14.2.20030826104559.01e24050@hesiod> X-Sender: jharford@hesiod (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 26 Aug 2003 16:42:11 -0400 To: dspace-tech@lists.sourceforge.net, dspace-general@MIT.EDU From: Julie Harford Walker Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_28639861==_.ALT" Subject: [Dspace-general] DSpace website update X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 26 Aug 2003 20:42:05 -0000 --=====================_28639861==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Greetings, We would like to announce the launch of the DSpace Federation website and a new address for MIT's DSpace website: * www.dspace.org houses the DSpace Federation site with general information about DSpace and content and tools for sites running DSpace. * dspace.mit.edu/about is the new location for the informational site for MIT's DSpace service. Visit dspace.mit.edu to see the live MIT DSpace site. Reminder: There are three DSpace mailing lists to which you can subscribe: * DSpace General Discussion List - the DSpace Federation's new mailing list for discussion about building and running a DSpace service. It is open to all DSpace users to ask questions, share news, and spark discussion about DSpace with people managing other DSpace sites. * DSpace Announcement List - Subscribe to the DSpace Announcements list to hear about new releases of the software, and to stay informed about DSpace. This is a one-way list for announcements from DSpace project staff only, so it is a very low-traffic list. Other postings are not permitted. * DSpace Technology List - DSpace developers and system managers help answer installation questions, share information and help each other solve technical problems through the DSpace-Tech mailing list. Developers and system managers are encouraged to post questions and contribute their expertise to others working with the system. See www.dspace.org/feedback/mailing.html for subscription instructions. Thanks for your interest in DSpace, Margret Branschofsky DSpace User Support Manager, MIT Libraries Julie Walker Senior Business Strategist, MIT Libraries ==================================================== You have received this email because you have subscribed to one of the three DSpace email lists: DSpace General, DSpace Announcement or DSpace Technology. ==================================================== --=====================_28639861==_.ALT Content-Type: text/html; charset="us-ascii" Greetings,

We would like to announce the launch of the DSpace Federation website and a new address for MIT’s DSpace website: 

    *  www.dspace.org houses the DSpace Federation site with general information about DSpace and content and tools for sites running DSpace.

    * dspace.mit.edu/about is the new location for the informational site for MIT’s DSpace service.

Visit dspace.mit.edu to see the live MIT DSpace site.

Reminder:  There are three DSpace mailing lists to which you can subscribe:

   * DSpace General Discussion List - the DSpace Federation's new mailing list for discussion about building and running a DSpace service. It is open to all DSpace users to ask questions, share news, and spark discussion about DSpace with people managing other DSpace sites.

   * DSpace Announcement List - Subscribe to the DSpace Announcements list to hear about new releases of the software, and to stay informed about DSpace. This is a one-way list for announcements from DSpace project staff only, so it is a very low-traffic list. Other postings are not permitted.

   * DSpace Technology List - DSpace developers and system managers help answer installation questions, share information and help each other solve technical problems through the DSpace-Tech mailing list. Developers and system managers are encouraged to post questions and contribute their expertise to others working with the system.

See www.dspace.org/feedback/mailing.html for subscription instructions.


Thanks for your interest in DSpace,

Margret Branschofsky
DSpace User Support Manager, MIT Libraries

Julie Walker
Senior Business Strategist, MIT Libraries

====================================================
You have received this email because you have subscribed to one of the
three DSpace email lists:  DSpace General, DSpace Announcement or
DSpace Technology.
==================================================== --=====================_28639861==_.ALT-- From andrew.hankinson@acadiau.ca Wed Aug 27 13:35:46 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p1/8.12.8) with ESMTP id h7RHZjk0025441 for ; Wed, 27 Aug 2003 13:35:45 -0400 (EDT) Received: from acadiau.ca (hades.acadiau.ca [131.162.201.35]) h7RHZiON000765 for ; Wed, 27 Aug 2003 13:35:44 -0400 (EDT) Received: from acadiau.ca (debussy.acadiau.ca [131.162.130.83]) by acadiau.ca (Postfix) with ESMTP id 092758BF6BF for ; Wed, 27 Aug 2003 14:35:44 -0300 (ADT) Date: Wed, 27 Aug 2003 14:35:43 -0300 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; charset=US-ASCII; format=flowed From: Andrew Hankinson To: dspace-general@mit.edu Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: Apple Mail (2.552) Subject: [Dspace-general] Dspace 1.1 download? X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 27 Aug 2003 17:35:46 -0000 Hello all, We were wondering if the Dspace 1.1 source will be available for download on the sourceforge site sometime soon. It currently only lists the dspace 1.1.1 beta version, although the website says the new version is available. Thanks, Andrew Hankinson Acadia Institute for Teaching and Technology Acadia University From david.stuve@hp.com Wed Aug 27 13:40:20 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p1/8.12.8) with ESMTP id h7RHeHk0025572 for ; Wed, 27 Aug 2003 13:40:20 -0400 (EDT) Received: from palrel13.hp.com (palrel13.hp.com [156.153.255.238]) h7RHeGKm019223 for ; Wed, 27 Aug 2003 13:40:17 -0400 (EDT) Received: from xparelay1.ptp.hp.com (xparelay1.ptp.hp.com [15.1.28.62]) by palrel13.hp.com (Postfix) with ESMTP id A0DE71C00BDF; Wed, 27 Aug 2003 10:40:15 -0700 (PDT) Received: from xcorbh1.cv.hp.com (xcorbh1.cv.hp.com [15.7.113.189]) by xparelay1.ptp.hp.com (Postfix) with ESMTP id 715971004BA7; Wed, 27 Aug 2003 10:40:15 -0700 (PDT) Received: by xcorbh1.cv.hp.com with Internet Mail Service (5.5.2655.55) id ; Wed, 27 Aug 2003 10:40:15 -0700 Message-ID: <5755325D04C5834187459E1E17D81F6F0834EFFD@xcor01.cv.hp.com> From: "STUVE,DAVID (HP-Corvallis,ex1)" To: "'Andrew Hankinson'" , dspace-general@mit.edu Subject: RE: [Dspace-general] Dspace 1.1 download? Date: Wed, 27 Aug 2003 10:40:14 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 27 Aug 2003 17:40:20 -0000 Hi Andrew, DSpace 1.1.1 beta is the latest version available, and will be the same as our next release, probably renamed to 1.1.1 or 1.1.2 - so if you want the latest release you can install 1.1.1 now. I'm writing the release notes for it at the moment. Dave David Stuve / HP Labs Cambridge / David.Stuve@hp.com / 617-551-7632 -----Original Message----- From: Andrew Hankinson [mailto:andrew.hankinson@acadiau.ca] Sent: Wednesday, August 27, 2003 1:36 PM To: dspace-general@mit.edu Subject: [Dspace-general] Dspace 1.1 download? Hello all, We were wondering if the Dspace 1.1 source will be available for download on the sourceforge site sometime soon. It currently only lists the dspace 1.1.1 beta version, although the website says the new version is available. Thanks, Andrew Hankinson Acadia Institute for Teaching and Technology Acadia University _______________________________________________ Dspace-general mailing list Dspace-general@mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general From margretb@MIT.EDU Mon Aug 25 10:46:20 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p1/8.12.8) with ESMTP id h7PEkJk0026271 for ; Mon, 25 Aug 2003 10:46:19 -0400 (EDT) Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82])h7PEkHYs026192; Mon, 25 Aug 2003 10:46:19 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])h7PEfd4Y013933; Mon, 25 Aug 2003 10:41:39 -0400 (EDT) Received: from m10-423-1.mit.edu (DSPACE-01.MIT.EDU [18.51.2.146]) ) h7PEfbGs027450; Mon, 25 Aug 2003 10:41:38 -0400 (EDT) Message-Id: <5.1.0.14.2.20030825103843.0212abb8@po10.mit.edu> X-Sender: margretb@po10.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 25 Aug 2003 10:42:41 -0400 To: Rosa =?iso-8859-1?Q?Mar=EDa?= =?iso-8859-1?Q?_G=F3mez?= de Regil , dspace-general@MIT.EDU From: Margret Branschofsky Subject: Re: [Dspace-general] Metadata Question In-Reply-To: <5.0.2.1.2.20030825112749.009f65e0@insa.insa-lyon.fr> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_4628815==_" X-Mailman-Approved-At: Thu, 04 Sep 2003 10:27:34 -0400 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 25 Aug 2003 14:46:20 -0000 --=====================_4628815==_ Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Hi Rosa, It just so happens that we wrote a short paper on this subject last year=20 which has not yet been published. I've attached it to this message. Feel= =20 free to ask more questions after reading it. Margret Branschofsky At 11:29 AM 8/25/2003 +0200, Rosa Mar=EDa G=F3mez de Regil wrote: >Hello, > >I'm working in metadata standards choices that experts made for=20 >educational digital repositories. > >I would like to know which are some reasons that motivated Dspace creators= =20 >to choose Dublin Core Metadata instead of Learning Object Metadata for= Dspace. > >Thanks > >Rosa Mar=EDa G=F3mez de Regil > >Rosa Mar=EDa G=F3mez de Regil >Doc'INSA >T=E9l. 04 72 43 87 60 >E-Mail.=20 >gomez@insa-lyon.fr > > >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general Margret Branschofsky DSpace User Support Manager Digital Library Research Group Bldg. 14S-M24 (617)253-1293 margretb@mit.edu http://dspace.mit.edu --=====================_4628815==_ Content-Type: application/msword; name="Defining a Metadata Schema for DSpace2.doc"; x-mac-type="42494E41"; x-mac-creator="4D535744" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Defining a Metadata Schema for DSpace2.doc" 0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAOAAAAAAAAAAA EAAAOgAAAAEAAAD+////AAAAADcAAAD///////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// ///////////////////////////////////////////////////////////////////////////s pcEANyAJBAAA8BK/AAAAAAAAEAAAAAAABAAAFigAAA4AYmpialUWVRYAAAAAAAAAAAAAAAAAAAAA AAAJBBYAIjYAADd8AAA3fAAA/CMAAAAAAAAZAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD//w8AAAAA AAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAAAAAAAAAAAAGwAAAAAAHwCAAAAAAAAfAIAAHwC AAAAAAAAfAIAAAAAAAB8AgAAAAAAAHwCAAAAAAAAfAIAABQAAAAAAAAAAAAAAJACAAAAAAAAZAcA AAAAAABkBwAAAAAAAGQHAAA4AAAAnAcAAAwAAACoBwAAHAAAAJACAAAAAAAAHxEAALYAAADQBwAA AAAAANAHAAAiAAAA8gcAAAAAAADyBwAAAAAAAPIHAAAAAAAA8gcAAAAAAADyBwAAAAAAAPIHAAAA AAAAnhAAAAIAAACgEAAAAAAAAKAQAAAAAAAAoBAAAAAAAACgEAAAAAAAAKAQAAAAAAAAoBAAACQA AADVEQAAIAIAAPUTAACkAAAAxBAAABUAAAAAAAAAAAAAAAAAAAAAAAAAfAIAAAAAAADyBwAAAAAA AAAAAAAAAAAAAAAAAAAAAADyBwAAAAAAAPIHAAAAAAAA8gcAAAAAAADyBwAAAAAAAMQQAAAAAAAA 3AgAAAAAAAB8AgAAAAAAAHwCAAAAAAAA8gcAAAAAAAAAAAAAAAAAAPIHAAAAAAAA2RAAABYAAADc CAAAAAAAANwIAAAAAAAA3AgAAAAAAADyBwAAFgAAAHwCAAAAAAAA8gcAAAAAAAB8AgAAAAAAAPIH AAAAAAAAnhAAAAAAAAAAAAAAAAAAANwIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAA8gcAAAAAAACeEAAAAAAAANwIAAC0BwAA3AgAAAAAAAAAAAAA AAAAAJAQAAAAAAAAfAIAAAAAAAB8AgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAkBAAAAAAAADyBwAAAAAAAMQHAAAMAAAAMHY+qa3h wgGQAgAA1AQAAGQHAAAAAAAACAgAAF4AAACQEAAAAAAAAAAAAAAAAAAAnhAAAAAAAADvEAAAMAAA AB8RAAAAAAAAkBAAAAAAAACZFAAAAAAAAGYIAAB2AAAAmRQAAAAAAACQEAAADgAAANwIAAAAAAAA kAIAAAAAAACQAgAAAAAAAHwCAAAAAAAAfAIAAAAAAAB8AgAAAAAAAHwCAAAAAAAAAgDZAAAADQ1E ZWZpbmluZyBhIE1ldGFkYXRhIFNjaGVtYSBmb3IgRFNwYWNlDQ1CeSAgIE1hcmdyZXQgQnJhbnNj aG9mc2t5LCBSZWJlY2NhIEwuIEx1YmFzLCBQYXRzeSBCYXVkb2luLCBEYW4gQ2h1ZG5vdiwgSm9h biBLb2xpYXMsIFNhcmFoIE1pdGNoZWxsDQ0NQUJTVFJBQ1Q6IEluIDIwMDAsIE1JVCBMaWJyYXJp ZXMgbGF1bmNoZWQgdGhlIERTcGFjZSBwcm9qZWN0LiAgVGhlIG1pc3Npb24gb2YgRFNwYWNlIGlz IHRvIGNyZWF0ZSBhbmQgZXN0YWJsaXNoIGFuIGVsZWN0cm9uaWMgc3lzdGVtIHRoYXQgY2FwdHVy ZXMsIHByZXNlcnZlcyBhbmQgY29tbXVuaWNhdGVzIHRoZSBpbnRlbGxlY3R1YWwgb3V0cHV0IG9m IE1JVCdzIGZhY3VsdHkgYW5kIHJlc2VhcmNoZXJzIGFuZCB0byBzdXBwb3J0IGFkb3B0aW9uIGJ5 IGFuZCBmZWRlcmF0aW9uIHdpdGggb3RoZXIgaW5zdGl0dXRpb25zLiAgVHdvIGRpc3RpbmN0aXZl IGZlYXR1cmVzIG9mIERTcGFjZSBhcmUgdGhlIGV4cGVjdGF0aW9uIHRoYXQgYXV0aG9ycyBvciBz dWJtaXR0ZXJzIHdpbGwgcHJvdmlkZSBtZXRhZGF0YSBmb3IgZWFjaCBpdGVtIHRoZW1zZWx2ZXMs IGFuZCB0aGF0IHRoZSByZXBvc2l0b3J5IHdpbGwgYWNjb21tb2RhdGUgYSB2YXJpZXR5IG9mIGRp Z2l0YWwgdHlwZXMgYW5kIGZvcm1hdHMuICBJbiBsaWdodCBvZiB0aGVzZSBmZWF0dXJlcywgYSB0 YXNrIGZvcmNlIG9mIE1JVCBsaWJyYXJpYW5zIGNob3NlIHRoZSBEdWJsaW4gQ29yZSBNZXRhZGF0 YSBFbGVtZW50IFNldCB3aXRoIHF1YWxpZmllcnMgZm9yIERTcGFjZSBtZXRhZGF0YSwgYW5kIGJh c2VkIGl0cyBpbXBsZW1lbnRhdGlvbiB0byBhIGxhcmdlIGV4dGVudCBvbiB0aGUgTGlicmFyaWVz IEFwcGxpY2F0aW9uIFByb2ZpbGUgKExBUCkuDVRoZSBmaXJzdCBvYmplY3RzIHRvIGVudGVyIERT cGFjZSBpbmNsdWRlZCBhcHByb3hpbWF0ZWx5IDEwMCBvdXQtb2YtcHJpbnQgTUlUIFByZXNzIGJv b2tzIGluIFBERiBmb3JtYXQgYW5kIHR3byBzZXJpZXMgb2YgdGVjaG5pY2FsIHJlcG9ydHMuICBP Q0xDIGNvbnRhaW5lZCByZWNvcmRzIGZvciB0aGVzZSB0aXRsZXMuICBUaGlzIGdhdmUgdXMgdGhl IG9wcG9ydHVuaXR5IHRvIHVzZSBleGlzdGluZyBtZXRhZGF0YSBpbiB0aGUgZm9ybSBvZiB0cmFk aXRpb25hbCBNQVJDIHJlY29yZHMuICBUaGUgdGFzayBmb3JjZSB0aGVuIGZhY2VkIGNyZWF0aW5n IGJvdGggb3VyIHZlcnNpb24sIG9yIHJlZ2lzdHJ5LCBvZiAgcXVhbGlmaWVkIER1YmxpbiBDb3Jl IGFuZCBhIGNyb3Nzd2FsayBmcm9tIE1BUkMgdG8gRHVibGluIENvcmUgZm9yIHRob3NlIGRvY3Vt ZW50cyB3aXRoIGV4aXN0aW5nIE1BUkMgZGF0YS4gIFRoaXMgcGFwZXIgZGVzY3JpYmVzIHRoZSBE U3BhY2UgcHJvamVjdCwgb3VyIGRlY2lzaW9ucyByZWdhcmRpbmcgRHVibGluIENvcmUgcXVhbGlm aWVycywgYW5kIG91ciBNQVJDIHRvIERDIGNyb3Nzd2Fsay4gIA0NS2V5d29yZHM6IERTcGFjZSwg RHVibGluIENvcmUsIE1hc3NhY2h1c2V0dHMgSW5zdGl0dXRlIG9mIFRlY2hub2xvZ3ksIE1JVCwg TUFSQywgTWV0YWRhdGEsIENyb3Nzd2Fsa3MNDUludHJvZHVjdGlvbg0NRHNwYWNlIGlzIHRoZSBw cm9kdWN0IG9mIGEgam9pbnQgZGV2ZWxvcG1lbnQgcHJvamVjdCBieSBNSVQgTGlicmFyaWVzIGFu ZCB0aGUgSGV3bGV0dC1QYWNrYXJkIENvbXBhbnkgdG8gYnVpbGQgYSBzdGFibGUgYW5kIHN1c3Rh aW5hYmxlIGxvbmctdGVybSBkaWdpdGFsIHJlcG9zaXRvcnkgdGhhdCBjYXB0dXJlcywgcHJlc2Vy dmVzIGFuZCBkaXNzZW1pbmF0ZXMgdGhlIHJlc2VhcmNoIGdlbmVyYXRlZCBhY3Jvc3MgdGhlIHNw ZWN0cnVtIG9mIGRpc2NpcGxpbmVzIGF0IE1JVC4gIEJ5IHByb3ZpZGluZyBhIHN1c3RhaW5hYmxl IHJlY29yZCBvZiB0aGUgZGlnaXRhbCBvdXRwdXQgb2YgTUlUIGZhY3VsdHkgYW5kIHJlc2VhcmNo ZXJzIGluIGFuIGluY3JlYXNpbmdseSBtdWx0aW1lZGlhIGFjYWRlbWljIGVudmlyb25tZW50LCBE U3BhY2Ugd2lsbCBtZWV0IGEgZ3Jvd2luZyBpbnN0aXR1dGlvbmFsIG5lZWQuICBBZnRlciBjb21w bGV0aW5nIGEgYmV0YS10ZXN0aW5nIHBoYXNlIG92ZXIgdGhlIFNwcmluZyBhbmQgU3VtbWVyIG9m IDIwMDIsIERTcGFjZSB3aWxsIG9mZmljaWFsbHkgYmUgbGF1bmNoZWQgYXQgTUlUIGluIHRoZSBG YWxsIG9mIDIwMDIuICBTb29uIHRoZXJlYWZ0ZXIgTUlUIExpYnJhcmllcyB3aWxsIGV4dGVuZCB0 aGUgc2NvcGUgb2YgRFNwYWNlIGJ5IGludml0aW5nIG90aGVyIHJlc2VhcmNoIGluc3RpdHV0aW9u cyB0byBpbXBsZW1lbnQgdGhlIERTcGFjZSBzb2Z0d2FyZSwgd2hpY2ggd2lsbCBldmVudHVhbGx5 IGJlIHJlbGVhc2VkIGFzIG9wZW4gc291cmNlLg0NVGhlIE11bHRpZGlzY2lwbGluYXJ5IE5hdHVy ZSBvZiBEU3BhY2UNDUluIGRlY2lkaW5nIHVwb24gc2NoZW1hcyBmb3IgdXNlIHdpdGggRFNwYWNl IGl0IHdhcyBpbXBvcnRhbnQgdG8gY29uc2lkZXIgdGhlIHR5cGUgb2YgY29udGVudCBEU3BhY2Ug IGV4cGVjdGVkIHRvIHJlY2VpdmUgYW5kIHByb2Nlc3MsIGJvdGggaW1tZWRpYXRlbHkgYW5kIGlu IHRoZSBmdXR1cmUuIFNpbmNlIERTcGFjZSBpcyBhbiBpbnN0aXR1dGlvbmFsIHJlcG9zaXRvcnks IGl0IHdpbGwgaGF2ZSB0byBhY2NvbW1vZGF0ZSB0aGUgbWFueSBkaXNjaXBsaW5lcyByZXByZXNl bnRpbmcgYWxsIHRoZSBzY2hvb2xzLCBkZXBhcnRtZW50cywgbGFicyBhbmQgY2VudGVycyBhdCBN SVQuIEluIGFkZGl0aW9uLCBEU3BhY2UgaGFzIGNvbW1pdHRlZCBpdHNlbGYgdG8gaGFuZGxpbmcg bWFueSB0eXBlcyBvZiBkaWdpdGFsIGZvcm1hdHMsIGluY2x1ZGluZyB0ZXh0LCBkYXRhLCBpbWFn ZSBhdWRpbywgdmlkZW8gYW5kIHdlYnNpdGVzLiBJbiBzdWNoIGEgaGV0ZXJvZ2VuZW91cyBlbnZp cm9ubWVudCwgaXQgaXMgdW5saWtlbHkgdGhhdCBvbmUgcGFydGljdWxhciBkZXNjcmlwdGl2ZSBt ZXRhZGF0YSBzY2hlbWEgd2lsbCBmaXQgYWxsIERTcGFjZSBjb250ZW50LiBJdCBpcyBhbHNvIGlt cG9zc2libGUgdG8gZm9yZWNhc3QgZXhhY3RseSB3aGljaCB0eXBlcyBvZiBjb250ZW50IHdpbGwg YmVjb21lIHByb21pbmVudCBpbiB0aGUgZnV0dXJlLiBDb21tdW5pdGllcyB0aGF0IGNvbGxlY3Qg b3IgcHJvZHVjZSBkaWZmZXJlbnQgdHlwZXMgb2YgaW5mb3JtYXRpb24gb2JqZWN0cyBoYXZlIHVz ZWQgZGlmZmVyZW50IG1ldGFkYXRhIHNjaGVtYXMgdG8gc2VydmUgdGhlaXIgb3duIG5lZWRzLiAN DUFzIHdlIGhhdmUgYXBwcm9hY2hlZCBwb3RlbnRpYWwgY29udHJpYnV0b3JzIHRvIERTcGFjZSwg d2UgaGF2ZSBub3RlZCB0aGUgZGlmZmVyZW50IHR5cGVzIG9mIG1ldGFkYXRhIHNjaGVtYXMgdXNl ZCBieSBkaWZmZXJlbnQgY29tbXVuaXRpZXMsIGFuZCB3aGF0IGRhdGEgZm9ybWF0cyBoYXZlIHBy b21wdGVkIHRoZW0gdG8gdXNlIHRoZW0uIFdlIGFsc28gbm90ZWQgd2hlcmUgbWV0YWRhdGEgcmVj b3JkcyBhbHJlYWR5IGV4aXN0IGZvciBzcGVjaWZpYyBjb2xsZWN0aW9ucy4gV2UgZGlzY292ZXJl ZCB0aGF0IER1YmxpbiBDb3JlIHdhcyB1c2VkIGZvciBzb21lIG9mIHRoZSB0ZXh0IGZpbGVzLCB0 aGUgRkdEQyBzY2hlbWEgZm9yIGdlb3NwYXRpYWwgZGF0YSBmaWxlcywgTUFSQyByZWNvcmRzIGZv ciBzY2FubmVkIG9iamVjdHMgYWxyZWFkeSBpbiB0aGUgTUlUIExpYnJhcmllcyBjYXRhbG9nLCBh bmQgVlJBIGZvciBzb21lIGRpZ2l0YWwgaW1hZ2VzLg0NSW5kaXZpZHVhbCBTdWJtaXNzaW9ucw0N SXQgaXMgZXhwZWN0ZWQgdGhhdCB0aGUgYnVsayBvZiByZWd1bGFyIGFuZCBvbmdvaW5nIHN1Ym1p c3Npb25zIHRvIERTcGFjZSB3aWxsIGJlIGRvbmUgb24gYW4gaW5kaXZpZHVhbCBiYXNpcywgYnkg dGhlIGNyZWF0b3Igb2YgdGhlIGNvbnRlbnQgb2JqZWN0IG9yIGJ5IGFuIGFkbWluaXN0cmF0aXZl IHN0YWZmIG1lbWJlciBvZiB0aGUgY29tbXVuaXR5LiBEdXJpbmcgdGhlIHN1Ym1pc3Npb24gcHJv Y2VzcyBlYWNoIHN1Ym1pdHRlciB3aWxsIGJlIGV4cGVjdGVkIHRvIGZpbGwgb3V0IGEgbWV0YWRh dGEgZm9ybSBwcm92aWRpbmcgYXQgbGVhc3QgbWluaW1hbCBpbmZvcm1hdGlvbiBkZXNjcmliaW5n IHRoZSBzdWJtaXR0ZWQgZG9jdW1lbnQuIFRoZSBEU3BhY2UgbWV0YWRhdGEgc2NoZW1hIHdvdWxk IGhhdmUgdG8gYmUgc2ltcGxlIGVub3VnaCBmb3Igbm9uLWNhdGFsb2dlcnMgdG8gdXNlLCB5ZXQg Y29tcHJlaGVuc2l2ZSBlbm91Z2ggdG8gY2FwdHVyZSB0aGUgaW5mb3JtYXRpb24gZWxlbWVudHMg bmVlZGVkIHRvIGVuYWJsZSBhZGVxdWF0ZSByZXRyaWV2YWwuIE1ldGFkYXRhIGlucHV0IHRlbXBs YXRlcyB3b3VsZCBoYXZlIHRvIGJlIGVhc3kgdG8gdXNlIGFuZCBub3QgdG9vIGxlbmd0aHksIHNv IHRoYXQgcG90ZW50aWFsIGNvbnRyaWJ1dG9ycyB0byBEU3BhY2Ugd291bGQgbm90IGJlIHB1dCBv ZmYgYnkgdGhlIHN1Ym1pc3Npb24gcHJvY2Vzcy4gDQ1CYXRjaCBTdWJtaXNzaW9ucw0NU2V2ZXJh bCBvZiBvdXIgZWFybHkgYmV0YS10ZXN0ZXJzIGJhdGNoZXMgb2YgZWxlY3Ryb25pYyBpdGVtcyBj b252ZXJ0ZWQgZnJvbSBwcmludCB0byBlbGVjdHJvbmljIGZvcm0uIFRoZSBmaXJzdCBzdWJzdGFu dGlhbCBiYXRjaCBvZiBEU3BhY2UgY29udGVudCB3YXMgYSBjb2xsZWN0aW9uIG9mIFBERiBpbWFn ZXMgb2YgTUlUIFByZXNzIG91dC1vZi1wcmludCBib29rcy4gU3Vic2VxdWVudCBiYXRjaGVzIG9m IHN1Ym1pc3Npb25zIHRvIERTcGFjZSB3aWxsIGNvbnNpc3Qgb2YgY29sbGVjdGlvbnMgb2Ygc2Nh bm5lZCBQREYgaW1hZ2VzIG9mIHByaW50IHRlY2huaWNhbCByZXBvcnRzIGFuZCB3b3JraW5nIHBh cGVyIHNlcmllcyBmcm9tIHZhcmlvdXMgbGFicywgY2VudGVycyBhbmQgc2Nob29scyBvbiBjYW1w dXMuICBXZSB3aWxsIGhhdmUgYWNjZXNzIHRvIHRoZSBNQVJDIGZvcm1hdCBtZXRhZGF0YSByZWNv cmRzIGZvciB0aGVzZSBpdGVtcyBpbiB0aGUgTUlUIExpYnJhcmllcyBjYXRhbG9nLg0NRXhpc3Rp bmcgRGVzY3JpcHRpdmUgTWV0YWRhdGEgU2NoZW1hIGNvbnNpZGVyZWQgZm9yIERTcGFjZQ0NVGhl IER1YmxpbiBDb3JlIG1ldGFkYXRhIHNjaGVtYSAoREMpIHdhcyBkZXZlbG9wZWQgZXNwZWNpYWxs eSBmb3IgZWxlY3Ryb25pYyBpbmZvcm1hdGlvbiBvYmplY3RzIHRvIHByb3ZpZGUgYSBzaW1wbGUg bWV0YWRhdGEgc2NoZW1hIHRoYXQgd291bGQgYmUgZmxleGlibGUgZW5vdWdoIHRvIGFjY29tbW9k YXRlIGEgdmFyaWV0eSBvZiBmb3JtYXRzLiBBY2NvbXBhbmllZCBieSB3ZWxsLWRlc2lnbmVkIHRl bXBsYXRlcyBmb3IgbWV0YWRhdGEgaW5wdXQsIHRoZSBEdWJsaW4gQ29yZSBzY2hlbWEgaGFzIHRo ZSBwb3RlbnRpYWwgdG8gZWxpY2l0IGVub3VnaCBpbmZvcm1hdGlvbiB0byBwcm92aWRlIGFtcGxl IHNlYXJjaGluZyBhbmQgaWRlbnRpZmljYXRpb24gY2FwYWJpbGl0aWVzIGZvciBEU3BhY2UuIEl0 cyBkaXNhZHZhbnRhZ2UgaXMgdGhhdCBpdCBkb2VzIG5vdCBwcm92aWRlIHRoZSBmaW5lLWdyYWlu ZWQgdGFyZ2V0ZWQgZmllbGRlZCBzZWFyY2ggY2FwYWJpbGl0aWVzIHRoYXQgc29tZSBjb21tdW5p dGllcyBwcm9kdWNpbmcgc3BlY2lhbGl6ZWQgZGF0YSBvYmplY3RzIG1heSByZXF1aXJlLiANDU1B UkMgcmVjb3Jkcywgb24gdGhlIG90aGVyIGhhbmQsIGRvIHByb3ZpZGUgbW9yZSBmaW5lLWdyYWlu ZWQgZGF0YSBkZXNjcmlwdGlvbiBhbmQgc2VhcmNoaW5nIHBvc3NpYmlsaXRpZXMuICBIb3dldmVy LCBNQVJDIHJlY29yZHMgYXJlIGNyZWF0ZWQgYnkgcHJvZmVzc2lvbmFsIGxpYnJhcnkgY2F0YWxv Z2VycyB3aG8gZm9sbG93IGEgc3RyaW5nZW50IHNldCBvZiBydWxlcywgdGhlIEFuZ2xvLUFtZXJp Y2FuIENhdGFsb2dpbmcgUnVsZXMuIEl0IHdvdWxkIGJlIG91dCBvZiB0aGUgcXVlc3Rpb24gdG8g YXNrIERTcGFjZSBjb250cmlidXRvcnMgdG8gc3VibWl0IG1ldGFkYXRhIG9mIHRoaXMgY29tcGxl eGl0eSwgc2luY2UgdGhlIGJ1bGsgb2YgRFNwYWNlIGNvbnRlbnQgd2lsbCBub3QgYmUgaW5wdXQg YnkgcHJvZmVzc2lvbmFsIGNhdGFsb2dlcnMsIGJ1dCByYXRoZXIgYnkgdGhlIGF1dGhvcnMgYW5k IHN1Ym1pdHRlcnMgb2YgY29udGVudC4NDVdlIGFsc28gZGVjaWRlZCB0byB1c2UgYW4gZXhpc3Rp bmcgb3BlbiBzb3VyY2Ugc2VhcmNoIGVuZ2luZSBmb3IgRFNwYWNlIHJhdGhlciB0aGFuIGNyZWF0 ZSBhIHRvb2wgZGVzaWduZWQgdG8gaW50ZXJwcmV0IGFsbCB0aGUgbnVhbmNlcyBvZiB0aGUgTUFS QyByZWNvcmQuICBTaW5jZSBNQVJDIHJlY29yZHMgYWxyZWFkeSBleGlzdCBmb3Igc2V2ZXJhbCBE U3BhY2UgY29sbGVjdGlvbnMsIGl0IG1hZGUgc2Vuc2UgdG8gc2VsZWN0IGEgc2NoZW1hIHRoYXQg Y291bGQgZWFzaWx5IGFjY2VwdCBtYXBwaW5ncyBmcm9tIE1BUkMuICAgDQ1Db252ZXJzaW9uIG9m IE1BUkMgdG8gRHVibGluIENvcmUNDVRvIHByZXBhcmUgZm9yIHRoZSBpbmdlc3Rpb24gb2YgdGhl IG1ldGFkYXRhIHJlY29yZHMgYWxyZWFkeSBleGlzdGluZyBpbiBNQVJDIGZvcm1hdCwgd2UgcmFu IHNldmVyYWwgc2FtcGxlIE1BUkMgcmVjb3JkcyB0aHJvdWdoIHRoZSBDT1JDIHN5c3RlbSwgd2hp Y2ggY29udmVydHMgTUFSQyB0byAicXVhbGlmaWVkIiBEdWJsaW4gQ29yZSBvbiBhIG9uZSByZWNv cmQgYXQgYSB0aW1lIGJhc2lzLiBXZSBhbHNvIHJhbiBzb21lIG9mIHRoZSBNQVJDIHJlY29yZHMg dGhyb3VnaCBhbiBleGlzdGluZyBiYXRjaCBjb252ZXJzaW9uIHRvb2wgZGV2ZWxvcGVkIGJ5IEpl ZmYgWW91bmcgYXQgT0NMQyB0aGF0IGNvbnZlcnRlZCB0aGVtIHRvICJ1bnF1YWxpZmllZCIgRHVi bGluIENvcmUgcmVjb3Jkcy4gV2UgIGV4YW1pbmVkIHNldmVyYWwgaW1wbGVtZW50YXRpb25zIG9m IHRoZSBEdWJsaW4gQ29yZSBzY2hlbWEgYXMgd2VsbCBhcyB0aGUgTGlicmFyeSBvZiBDb25ncmVz cw0iTUFSQyB0byBEdWJsaW4gQ29yZSBDcm9zc3dhbGsiIGRldmVsb3BlZCBieSB0aGUgTGlicmFy eSBvZiBDb25ncmVzcy4gDQ1XZSBjb25jbHVkZWQgdGhhdCBub25lIG9mIHRoZXNlIGNvbnZlcnNp b24gcHJvY2Vzc2VzIGFyZSBsb3NzLWxlc3MsIGJ1dCBzb21lIGxvc3NlcyBvdXR3ZWlnaGVkIG90 aGVycy4gU29tZSBiaXRzIG9mIGluZm9ybWF0aW9uIGFyZSBsb3N0IGluIHRoZSBjb252ZXJzaW9u IGZyb20gTUFSQyB0byBEQy4gT2YgcHJpbWFyeSBjb25jZXJuIGlzIHRoZSBsb3NzIG9mIGluZm9y bWF0aW9uIHJlbGF0aW5nIHRvICJ3b3JrIGRvbmUgdW5kZXIgY29udHJhY3QgdG8iIGNvbnRhaW5l ZCBpbiB0aGUgNTM2IE1BUkMgZmllbGQsIHdoaWNoIGlzIGN1c3RvbWFyaWx5IGVudGVyZWQgZm9y IE1JVCB0ZWNobmljYWwgcmVwb3J0cy4gU2ltaWxhciBsb2NhbCBjYXRhbG9naW5nIGluZm9ybWF0 aW9uIHdpbGwgYWxzbyBiZSBjb250YWluZWQgaW4gdGhlIE1JVCBkaWdpdGFsIHRoZXNlcyByZWNv cmRzLCB3aGljaCB3aWxsIGV2ZW50dWFsbHkgYmUgaW5jb3Jwb3JhdGVkIGludG8gRFNwYWNlLg0N UXVhbGlmaWVkIHZzLiBVbnF1YWxpZmllZCBEdWJsaW4gQ29yZQ0NVGhlIHRhc2sgZm9yY2Ugc3Bl bnQgc29tZSB0aW1lIGV2YWx1YXRpbmcgdGhlIHJlc3VsdHMgb2YgYSBiYXRjaCBjb252ZXJzaW9u IGZyb20gTUFSQyB0byB1bnF1YWxpZmllZCBEdWJsaW4gQ29yZSB1c2luZyBhIHRvb2wgZGV2ZWxv cGVkIGJ5IGEgRFNwYWNlIHByb2dyYW1tZXIuIEFsdGhvdWdoIHRoaXMgd291bGQgcHJvdmlkZSB1 cyB3aXRoIGEgcXVpY2sgbWV0aG9kIG9mIGNvbnZlcnRpbmcgbGFyZ2UgYW1vdW50cyBvZiBNQVJD IHJlY29yZHMgaW50byBEQywgd2Ugd2VyZSBub3Qgc2F0aXNmaWVkIHdpdGggdGhlIHJlY29yZHMg cHJvZHVjZWQgYnkgdGhpcyB0b29sLiBXZSB3b3VsZCBoYXZlIGxvc3Qgc29tZSBncmFudWxhcml0 eSBieSBub3QgYmVpbmcgYWJsZSB0byBzcGVjaWZ5IGNhdGVnb3JpZXMgb2YgImNyZWF0b3IiLCBm b3IgaW5zdGFuY2UsIG9yIHNwZWNpZnkgdGhlIHRoZXNhdXJ1cyBzb3VyY2Ugb2Ygc3ViamVjdCB0 ZXJtcy4gU29tZSB1c2VycyBtaWdodCB3YW50IHRvIGxpbWl0IGEgc2VhcmNoIHRvIG9ubHkgdGhl ICJwaG90b2dyYXBoZXIiIHF1YWxpZmljYXRpb24gY2F0ZWdvcnkgb2YgdGhlICJjcmVhdG9yIiBl bGVtZW50LCBmb3IgaW5zdGFuY2UsIG9yIHdlIG1pZ2h0IHdhbnQgdG8gaW1wbGVtZW50IGEgc3Vi amVjdCBicm93c2UgYmFzZWQgb24gdGhlIEFtZXJpY2FuIE1hdGhlbWF0aWNhbCBTb2NpZXR5IG51 bWVyaWMgY2xhc3MgY29kZXMuICBXZSBhbHNvIG5lZWRlZCB0byBzcGVjaWZ5IGRpZmZlcmVudCBr aW5kcyBvZiBkYXRlcy4gV2UgZmVsdCB0aGF0IHdlIG5lZWRlZCBhIGhpZ2hlciBsZXZlbCBvZiBz cGVjaWZpY2l0eSB0aGFuIHRoZSBzaW1wbGUgREMgY291bGQgb2ZmZXIsIGJvdGggZm9yIGNvbnZl cnNpb25zIG9mIGV4aXN0aW5nIE1BUkMgcmVjb3JkcyBhbmQgZm9yIERTcGFjZSBhcyBhIHdob2xl LiANDU91ciBkZWxpYmVyYXRpb25zIGNvaW5jaWRlZCB3aXRoIHRoZSBBdWd1c3QgMjAwMSBEdWJs aW4gQ29yZSBMaWJyYXJpZXMgV29ya2luZyBHcm91cCBBcHBsaWNhdGlvbiBQcm9maWxlIHJlbGVh c2UgZm9yIHB1YmxpYyBjb21tZW50LiAgVWx0aW1hdGVseSwgd2UgdXNlZCB0aGUgTEFQIGFzIGEg c3RhcnRpbmcgcG9pbnQgZm9yIG91ciBvd24gYXBwbGljYXRpb24gb2YgREMsIGJvcnJvd2luZyBt b3N0IG9mIHRoZSBxdWFsaWZpZXJzIGZyb20gaXQgYW5kIGFkYXB0aW5nIG90aGVycyB0byBmaXQu ICBXZSBhbHNvIGFkZGVkIHNvbWUgcXVhbGlmaWVycyB0byBzdWl0IERTcGFjZSBuZWVkcy4gIEF0 IHRoZSBzYW1lIHRpbWUgd2UgY3JlYXRlZCBhIE1BUkMgdG8gREMgY3Jvc3N3YWxrIHRoYXQgb3Vy IHByb2dyYW1tZXIgdXNlZCB0byBkZXZlbG9wIGEgdG9vbCBmb3IgYnJpbmdpbmcgYmF0Y2hlcyBv ZiBNQVJDIHJlY29yZHMgaW50byB0aGUgRFNwYWNlIGRhdGFiYXNlLiAgDQ1bRFNwYWNlIGlzIGlu IHRoZSBtaWRzdCBvZiBiZXRhLXRlc3RpbmcsIGJvdGggdGhlIHN5c3RlbSBhbmQgdGhlIGNyb3Nz d2Fsay4gIEFzIHNvb24gYXMgd2UgaGF2ZSBjb21wbGV0ZWQgdGVzdGluZyB3ZSB3aWxsIGFwcGVu ZCBib3RoIG91ciBzY2hlbWEgYW5kIHRoZSBjcm9zc3dhbGsuICBUaGlzIHdpbGwgaGFwcGVuIHdl bGwgYmVmb3JlIHRoZSBjb25mZXJlbmNlIGRhdGUuXQ0TUEFHRSAgFQ0NDRNQQUdFICAUMxUNDQ0N DQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAACQBAAAmAQAAJoEAAB2BwAAuwkA ADAKAABADQAAQg0AAGkNAACcEgAAnRIAALQSAAC1EgAAgBUAAIEVAACTFQAAlRcAANAXAAAfHQAA QR0AAGchAACNIQAAIycAACQnAAD8JwAA/ScAAAMoAAAEKAAABSgAAAcoAAAIKAAADigAAA8oAAAQ KAAAESgAABIoAAAVKAAAFigAAAD8APf0APQA7fQA7fT39O307fTt9O30APTm4+bjAObj5tvm4wD0 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAA8wShEAbUgABG5IAAR1CAEEMEoRAAANA2oAAAAAMEoRAFUIAQ01CIE+ KgBDShYAXAiBBENKFAAACE9KAABRSgAAAAY1CIFcCIEmAAQAAAEEAAACBAAAKAQAACkEAACOBAAA jwQAAJAEAAB2BwAAugkAALsJAAAhCgAAIgoAAC8KAAAwCgAAQQ0AAEINAABpDQAAag0AALQQAAC1 EAAAnBIAAJ0SAAC0EgAAtRIAAIAVAACBFQAA+gAAAAAAAAAAAAAAAPoAAAAAAAAAAAAAAAD4AAAA AAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAA AAAAAPQAAAAAAAAAAAAAAADuAAAAAAAAAAAAAAAA7gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2 AAAAAAAAAAAAAAAA7AAAAAAAAAAAAAAAAPYAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAA AAAAAAAAAOoAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAPYAAAAAAAAAAAAA AAD2AAAAAAAAAAAAAAAA9gAAAAAAAAAAAAAAAOoAAAAAAAAAAAAAAAD2AAAAAAAAAAAAAAAA5AAA AAAAAAAAAAAAAPYAAAAAAAAAAAAAAAAAAAAAAAAAAAAABg8ANyQBOCQBSCQBAAEEAAABBQAABQAA EYTQAmCE0AIAAQ8AAAEAAAABAgAABAAAAyQBYSQBABoABAAA/CcAABUoAAD+/gAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgEBAoEVAACTFQAAlBUAAJQXAACVFwAA0BcAANEX AAALGgAADBoAAO4bAADvGwAAHh0AAB8dAABBHQAAQh0AAC8fAAB2HwAAdx8AAGYhAABnIQAAjSEA AI4hAAAzJQAANCUAACMnAAAkJwAA/CcAAAUoAAAGKAAA/QAAAAAAAAAAAAAAAPsAAAAAAAAAAAAA AAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAA AAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAA AAAAAAD7AAAAAAAAAAAAAAAA/QAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA +wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAP0AAAAA AAAAAAAAAAD7AAAAAAAAAAAAAAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAAD7AAAAAAAAAAAA AAAA+wAAAAAAAAAAAAAAAPsAAAAAAAAAAAAAAADyAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAAAB EAAACBAAGIT8/xmEAQAbJmAjJAIAAQAAAAEEAAAcBigAAAcoAAASKAAAEygAABQoAAAVKAAAFigA AP0AAAAAAAAAAAAAAAD0AAAAAAAAAAAAAAAA8gAAAAAAAAAAAAAAAP0AAAAAAAAAAAAAAAD9AAAA AAAAAAAAAAAA/QAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAABEAAACBAAGIT8/xmEAQAbJmAjJAIAAQAAAAYgADGQaAEfsNAvILDgPSGwCAcisAgHI5CgBSSQ oAUlsAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABQAEgAKAAEAaQAPAAMAAAAAAAAAAAA4AABA8f8C ADgADAAGAE4AbwByAG0AYQBsAAAAAgAAABgAQ0oYAF9IAQRhShgAbUgJBHNICQR0SAkESgABAAEA EgBKAAwACQBIAGUAYQBkAGkAbgBnACAAMQAAABMAAQATpGQAFKRkAEAmAFskAVwkAQASADUIgUNK MABLSCQAXAiBYUowADwAAkABAAIAPAAMAAkASABlAGEAZABpAG4AZwAgADIAAAAOAAIAAyQBBiQB QCYBYSQBCgA1CIFDShwAXAiBRgADAAEAMgBGAAwACQBIAGUAYQBkAGkAbgBnACAAMwAAABMAAwAT pGQAFKRkAEAmAlskAVwkAQAOADUIgUNKGwBcCIFhShsAMAAEQAEAAgAwAAwACQBIAGUAYQBkAGkA bgBnACAANAAAAAgABAAGJAFAJgMDAD4qAQA4AAVAAQACADgADAAJAEgAZQBhAGQAaQBuAGcAIAA1 AAAACAAFAAYkAUAmBAsAPioBQ0oWAF5KAgAAAAAAAAAAAAA8AEFA8v+hADwADAAWAEQAZQBmAGEA dQBsAHQAIABQAGEAcgBhAGcAcgBhAHAAaAAgAEYAbwBuAHQAAAAAAAAAAAAAAAAASAD+T/H/8gBI AAwACQBIAFQATQBMACAAQgBvAGQAeQAAAAsADwA3JAA4JABIJAAAGABPSgIAUUoCAF9IAQRtSAkE c0gJBHRICQQsACBAAQACASwADAAGAEYAbwBvAHQAZQByAAAADQAQAA3GCAAC4BDAIQECAAAAJgAp QKIAEQEmAAwACwBQAGEAZwBlACAATgB1AG0AYgBlAHIAAAAAAAAAAAAWJAAAAwAANgAAAAD///// AAAAAAEAAAACAAAAKAAAACkAAACOAAAAjwAAAJAAAAB2AwAAugUAALsFAAAhBgAAIgYAAC8GAAAw BgAAQQkAAEIJAABpCQAAagkAALQMAAC1DAAAnA4AAJ0OAAC0DgAAtQ4AAIARAACBEQAAkxEAAJQR AACUEwAAlRMAANATAADREwAACxYAAAwWAADuFwAA7xcAAB4ZAAAfGQAAQRkAAEIZAAAvGwAAdhsA AHcbAABmHQAAZx0AAI0dAACOHQAAMyEAADQhAAAjIwAAJCMAAPwjAAAHJAAAEiQAABMkAAAXJAAA mAAAAAAwAAAAAAAAAIAAAACAmAAAAAAwAAAAAAAAAIAAAACAGAAAAAIwAAAAAAAAAIAAAACAmAAA AAAwAAAAAAAAAIACAAAAmAAAAAAwAAAAAAAAAIACAAAAmAAAAAAwAAAAAAAAAIACAAAAmAAAAAAw AAAAAAAAAIACAAAAmAAAAA8wAAAAAAAAAIACAAAAmAAAAAAwAAAAAAAAAIACAAAAmAAAAAAwAAAA AAAAAIACAAAAmAAAAAAwAAAAAAAAAIAAAACAmAAAAAAwAAAAAAAAAIAAAACASAAAAAUwAAAAAAAA AIAAAACAmAAAAAAwAAAAAAAAAIAiBgAAmAAAAAAwAAAAAAAAAIAiBgAAmAAAAAAwAAAAAAAAAIAi BgAAOAAAAAQwAAAAAAAAAIACAAAAmAAAAAAwAAAAAAAAAIBCCQAAmAAAAAAwAAAAAAAAAIAAAACA mAAAAAAwAAAAAAAAAIBCCQAAmAAAAAAwAAAAAAAAAIBCCQAAmAAAAAAwAAAAAAAAAIBCCQAAOAAA AAQwAAAAAAAAAIACAAAAmAAAAAAwAAAAAAAAAICZDgAAmAAAAA8wAAAAAAAAAICZDgAAmAAAAAAw AAAAAAAAAICZDgAAOAAAAAQwAAAAAAAAAIACAAAAmAAAAAAwAAAAAAAAAIB9EQAAmAAAAAAwAAAA AAAAAIAAAACAmAAAAAAwAAAAAAAAAIB9EQAAOAAAAAQwAAAAAAAAAIACAAAAmAAAAAAwAAAAAAAA AICiEwAAmAAAAAAwAAAAAAAAAICiEwAAmAAAAAAwAAAAAAAAAICiEwAAmAAAAAAwAAAAAAAAAICi EwAAmAAAAAAwAAAAAAAAAICiEwAAmAAAAAAwAAAAAAAAAIAAAACAmAAAAAAwAAAAAAAAAICiEwAA OAAAAAQwAAAAAAAAAIACAAAAmAAAAAAwAAAAAAAAAIBPGQAAmAAAAAAwAAAAAAAAAIAAAACAmAAA AAAwAAAAAAAAAIBPGQAAmAAAAAAwAAAAAAAAAIBPGQAAmAAAAAAwAAAAAAAAAIAAAACAmAAAAAAw AAAAAAAAAIBPGQAAOAAAAAQwAAAAAAAAAIAAAACAmAAAAAAwAAAAAAAAAIDFHgAAmAAAAAAwAAAA AAAAAIAAAACAmAAAAAAwAAAAAAAAAIDFHgAAmAAAAAAwAAAAAAAAAIAAAACAmAAAAAAwAAAAAAAA AIDFHgAAmAAAAAAwAAAAAAAAAIAAAACAmkAAAAAwAAAAAAAAAIAAAACAmkAAABAwAAAAAAAAAIAA AACAmEAAABAwAAAAAAAAAIAAAACACgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAACwAAABgAAAAYAAAAGAAAABsAAAAABAAAFigAABYAAAAABAAAgRUA AAYoAAAWKAAAFwAAABkAAAAaAAAAAAQAABUoAAAYAAAAAAAAAAcAAAALAAAAEgAAABQAAAAbAAAA EyGVABMh9P+VgAAAAAD8IwAAFCQAABckAAAHAAcAAgAAAAAAFgYAACAGAABYDQAAXA0AAM0aAADZ GgAAlRwAAJocAACgIgAApiIAAD8jAABLIwAA/CMAABQkAAAXJAAABwAzAAcAMwAHADMABwAzAAcA MwAHADMABwAHAAIAAAAAACAGAAAhBgAALgYAAC4GAACoDAAArAwAAKkRAAC1EQAA8h8AAPIfAACp IQAAsCEAACQjAAD7IwAA/CMAAAQkAAAHJAAAESQAABckAAADAAQAAwAEAAMABAADAAQAAwAEAAMA BAADAAQAAgAHAAIABwACAP//FAAAABAAUgBlAGIAZQBjAGMAYQAgAEwALgAgAEwAdQBiAGEAcwB0 AEMAOgBcAFcASQBOAE4AVABcAFAAcgBvAGYAaQBsAGUAcwBcAHIAbABsAFwAQQBwAHAAbABpAGMA YQB0AGkAbwBuACAARABhAHQAYQBcAE0AaQBjAHIAbwBzAG8AZgB0AFwAVwBvAHIAZABcAEEAdQB0 AG8AUgBlAGMAbwB2AGUAcgB5ACAAcwBhAHYAZQAgAG8AZgAgAEQAZQBmAGkAbgBpAG4AZwAgAGEA IABNAGUAdABhAGQAYQB0AGEAIABTAGMAaABlAG0AYQAgAGYAbwByACAARABTAHAAYQBjAGUALgBh AHMAZAAQAFIAZQBiAGUAYwBjAGEAIABMAC4AIABMAHUAYgBhAHMASQBDADoAXAB3AG8AcgBkAGQA bwBjAHMAXABQAGUAcgBzAG8AbgBhAGwAXABBAEwAQQBPAEwAQQBDAHAAdQBiAFwARABlAGYAaQBu AGkAbgBnACAAYQAgAE0AZQB0AGEAZABhAHQAYQAgAFMAYwBoAGUAbQBhACAAZgBvAHIAIABEAFMA cABhAGMAZQAuAGQAbwBjABAAUgBlAGIAZQBjAGMAYQAgAEwALgAgAEwAdQBiAGEAcwBJAEMAOgBc AHcAbwByAGQAZABvAGMAcwBcAFAAZQByAHMAbwBuAGEAbABcAEEATABBAE8ATABBAEMAcAB1AGIA XABEAGUAZgBpAG4AaQBuAGcAIABhACAATQBlAHQAYQBkAGEAdABhACAAUwBjAGgAZQBtAGEAIABm AG8AcgAgAEQAUwBwAGEAYwBlAC4AZABvAGMAEABSAGUAYgBlAGMAYwBhACAATAAuACAATAB1AGIA YQBzAHQAQwA6AFwAVwBJAE4ATgBUAFwAUAByAG8AZgBpAGwAZQBzAFwAcgBsAGwAXABBAHAAcABs AGkAYwBhAHQAaQBvAG4AIABEAGEAdABhAFwATQBpAGMAcgBvAHMAbwBmAHQAXABXAG8AcgBkAFwA QQB1AHQAbwBSAGUAYwBvAHYAZQByAHkAIABzAGEAdgBlACAAbwBmACAARABlAGYAaQBuAGkAbgBn ACAAYQAgAE0AZQB0AGEAZABhAHQAYQAgAFMAYwBoAGUAbQBhACAAZgBvAHIAIABEAFMAcABhAGMA ZQAuAGEAcwBkABAAUgBlAGIAZQBjAGMAYQAgAEwALgAgAEwAdQBiAGEAcwBJAEMAOgBcAHcAbwBy AGQAZABvAGMAcwBcAFAAZQByAHMAbwBuAGEAbABcAEEATABBAE8ATABBAEMAcAB1AGIAXABEAGUA ZgBpAG4AaQBuAGcAIABhACAATQBlAHQAYQBkAGEAdABhACAAUwBjAGgAZQBtAGEAIABmAG8AcgAg AEQAUwBwAGEAYwBlAC4AZABvAGMACABtAGEAcgBnAHIAZQB0AGIAegBDADoAXABXAEkATgBOAFQA XABQAHIAbwBmAGkAbABlAHMAXABtAGEAcgBnAHIAZQB0AGIAXABBAHAAcABsAGkAYwBhAHQAaQBv AG4AIABEAGEAdABhAFwATQBpAGMAcgBvAHMAbwBmAHQAXABXAG8AcgBkAFwAQQB1AHQAbwBSAGUA YwBvAHYAZQByAHkAIABzAGEAdgBlACAAbwBmACAARABlAGYAaQBuAGkAbgBnACAAYQAgAE0AZQB0 AGEAZABhAHQAYQAgAFMAYwBoAGUAbQBhACAAZgBvAHIAIABEAFMAcABhAGMAZQAxAC4AYQBzAGQA CABtAGEAcgBnAHIAZQB0AGIAVwBDADoAXABQAHIAbwBnAHIAYQBtACAARgBpAGwAZQBzAFwAUQB1 AGEAbABjAG8AbQBtAFwARQB1AGQAbwByAGEAIABNAGEAaQBsAFwAQQB0AHQAYQBjAGgAXABEAGUA ZgBpAG4AaQBuAGcAIABhACAATQBlAHQAYQBkAGEAdABhACAAUwBjAGgAZQBtAGEAIABmAG8AcgAg AEQAUwBwAGEAYwBlADEALgBkAG8AYwAIAG0AYQByAGcAcgBlAHQAYgA9AEMAOgBcAEQAcwBwAGEA YwBlAFwATQBlAHQAYQBkAGEAdABhAFwARABlAGYAaQBuAGkAbgBnACAAYQAgAE0AZQB0AGEAZABh AHQAYQAgAFMAYwBoAGUAbQBhACAAZgBvAHIAIABEAFMAcABhAGMAZQAxAC4AZABvAGMACABtAGEA cgBnAHIAZQB0AGIAPQBDADoAXABEAHMAcABhAGMAZQBcAE0AZQB0AGEAZABhAHQAYQBcAEQAZQBm AGkAbgBpAG4AZwAgAGEAIABNAGUAdABhAGQAYQB0AGEAIABTAGMAaABlAG0AYQAgAGYAbwByACAA RABTAHAAYQBjAGUAMgAuAGQAbwBjAAgAbQBhAHIAZwByAGUAdABiAD0AQwA6AFwARABTAHAAYQBj AGUAXABNAGUAdABhAGQAYQB0AGEAXABEAGUAZgBpAG4AaQBuAGcAIABhACAATQBlAHQAYQBkAGEA dABhACAAUwBjAGgAZQBtAGEAIABmAG8AcgAgAEQAUwBwAGEAYwBlADIALgBkAG8AYwABAAAAAQAJ BAUAAgBAAP9AA4ABACEGAAAhBgAADEpjAQEAAQAhBgAAAAAAACAGAAAAAAAAAhAAAAAAAAAAFiQA ADAAAAgAQAAA//8BAAAABwBVAG4AawBuAG8AdwBuAP//AQAIAAAAAAAAAAAAAAD//wEAAAAAAP// AAACAP//AAAAAP//AAACAP//AAAAAAMAAABHFpABAAACAgYDBQQFAgMEh3oAIAAAAIAIAAAAAAAA AP8BAAAAAAAAVABpAG0AZQBzACAATgBlAHcAIABSAG8AbQBhAG4AAAA1FpABAgAFBQECAQcGAgUH AAAAAAAAABAAAAAAAAAAAAAAAIAAAAAAUwB5AG0AYgBvAGwAAAAzJpABAAACCwYEAgICAgIEh3oA IAAAAIAIAAAAAAAAAP8BAAAAAAAAQQByAGkAYQBsAAAAIgAEAPEIiBgA8NACAABoAQAAAAD5YmZm NBtzJsVjZmYEABUAAAA0BQAArB0AAAEADwAAAAQAAxA/AAAAAAAAAAAAAAABAAEAAAABAAAAAAAA ACEDAPAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgHoAW0ALQAgYEyMAAAEAAZAGQAAAAZ AAAAcCQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAADKDEQDwEAAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAP//EgAAAAAAAAAlAEQAZQBmAGkAbgBpAG4AZwAgAGEAIABNAGUAdABhAGQAYQB0AGEA IABTAGMAaABlAG0AYQAgAGYAbwByACAARABTAHAAYQBjAGUAAAAAAAAAEABSAGUAYgBlAGMAYwBh ACAATAAuACAATAB1AGIAYQBzAAgAbQBhAHIAZwByAGUAdABiAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAD+/wAABQECAAAAAAAAAAAAAAAAAAAAAAABAAAA4IWf8vlPaBCrkQgA Kyez2TAAAACwAQAAEgAAAAEAAACYAAAAAgAAAKAAAAADAAAA0AAAAAQAAADcAAAABQAAAPgAAAAG AAAABAEAAAcAAAAQAQAACAAAACQBAAAJAAAAOAEAABIAAABEAQAACgAAAGABAAALAAAAbAEAAAwA AAB4AQAADQAAAIQBAAAOAAAAkAEAAA8AAACYAQAAEAAAAKABAAATAAAAqAEAAAIAAADkBAAAHgAA ACYAAABEZWZpbmluZyBhIE1ldGFkYXRhIFNjaGVtYSBmb3IgRFNwYWNlAHQgHgAAAAEAAAAAZWZp HgAAABEAAABSZWJlY2NhIEwuIEx1YmFzAHRhIB4AAAABAAAAAGViZR4AAAABAAAAAGViZR4AAAAL AAAATm9ybWFsLmRvdABMHgAAAAkAAABtYXJncmV0YgB0AEweAAAAAgAAADQAcmceAAAAEwAAAE1p Y3Jvc29mdCBXb3JkIDkuMAAgQAAAAAC+BO8CAAAAQAAAAAB+eG5MEsIBQAAAAAAWESsyEsIBQAAA AAAgE5et4cIBAwAAAAEAAAADAAAANAUAAAMAAACsHQAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAA/v8AAAUBAgAAAAAAAAAAAAAAAAAAAAAAAQAAAALVzdWcLhsQk5cIACss+a4wAAAA GAEAAAwAAAABAAAAaAAAAA8AAABwAAAABQAAAIgAAAAGAAAAkAAAABEAAACYAAAAFwAAAKAAAAAL AAAAqAAAABAAAACwAAAAEwAAALgAAAAWAAAAwAAAAA0AAADIAAAADAAAAPoAAAACAAAA5AQAAB4A AAAOAAAATUlUIExpYnJhcmllcwBNAAMAAAA/AAAAAwAAAA8AAAADAAAAcCQAAAMAAACgCgkACwAA AAAAAAALAAAAAAAAAAsAAAAAAAAACwAAAAAAAAAeEAAAAQAAACYAAABEZWZpbmluZyBhIE1ldGFk YXRhIFNjaGVtYSBmb3IgRFNwYWNlAAwQAAACAAAAHgAAAAYAAABUaXRsZQADAAAAAQAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAEAAAACAAAAAwAAAAQAAAAFAAAABgAAAAcAAAAIAAAACQAAAAoAAAALAAAADAAAAA0AAAAOAAAA DwAAABAAAAARAAAAEgAAABMAAAAUAAAAFQAAABYAAAAXAAAAGAAAABkAAAAaAAAAGwAAAP7///8d AAAAHgAAAB8AAAAgAAAAIQAAACIAAAAjAAAAJAAAACUAAAAmAAAA/v///ygAAAApAAAAKgAAACsA AAAsAAAALQAAAC4AAAD+////MAAAADEAAAAyAAAAMwAAADQAAAA1AAAANgAAAP7////9////OQAA AP7////+/////v////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// UgBvAG8AdAAgAEUAbgB0AHIAeQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAABYABQH//////////wMAAAAGCQIAAAAAAMAAAAAAAABGAAAAAAAAAAAAAAAAwCFdqa3h wgE7AAAAgAAAAAAAAAAxAFQAYQBiAGwAZQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAADgACAP///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAABwAAACZFAAAAAAAAFcAbwByAGQARABvAGMAdQBtAGUAbgB0AAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAaAAIBBQAAAP//////////AAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACI2AAAAAAAABQBTAHUAbQBtAGEAcgB5 AEkAbgBmAG8AcgBtAGEAdABpAG8AbgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACgAAgECAAAA BAAAAP////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAnAAAAABAAAAAAAAAF AEQAbwBjAHUAbQBlAG4AdABTAHUAbQBtAGEAcgB5AEkAbgBmAG8AcgBtAGEAdABpAG8AbgAAAAAA AAAAAAAAOAACAf///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AC8AAAAAEAAAAAAAAAEAQwBvAG0AcABPAGIAagAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAASAAIBAQAAAAYAAAD/////AAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAGoAAAAAAAAATwBiAGoAZQBjAHQAUABvAG8AbAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABYAAQD///////////////8AAAAAAAAA AAAAAAAAAAAAAAAAAMAhXamt4cIBwCFdqa3hwgEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP////// /////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEA AAD+//////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////// ////////////////////////////////////////////////////////////////////////AQD+ /wMKAAD/////BgkCAAAAAADAAAAAAAAARhgAAABNaWNyb3NvZnQgV29yZCBEb2N1bWVudAAKAAAA TVNXb3JkRG9jABAAAABXb3JkLkRvY3VtZW50LjgA9DmycQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA= --=====================_4628815==_-- From rrodgers@MIT.EDU Fri Sep 5 11:52:10 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p1/8.12.8) with ESMTP id h85FqAk0018421 for ; Fri, 5 Sep 2003 11:52:10 -0400 (EDT) Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82])h85Fpwje003640; Fri, 5 Sep 2003 11:51:59 -0400 (EDT) Received: from manawatu-mail-centre.mit.edu (MANAWATU-MAIL-CENTRE.MIT.EDU [18.7.7.71])h85Fo0SZ017605; Fri, 5 Sep 2003 11:50:00 -0400 (EDT) Received: from dspace-03.mit.edu (DSPACE-03.MIT.EDU [18.51.2.148]) ) h85Fnxaq026217; Fri, 5 Sep 2003 11:49:59 -0400 (EDT) Received: (from rrodgers@localhost) by dspace-03.mit.edu (8.9.3) id LAA10252; Fri, 5 Sep 2003 11:49:59 -0400 From: Richard Rodgers To: dspace-general@MIT.EDU, dspace-tech@lists.sourceforge.net Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 05 Sep 2003 11:49:59 -0400 Message-Id: <1062776999.25377.91.camel@dspace-03.mit.edu> Mime-Version: 1.0 Subject: [Dspace-general] Preview of next release of DSpace X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Fri, 05 Sep 2003 15:52:10 -0000 An Early Look at DSpace 1.2 We would like to share our plans for the next release of DSpace in order to open up the development process and let adopters and evaluators know where we are putting our efforts. Here is a 'short list' of major features we propose to include in this release, reflecting our assessment of the most desired and widely useful enhancements to the system. These have been gathered from the SourceForge request list, discussions on the 'dspace-tech' mailing list, and input from others using the DSpace system. Given thousands of downloads and over a hundred known deployments, it is difficult to come up with an optimal list of enhancements that is both small and gives maximum benefit to the DSpace community - if you feel strongly about a feature that is not on this list, please let us know. It is a 'short-list' in the sense that while we will concentrate our efforts on the list items for the next release, we may not be able to implement all of the items in the list. It is also our short list - DSpace 1.2 will also likely contain other contributed work from third parties, which will be announced separately. The item descriptions are rather brief, but we wanted to offer at least a general picture of the release as early as we could. We will be sending out calls for discussion on several of the features, and more detailed descriptions of the others, to insure that the community has good opportunity to offer input. DSpace 1.2 Enhancement Short List (1) Support for sub-communities. The current simple and flat implementation of communities is not powerful enough for users who would like to express more complex organizational structures. (2) Allow delegated administration of communities and collections. It is time to offload administration tasks to the users. A 'collection-editor' role will be able to edit item metadata within a collection after items have been submitted, and a'community-administrator' role will have the ability to manage a community. (3) Import/Export items with METS metadata. DSpace currently uses a custom XML schema to import and export item metadata and associated digital files (or 'bitstreams'). With the emergence of the METS standard for digital object encoding http://www.loc.gov/standards/mets/, and in particular its application as an Open Archival Information Systems Archival Information Package, we are in the process of defining a METS profile for DSpace items. Once that profile is complete, we will add support in the batch import and export routines for METS encoding of DSpace items, as well as storing METS packages internally as AIPs. When the METS profile is ready, we will distribute it (in advance of the release). (4) Tools for adding and managing items in multiple collections. (5) Analyze need for persistent identifiers (e.g. Handles) for bitstreams in addition to item metadata records. Implement if appropriate. (6) Support for thumbnails of bitstreams in the item display (for appropriate content). (7) Several enhancements to the administration UI centered around ease-of-use and robustness. (8) Support for indexing and search of the full-text of item documents. (9) Better support for web page (HTML document) item display. MIT and HP's role in future DSpace development The DSpace developers at MIT and HP would also like to take this opportunity to share with the community of DSpace adopters what we feel our role should be in the continuing development and support of the DSpace system. DSpace was released as open source system in the hope that our work at HP and MIT would benefit other institutions with similar problems. We are delighted by the interest in and adoption of the DSpace system so far, but we have very limited resources to enhance and maintain the system... Remember that as an open source system DSpace does not generate any revenue, and we are maintaining the system for non-MIT use gratis, because we need it too. Today we see the HP/MIT team as having two main roles, to: -- make changes that are needed by MIT to meet its service goals -- coordinate changes made by other institutions or individuals back into the main codebase We will focus our energy on changes required by MIT. We acknowledge that some changes (e.g. digital publishing tools, or support for non-Roman character sets), while not at the top of MIT's list, are priorities elsewhere. We welcome contributions to the system from those for whom these changes are a priority. We have posted guidelines for those who wish to contribute code at the new dspace.org website (Choose the 'DSpace Technology' link, and look for 'Development Guidelines'), and encourage participation in advancing the DSpace platform. From j.krizack@neu.edu Fri Sep 5 12:40:07 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p1/8.12.8) with ESMTP id h85Ge7k0019124 for ; Fri, 5 Sep 2003 12:40:07 -0400 (EDT) Received: from neuhub02.neu.edu (neuhub02.neu.edu [155.33.17.117]) h85Ge6m5011385 for ; Fri, 5 Sep 2003 12:40:06 -0400 (EDT) To: dspace-general@mit.edu X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: From: j.krizack@neu.edu Date: Fri, 5 Sep 2003 12:40:06 -0400 X-MIMETrack: Serialize by Router on NEUHUB02/Server/NEU(Release 5.0.11 |July 24, 2002) at 09/05/2003 12:40:04 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Subject: [Dspace-general] Re: Margaret Branschofsky's paper X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Fri, 05 Sep 2003 16:40:08 -0000 The text didn't come through on my email. Is there another way I can get a copy of the paper? Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joan D. Krizack University Archivist and Head, Special Collections Department 92 Snell Library Northeastern University 360 Huntington Avenue Boston, MA 02115-5000 (v) 617.373.8318 (f) 617.373.8132 j.krizack@neu.edu http://www.lib.neu.edu/archives/ From chodge5@utk.edu Fri Sep 5 13:39:56 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p1/8.12.8) with ESMTP id h85Hduk0019866 for ; Fri, 5 Sep 2003 13:39:56 -0400 (EDT) Received: from panther.mail.utk.edu (panther.mail.utk.edu [160.36.178.33]) h85HdtmX015304 for ; Fri, 5 Sep 2003 13:39:55 -0400 (EDT) Received: from helios.dii.utk.edu (helios.dii.utk.edu [160.36.178.159]) by panther.mail.utk.edu (8.12.9/8.12.9) with ESMTP id h85HdiPg022577; Fri, 5 Sep 2003 13:39:44 -0400 Received: from helios.dii.utk.edu (helios.dii.utk.edu [160.36.178.159]) by helios.dii.utk.edu (8.12.9/8.12.9) with ESMTP id h85Hdi1c004354; Fri, 5 Sep 2003 13:39:44 -0400 (EDT) Date: Fri, 5 Sep 2003 13:39:44 -0400 (EDT) From: chodge5@utk.edu X-Sender: hodge@helios.dii.utk.edu To: dspace-general@mit.edu Subject: [Dspace-general] Preview of next release of DSpace] Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=0.8 required=100.0 tests=NO_REAL_NAME,USER_AGENT_PINE version=2.54 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.54 (1.174.2.17-2003-05-11-exp) X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Fri, 05 Sep 2003 17:39:56 -0000 This is great news! With regard to future development, I think the real challenge is going to be for the DSpace community to find some way to organize itself and facilitate the development of collaborative projects around specific issues. I think a number of people are willing to devote some resources in this area -- I know we are -- but there needs to be some structure and coordination to make sure the work gets channelled back into the community as a whole. Chris Hodge UNiversity of Tennessee -------- Original Message -------- Subject: [Dspace-general] Preview of next release of DSpace Date: Fri, 05 Sep 2003 11:49:59 -0400 From: Richard Rodgers To: dspace-general@mit.edu, dspace-tech@lists.sourceforge.net An Early Look at DSpace 1.2 We would like to share our plans for the next release of DSpace in order to open up the development process and let adopters and evaluators know where we are putting our efforts. Here is a 'short list' of major features we propose to include in this release, reflecting our assessment of the most desired and widely useful enhancements to the system. These have been gathered from the SourceForge request list, discussions on the 'dspace-tech' mailing list, and input from others using the DSpace system. Given thousands of downloads and over a hundred known deployments, it is difficult to come up with an optimal list of enhancements that is both small and gives maximum benefit to the DSpace community - if you feel strongly about a feature that is not on this list, please let us know. It is a 'short-list' in the sense that while we will concentrate our efforts on the list items for the next release, we may not be able to implement all of the items in the list. It is also our short list - DSpace 1.2 will also likely contain other contributed work from third parties, which will be announced separately. The item descriptions are rather brief, but we wanted to offer at least a general picture of the release as early as we could. We will be sending out calls for discussion on several of the features, and more detailed descriptions of the others, to insure that the community has good opportunity to offer input. DSpace 1.2 Enhancement Short List (1) Support for sub-communities. The current simple and flat implementation of communities is not powerful enough for users who would like to express more complex organizational structures. (2) Allow delegated administration of communities and collections. It is time to offload administration tasks to the users. A 'collection-editor' role will be able to edit item metadata within a collection after items have been submitted, and a'community-administrator' role will have the ability to manage a community. (3) Import/Export items with METS metadata. DSpace currently uses a custom XML schema to import and export item metadata and associated digital files (or 'bitstreams'). With the emergence of the METS standard for digital object encoding http://www.loc.gov/standards/mets/, and in particular its application as an Open Archival Information Systems Archival Information Package, we are in the process of defining a METS profile for DSpace items. Once that profile is complete, we will add support in the batch import and export routines for METS encoding of DSpace items, as well as storing METS packages internally as AIPs. When the METS profile is ready, we will distribute it (in advance of the release). (4) Tools for adding and managing items in multiple collections. (5) Analyze need for persistent identifiers (e.g. Handles) for bitstreams in addition to item metadata records. Implement if appropriate. (6) Support for thumbnails of bitstreams in the item display (for appropriate content). (7) Several enhancements to the administration UI centered around ease-of-use and robustness. (8) Support for indexing and search of the full-text of item documents. (9) Better support for web page (HTML document) item display. MIT and HP's role in future DSpace development The DSpace developers at MIT and HP would also like to take this opportunity to share with the community of DSpace adopters what we feel our role should be in the continuing development and support of the DSpace system. DSpace was released as open source system in the hope that our work at HP and MIT would benefit other institutions with similar problems. We are delighted by the interest in and adoption of the DSpace system so far, but we have very limited resources to enhance and maintain the system... Remember that as an open source system DSpace does not generate any revenue, and we are maintaining the system for non-MIT use gratis, because we need it too. Today we see the HP/MIT team as having two main roles, to: -- make changes that are needed by MIT to meet its service goals -- coordinate changes made by other institutions or individuals back into the main codebase We will focus our energy on changes required by MIT. We acknowledge that some changes (e.g. digital publishing tools, or support for non-Roman character sets), while not at the top of MIT's list, are priorities elsewhere. We welcome contributions to the system from those for whom these changes are a priority. We have posted guidelines for those who wish to contribute code at the new dspace.org website (Choose the 'DSpace Technology' link, and look for 'Development Guidelines'), and encourage participation in advancing the DSpace platform. _______________________________________________ Dspace-general mailing list Dspace-general@mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general From margretb@MIT.EDU Tue Sep 16 14:41:55 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p1/8.12.8) with ESMTP id h8GIftk0025559 for ; Tue, 16 Sep 2003 14:41:55 -0400 (EDT) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72])h8GIfsex013104 for ; Tue, 16 Sep 2003 14:41:54 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])h8GIcdqv002354 for ; Tue, 16 Sep 2003 14:38:39 -0400 (EDT) Received: from dspace-01.mit.edu (DSPACE-01.MIT.EDU [18.51.2.146]) (authenticated bits=0) (User authenticated as margretb@ATHENA.MIT.EDU)h8GIccGs021314 for ; Tue, 16 Sep 2003 14:38:38 -0400 (EDT) Message-Id: <5.2.1.1.2.20030916142738.01de45c0@po10.mit.edu> X-Sender: margretb@po10.mit.edu X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Tue, 16 Sep 2003 14:38:04 -0400 To: dspace-general@MIT.EDU From: Margret Branschofsky Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Dspace-general] Theses in DSpace X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 16 Sep 2003 18:41:56 -0000 Hi all, I'm wondering if any other institutions are planning to use DSpace for theses. I know that the Theses Alive! project in the UK is doing this, and we at MIT are also planning an implementation. I'm thinking that it would be very useful if we could all agree to use the same metadata standard to accommodate theses in DSpace. Margret Margret Branschofsky DSpace User Support Manager Digital Library Research Group Bldg. 14S-M24 (617)253-1293 margretb@mit.edu http://dspace.mit.edu From ellermann@ubib.eur.nl Tue Sep 16 15:48:54 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p1/8.12.8) with ESMTP id h8GJmrk0026294 for ; Tue, 16 Sep 2003 15:48:53 -0400 (EDT) Received: from smtpq2.home.nl (smtpq2.home.nl [213.51.128.197]) h8GJm2ex022083; Tue, 16 Sep 2003 15:48:02 -0400 (EDT) Received: from [213.51.128.133] (port=44990 helo=smtp2.home.nl) by smtpq2.home.nl with esmtp (Exim 4.20) id 19zLnt-0002zu-IF; Tue, 16 Sep 2003 21:48:01 +0200 Received: from cp30619-a.landg1.lb.home.nl ([213.51.18.251]:35194 helo=ubib.eur.nl) by smtp2.home.nl with esmtp (Exim 4.20) id 19zLnr-0004TX-NS; Tue, 16 Sep 2003 21:47:59 +0200 Message-ID: <3F6768BA.6070404@ubib.eur.nl> Date: Tue, 16 Sep 2003 21:47:06 +0200 From: Henk Ellermann User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Margret Branschofsky Subject: Re: [Dspace-general] Theses in DSpace References: <5.2.1.1.2.20030916142738.01de45c0@po10.mit.edu> In-Reply-To: <5.2.1.1.2.20030916142738.01de45c0@po10.mit.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-AtHome-MailScanner-Information: Neem contact op met support@home.nl voor meer informatie X-AtHome-MailScanner: Found to be clean cc: dspace-general@MIT.EDU X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list Reply-To: ellermann@ubib.eur.nl List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 16 Sep 2003 19:48:54 -0000 Hi Margret, > I'm wondering if any other institutions are planning to use DSpace for > theses. I know that the Theses Alive! project in the UK is doing this, > and we at MIT are also planning an implementation. I'm thinking that it > would be very useful if we could all agree to use the same metadata > standard to accommodate theses in DSpace. We use DSpace as an Institutional Repository and have included a number of dissertations. It will not be long before we will put all (well, except the obvious few) dissertations of the Erasmus University in DSpace. So far we have not given dissertations any special treatment in terms of metadata. We do use aQDC field description.sponsorship for the names of the promotores (is that an English word too?). We have adapted DSpace to expert qualified dublin core too, so we can use this field for localized services (web display) in the near future. However, we sure would like it if there were some kind of (exportable) metadataset, standardized across DSpace users, for dissertations. If you can initiate something, we are willing to co-operate and spend some quality time on it. Regards, Henk Ellermann -- -- ------------------------------------------------------------------------------- - Henk Ellermann - Erasmus Electronic Publishing Initiative - University Library, Erasmus University Rotterdam - P.O. Box 1738, 3000 DR, Rotterdam, The Netherlands - ellermann@ubib.eur.nl - weblog: http://eepi.ubib.eur.nl/iliit/index.html - tel: +31 (0) 10 4081284/81208 - cell: +31 (0) 6 41 50 2002 ------------------------------------------------------------------------------- -- From margretb@MIT.EDU Wed Sep 17 10:09:53 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p1/8.12.8) with ESMTP id h8HE9rk0004812 for ; Wed, 17 Sep 2003 10:09:53 -0400 (EDT) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72])h8HE9qUC002181 for ; Wed, 17 Sep 2003 10:09:52 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])h8HE9qst029677 for ; Wed, 17 Sep 2003 10:09:52 -0400 (EDT) Received: from dspace-01.mit.edu (DSPACE-01.MIT.EDU [18.51.2.146]) (authenticated bits=0) (User authenticated as margretb@ATHENA.MIT.EDU)h8HE9qGs023946 for ; Wed, 17 Sep 2003 10:09:52 -0400 (EDT) Message-Id: <5.2.1.1.2.20030917093545.01e8ba90@po10.mit.edu> X-Sender: margretb@po10.mit.edu X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Wed, 17 Sep 2003 10:09:45 -0400 To: dspace-general@MIT.EDU From: Margret Branschofsky Subject: Re: [Dspace-general] Theses in DSpace In-Reply-To: <3F6768BA.6070404@ubib.eur.nl> References: <5.2.1.1.2.20030916142738.01de45c0@po10.mit.edu> <5.2.1.1.2.20030916142738.01de45c0@po10.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 17 Sep 2003 14:09:54 -0000 Hello Henk and JQ, Thanks for responding to my question. We are planning to use the existing qualified DC in DSpace for our theses, but we would like to add a few fields for the thesis-specific information, such as thesis department and degree granted. We were originally planning to put the thesis advisor (or sponsor or supervisor) under Contributor.advisor and the department and degree under Description.department and Description.degree. But now we are exploring alternatives and seeing what others are using before making a decision. The NDLTD schema, for example, uses (simple) Dublin Core with the addition of a Degree element and 4: thesis.degree.name Name of degree (Masters in Operations Research) thesis.degree.level Level of education (masters, doctoral) thesis.degree.discipline Area of study (name of department or program) thesis.degree.grantor Institution granting the degree I believe that the Thesis Alive! project is seriously considering using this. I am also in communication with Ed Fox (NDLTD) and Thom Hickey(OCLC) to find out how likely it is that the NDLTD standard will be brought into the Dublin Core. And I'm also trying to find out if the electronic thesis/dissertation OAI Union Catalog will ever adopt those fields (So far it uses simple DC.) I have one question for Henk: >We have adapted DSpace to expert qualified dublin core too, so we can use >this field for localized services (web display) in the near future. I'm assuming you meant "export" in this sentence? Have you created an XML Schema of the DSpace metadata? Best regards, Margret Margret Branschofsky DSpace User Support Manager Digital Library Research Group Bldg. 14S-M24 (617)253-1293 margretb@mit.edu http://dspace.mit.edu From Theo.Andrew@ed.ac.uk Wed Sep 17 11:16:42 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p1/8.12.8) with ESMTP id h8HFGgk0005947 for ; Wed, 17 Sep 2003 11:16:42 -0400 (EDT) Received: from lawnmarket.ucs.ed.ac.uk (lawnmarket.ucs.ed.ac.uk [129.215.166.63])h8HFGdSZ013302 for ; Wed, 17 Sep 2003 11:16:39 -0400 (EDT) Received: (from nobody@localhost) by lawnmarket.ucs.ed.ac.uk (8.11.6p2/8.11.6) id h8HFGck10976 for dspace-general@mit.edu; Wed, 17 Sep 2003 16:16:38 +0100 (BST) X-Authentication-Warning: lawnmarket.ucs.ed.ac.uk: nobody set sender to Theo.Andrew@ed.ac.uk using -f To: dspace-general Subject: Re: [Dspace-general] Theses in DSpace Message-ID: <1063811798.3f687ad675af3@staffmail.ed.ac.uk> Date: Wed, 17 Sep 2003 16:16:38 +0100 (BST) From: Theo Andrew References: <5.2.1.1.2.20030916142738.01de45c0@po10.mit.edu> <5.2.1.1.2.20030916142738.01de45c0@po10.mit.edu> <5.2.1.1.2.20030917093545.01e8ba90@po10.mit.edu> In-Reply-To: <5.2.1.1.2.20030917093545.01e8ba90@po10.mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.8 X-Originating-IP: 129.215.146.126 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 17 Sep 2003 15:16:43 -0000 Hello All, This discussion is extremely timely as we (the Theses Alive! team) are currently investigating metadata schemas for ETDs. It seems we are taking the same approach as Margret in that we are "exploring alternatives and seeing what others are using before making a decision". It would be extremely useful if we could all together reach a consensus on what to use. So far we have compared the DSPace default DC with the ETD-MS schema and the TDM DTD and come up with a proposed list that we are thinking of using. If you are interested you can visit our web site and see our Proposed Submission Fields and Related Metadata Elements: http://www.thesesalive.ac.uk/archive/SchemaComparison.html or have a look at a compiled list of the main DTDs for ETDs available; http://www.thesesalive.ac.uk/archive/MetadataSchemas.html We would welcome feedback on our proposed list! Kind regards Theo ****************************************************** Dr. Theo Andrew * Project Officer for * Tel: 0131 651 1612 Theses Alive! & SHERPA * Fax: 0131 650 3380 Edinburgh University * Main Library * http://www.thesesalive.ac.uk George Square * http://www.sherpa.ac.uk Edinburgh EH8 9LJ * ****************************************************** From ellermann@ubib.eur.nl Wed Sep 17 15:08:52 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p1/8.12.8) with ESMTP id h8HJ8pk0009349 for ; Wed, 17 Sep 2003 15:08:52 -0400 (EDT) Received: from smtpq1.home.nl (smtpq1.home.nl [213.51.128.196]) h8HJ7vlH027840; Wed, 17 Sep 2003 15:07:57 -0400 (EDT) Received: from [213.51.128.135] (port=41882 helo=smtp4.home.nl) by smtpq1.home.nl with esmtp (Exim 4.20) id 19zhee-0006JI-UW; Wed, 17 Sep 2003 21:07:56 +0200 Received: from cp30619-a.landg1.lb.home.nl ([213.51.18.251]:35460 helo=ubib.eur.nl) by smtp4.home.nl with esmtp (Exim 4.20) id 19zhed-0000fS-Tu; Wed, 17 Sep 2003 21:07:56 +0200 Message-ID: <3F68B0E2.9000101@ubib.eur.nl> Date: Wed, 17 Sep 2003 21:07:14 +0200 From: Henk Ellermann User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Margret Branschofsky Subject: Re: [Dspace-general] Theses in DSpace References: <5.2.1.1.2.20030916142738.01de45c0@po10.mit.edu> <5.2.1.1.2.20030916142738.01de45c0@po10.mit.edu> <5.2.1.1.2.20030917093545.01e8ba90@po10.mit.edu> In-Reply-To: <5.2.1.1.2.20030917093545.01e8ba90@po10.mit.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-AtHome-MailScanner-Information: Neem contact op met support@home.nl voor meer informatie X-AtHome-MailScanner: Found to be clean cc: dspace-general@mit.edu X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list Reply-To: ellermann@ubib.eur.nl List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 17 Sep 2003 19:08:52 -0000 Hi Margret, It's great that you are finding 'good practices' elsewhere when it comes to the dissertations metadata. It seems to me that > Thanks for responding to my question. We are planning to use the > existing qualified DC in DSpace for our theses, but we would like to add > a few fields for the thesis-specific information, such as thesis > department and degree granted. We were originally planning to put the Not sure what degree granted is about. are the possible Palues h D or dr? > > thesis.degree.name Name of degree (Masters in Operations > Research) > thesis.degree.level Level of education (masters, doctoral) > thesis.degree.discipline Area of study (name of department or > program) > thesis.degree.grantor Institution granting the degree There is no problem with these fields if the values are not restricted, except for the service providers of course :) Wouldn't it be an idea to constrain the values, or set a language? If I'm giving dutch strings and yours are in English we do have a slight problem. > > I believe that the Thesis Alive! project is seriously considering using > this. I am also in communication with Ed Fox (NDLTD) and Thom > Hickey(OCLC) to find out how likely it is that the NDLTD standard will > be brought into the Dublin Core. And I'm also trying to find out if the > electronic thesis/dissertation OAI Union Catalog will ever adopt those > fields (So far it uses simple DC.) Yes, good idea. Keep us posted. If there is anything I can do, if only to keep an eye on non-english users, let me know. >> We have adapted DSpace to expert qualified dublin core too, so we can >> use this field for localized services (web display) in the near future. > > > I'm assuming you meant "export" in this sentence? Have you created an > XML Schema of the DSpace metadata? Blush. Yes I meant export. No XML Schema as yet. We are using it for internal purposes only and have not yet 'fixed' the elements we want to use. We are experimenting a little. Of course, an xsd will be made in due time. Regards, Henk -- -- ------------------------------------------------------------------------------- - dr. Henk Ellermann - Erasmus Electronic Publishing Initiative - University Library, Erasmus University Rotterdam - P.O. Box 1738, 3000 DR, Rotterdam, The Netherlands - ellermann@ubib.eur.nl - http://eepi.ubib.eur.nl/iliit/index.html - tel: +31 (0) 10 4081284/81208 - cell: +31 (0) 6 41 50 2002 ------------------------------------------------------------------------------- -- From scott.yeadon@anu.edu.au Sun Sep 21 19:11:43 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8LNBggH000696 for ; Sun, 21 Sep 2003 19:11:43 -0400 (EDT) Received: from anu.edu.au (anumail4.anu.edu.au [150.203.2.44]) h8LNBeAk015597 for ; Sun, 21 Sep 2003 19:11:41 -0400 (EDT) Received: from anumail.anu.edu.au (adelong.anu.edu.au [150.203.2.90]) by anu.edu.au (8.12.9/8.12.9) with ESMTP id h8LNBdKx010344 for ; Mon, 22 Sep 2003 09:11:39 +1000 (EST) Received: from sts59101.anu.edu.au (sts59101.anu.edu.au [150.203.59.101]) by anumail.anu.edu.au (8.12.10/8.12.10) with ESMTP id h8LNBdXf008831 for ; Mon, 22 Sep 2003 09:11:39 +1000 (EST) Content-Type: text/plain; charset="us-ascii" From: Scott Yeadon To: dspace-general@mit.edu Date: Mon, 22 Sep 2003 09:11:21 +1000 User-Agent: KMail/1.4.1 MIME-Version: 1.0 Message-Id: <200309220911.21312.scott.yeadon@anu.edu.au> X-Sender: scott.yeadon@anu.edu.au X-Sender-Domain: anu.edu.au X-Spam-Status: Scanned X-Spam-Score: (-0.4) X-Spam-Tests: USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.36 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id h8LNBggH000696 Subject: [Dspace-general] DSpace customisation X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list Reply-To: scott.yeadon@anu.edu.au List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Sun, 21 Sep 2003 23:11:43 -0000 Hi, We're looking at introducing DSpace to ANU (Australian National University), and I have just read a paper date Jan 2003 in D-Lib magazine entitled DSpace - An OpenSource Dynamic Digital Repository, located at http://www.dlib.org/dlib/january03/smith/01smith.html. The section entitled "The DSpace Federation" contains a paragraph as follows: "In 2002, MIT formed collaborative partnerships with a small number of other academic research institutions in the US, UK, and Canada, to address some specific questions such as: what will it take to successfully deploy the system at another institution? How much localization, how much customization, and how much time and effort are needed?" I was wondering what sort of feedback (if any) had been received on these topics, especially where non-trivial modifications werer required such as more complex authorisation and low-level code modifications were required, and how these we done to avoid issues when upgrading to future versions. Thanks. Scott. From rrodgers@MIT.EDU Mon Sep 22 15:18:11 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8MJIBgH011968 for ; Mon, 22 Sep 2003 15:18:11 -0400 (EDT) Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82])h8MJIANL001916 for ; Mon, 22 Sep 2003 15:18:10 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])h8MJI9OT029736 for ; Mon, 22 Sep 2003 15:18:09 -0400 (EDT) Received: from dspace-03.mit.edu (DSPACE-03.MIT.EDU [18.51.2.148]) ) h8MJI9BY021543 for ; Mon, 22 Sep 2003 15:18:09 -0400 (EDT) Received: (from rrodgers@localhost) by dspace-03.mit.edu (8.9.3) id PAA15623; Mon, 22 Sep 2003 15:18:09 -0400 From: Richard Rodgers To: dspace-general@MIT.EDU Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 22 Sep 2003 15:18:08 -0400 Message-Id: <1064258288.15587.3.camel@dspace-03.mit.edu> Mime-Version: 1.0 Subject: [Dspace-general] Persistent Bitstream IDs - Call For Discussion X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 22 Sep 2003 19:18:11 -0000 Bitstream Identifiers in DSpace - Call for Discussion Part of the planning process for enhancements to DSpace is requirements analysis - obtaining a more precise understanding of the needs of the adopter community. We have frequently heard articulated the need for bitstream-level - rather than item-level - handles or other persistent identifiers. Recall that in DSpace terminology, an 'item' is a logical construct consisting of a Dublin Core metadata record, and one or more digital objects (files), each of which is referred to as a 'bitstream'. In the current design, when a item has exited the workflow, it is assigned a handle, but the individual bitstreams are not. The rationale for this - without delving too deeply into digital preservation debates - is fairly simple: the item represents some sort of usable content, but its digital expression may vary over time. For instance, a bitstream may need to be migrated into a physically distinct bitstream of another format for preservation purposes (e.g. because the original format has become obsolete): the bitstream has changed, but the item 'content' has not. The thing that persists is what is given a persistent identifier. So why would one need a persistent identifier for an individual bitstream? This write-up is an attempt to solicit your feedback on the subject. Any response is welcome - but best of all would be a 'use-case' description: a concrete set of practices or problems for which a different bitstream identifier system would provide a solution. Disentangling the Issues There are actually a few distinct but related issues here, and it is useful to attempt to tease them apart. First, what counts as an identifier in this context? Bitstreams (files) in DSpace already possess an identifier of a sort, viz. the URL appearing on the item display page: https://hpds1.mit.edu/retrieve/1042/Porter_debate.pdf This identifier, composed of the server name, the primary key in the bitstream database table, and the filename assigned upon submission has several noteworthy characteristics: (1) it is fixed, in that it always refers to the same bitstream (2) like all URLs, the identifier is a location reference: you can use it to retrieve the bitstream (3) it has limited persistence, viz. as long as server name and database tables do not change (4) one cannot use it to locate or retrieve the 'parent' item (its metadata and related bitstreams) For many purposes this identifier may be adequate. For instance, if the need is to retrieve bitstreams for near-term reuse as learning objects, then the time-scale is likely to be such that the URL will remain valid. Even if the repository is re-hosted (the server name changes), standard redirection techniques would ensure that the URL will resolve to the desired bitstream. Still, the bitstream URL is *fragile* in ways a handle is not: if the database is exported and re-imported (as was done for the DSpace 1.1 upgrade), there is no guarantee that the bitstream key part of the URL (therefore its validity) will be preserved. This quick dissection suggests some of the issues in play: do you need a bitstream identifier to be persistent for a longer period, or simply more 'durable'? Does it have to be a handle? Should bitstream IDs also be required to get you to the item of which it is a part? Do they have to be a location identifier (like a URL)? Does the identifier system need to independently maintained (like the handle system), or not? What are other required/desirable characteristics of bitstream identifiers? Please share your insights on the dspace-general list; again, a concrete use-case is the most valuable driver of design: a specific set of circumstances and outcomes that any design must satisfy. From jqj@darkwing.uoregon.edu Mon Sep 22 19:50:43 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8MNoggH015516 for ; Mon, 22 Sep 2003 19:50:43 -0400 (EDT) Received: from dynamic.uoregon.edu (dynamic.uoregon.edu [128.223.98.16]) h8MNoffW016269 for ; Mon, 22 Sep 2003 19:50:42 -0400 (EDT) Received: from jqj (12-225-124-41.client.attbi.com [12.225.124.41]) by dynamic.uoregon.edu (8.12.8/8.12.8) with SMTP id h8MNodZD008847 for ; Mon, 22 Sep 2003 16:50:39 -0700 From: "JQ Johnson" To: Subject: RE: [Dspace-general] Persistent Bitstream IDs - Call For Discussion Date: Mon, 22 Sep 2003 16:52:35 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-reply-to: <1064258288.15587.3.camel@dspace-03.mit.edu> X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4925.2800 Importance: Normal X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 22 Sep 2003 23:50:43 -0000 Overall, I do not believe that persistent bitstream IDs are a good idea. However, the question of persistent IDs reminds me of a closely related question, how to provide multiple revisions of an item in the DSpace context. Our faculty seem likely to use DSpace heavily as a repository for working papers. Such working papers have a short useful life, and are replaced by new versions fairly rapidly. How would one handle such versions in DSpace? The easiest option is separate items for each version, but then there's no automatic version control or tracking of the connections between versions (no "previous version" metadata, etc.). Another option would be to treat all versions as a single item, with different versions appearing as additional bitstreams. This has the advantage of preserving the connections between the versions, but would require implementation changes to allow bitstream additions by item owners and to provide a small amount of additional per-bitstream metadata (the version info; currently the only significant per-bitstream metadata is the filename). This issue is connected with the problem of persistent bitstream IDs. If we were to have multiple versions in the same item, then we'd certainly want persistent IDs at the bitstream level. Conversely, persistent bitstream IDs would encourage a future evolution of DSpace into making bitstreams first class citizens with more of their own metadata. However, I think that the key issue that should drive this discussion is "what do the faculty want?" I agree with Harnad that the major problem for institutional repositories is getting faculty to contribute. If real faculty care about PURLs and such (I don't think they do, by the way), then that should be the key desideratum. JQ Johnson Office: 115F Knight Library Academic Education Coordinator e-mail: jqj@darkwing.uoregon.edu 1299 University of Oregon 1-541-346-1746 (v); -3485 (fax) Eugene, OR 97403-1299 http://darkwing.uoregon.edu/~jqj From scott.yeadon@anu.edu.au Thu Sep 25 02:15:44 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8P6FhgH019239 for ; Thu, 25 Sep 2003 02:15:44 -0400 (EDT) Received: from anu.edu.au (anumail4.anu.edu.au [150.203.2.44]) h8P6FfAT022763 for ; Thu, 25 Sep 2003 02:15:42 -0400 (EDT) Received: from anumail.anu.edu.au (anumail.anu.edu.au [150.203.2.90]) by anu.edu.au (8.12.10/8.12.10) with ESMTP id h8P6FCIB021565; Thu, 25 Sep 2003 16:15:12 +1000 (EST) Received: from sts59101.anu.edu.au (sts59101.anu.edu.au [150.203.59.101]) by anumail.anu.edu.au (8.12.10/8.12.10) with ESMTP id h8P6FCXf016227; Thu, 25 Sep 2003 16:15:12 +1000 (EST) Content-Type: text/plain; charset="us-ascii" From: Scott Yeadon To: dspace-general@mit.edu, dspace-tech-request@lists.sourceforge.net Date: Thu, 25 Sep 2003 16:14:32 +1000 User-Agent: KMail/1.4.1 MIME-Version: 1.0 Message-Id: <200309251614.32666.scott.yeadon@anu.edu.au> X-Sender: scott.yeadon@anu.edu.au X-Sender-Domain: anu.edu.au X-Spam-Status: Scanned X-Spam-Score: (-0.4) X-Spam-Tests: USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.36 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id h8P6FhgH019239 Subject: [Dspace-general] Submitting documents as a non-administrator user X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list Reply-To: scott.yeadon@anu.edu.au List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Thu, 25 Sep 2003 06:15:44 -0000 Hello, At the ANU we've been performing some informal testing of DSpace, and one major issue appears to be setting up a group of non-adminstrative users who can submit documents. The DSpace documentation states that if "a collection has no e-person groups associated with any [workflow] step, submissions to that collection are installed straight into the main archive". This does not appear to be the case - non-adminstrator users do not appear to be able to store documents, but they can approve/reject submissions. For example, I have set up Community A which has the default anonymous read authorisations. Within this community is a single Collection. This Collection, as well as the default anonymous authorisations, has a group called Submitters containing two members - one an administrator user and one a non-administrator. This group has been granted all possible permissions add, read, write, remove, etc. against the Collection. There are no workflow steps for the Collection. The issue is that when logging on as the Submitter group administrator user, I can submit documents to the collection without issue, however when logged on as the Submitter group's non-adminstrator user (a basic author-type user) I get an authorisation error whenever I attempt to submit a document to the collection. In addition a log file error is generated stating that the user does not have WRITE access for the ITEM being submitted. This does not appear to be a problem related to the collection authorisation, but something at the item metadata level. Given that the item does not exist at this point as a DSpace item that can be manipulated via the DSpace GUI, I have drawn a blank as far as being able to get any further information and what I can do about this. Is this a known problem or can anyone shed any light on this problem? Thanks. Scott. From david.stuve@hp.com Thu Sep 25 17:39:07 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8PLd6gH001092 for ; Thu, 25 Sep 2003 17:39:06 -0400 (EDT) Received: from atlrel6.hp.com (atlrel6.hp.com [156.153.255.205]) h8PLd5dn000374 for ; Thu, 25 Sep 2003 17:39:05 -0400 (EDT) Received: from xatlrelay2.atl.hp.com (xatlrelay2.atl.hp.com [15.45.89.191]) by atlrel6.hp.com (Postfix) with ESMTP id CC8261C019D9; Thu, 25 Sep 2003 17:39:04 -0400 (EDT) Received: from xcorbh1.cv.hp.com (xcorbh1.cv.hp.com [15.7.113.189]) by xatlrelay2.atl.hp.com (Postfix) with ESMTP id 6BEB91C00A6E; Thu, 25 Sep 2003 17:39:04 -0400 (EDT) Received: by xcorbh1.cv.hp.com with Internet Mail Service (5.5.2655.55) id ; Thu, 25 Sep 2003 14:39:03 -0700 Message-ID: <5755325D04C5834187459E1E17D81F6F0834F03D@xcor01.cv.hp.com> From: "STUVE,DAVID (HP-Corvallis,ex1)" To: "'scott.yeadon@anu.edu.au'" , dspace-general@mit.edu, dspace-tech-request@lists.sourceforge.net Subject: RE: [Dspace-general] Submitting documents as a non-administrator user Date: Thu, 25 Sep 2003 14:39:02 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Thu, 25 Sep 2003 21:39:07 -0000 Hi Scott, This sounds like an issue we had with DSpace 1.1, and is fixed in the latest version (1.1.1). If you are running 1.1.1 and are still getting this error, can you reply with a copy of the logged error? Thanks, Dave David Stuve / HP Labs Corvallis / David.Stuve@hp.com / 541-715-4106 -----Original Message----- From: Scott Yeadon [mailto:scott.yeadon@anu.edu.au] Sent: Wednesday, September 24, 2003 11:15 PM To: dspace-general@mit.edu; dspace-tech-request@lists.sourceforge.net Subject: [Dspace-general] Submitting documents as a non-administrator user Hello, At the ANU we've been performing some informal testing of DSpace, and one major issue appears to be setting up a group of non-adminstrative users who can submit documents. The DSpace documentation states that if "a collection has no e-person groups associated with any [workflow] step, submissions to that collection are installed straight into the main archive". This does not appear to be the case - non-adminstrator users do not appear to be able to store documents, but they can approve/reject submissions. For example, I have set up Community A which has the default anonymous read authorisations. Within this community is a single Collection. This Collection, as well as the default anonymous authorisations, has a group called Submitters containing two members - one an administrator user and one a non-administrator. This group has been granted all possible permissions add, read, write, remove, etc. against the Collection. There are no workflow steps for the Collection. The issue is that when logging on as the Submitter group administrator user, I can submit documents to the collection without issue, however when logged on as the Submitter group's non-adminstrator user (a basic author-type user) I get an authorisation error whenever I attempt to submit a document to the collection. In addition a log file error is generated stating that the user does not have WRITE access for the ITEM being submitted. This does not appear to be a problem related to the collection authorisation, but something at the item metadata level. Given that the item does not exist at this point as a DSpace item that can be manipulated via the DSpace GUI, I have drawn a blank as far as being able to get any further information and what I can do about this. Is this a known problem or can anyone shed any light on this problem? Thanks. Scott. _______________________________________________ Dspace-general mailing list Dspace-general@mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general From dallan_quass@hotmail.com Fri Sep 26 13:19:39 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8QHJdgH014838 for ; Fri, 26 Sep 2003 13:19:39 -0400 (EDT) Received: from hotmail.com (bay8-dav3.bay8.hotmail.com [64.4.26.107]) h8QHJcGp014303 for ; Fri, 26 Sep 2003 13:19:38 -0400 (EDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 26 Sep 2003 10:19:37 -0700 Received: from 208.187.203.167 by bay8-dav3.bay8.hotmail.com with DAV; Fri, 26 Sep 2003 17:19:37 +0000 X-Originating-IP: [208.187.203.167] X-Originating-Email: [dallan_quass@hotmail.com] From: "Dallan Quass" To: Date: Fri, 26 Sep 2003 11:26:37 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-ID: X-OriginalArrivalTime: 26 Sep 2003 17:19:37.0687 (UTC) FILETIME=[5CDFEE70:01C38452] Subject: [Dspace-general] Any archives using DSpace? X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Fri, 26 Sep 2003 17:19:40 -0000 Are any archives (in contrast to libraries) currently using or considering using DSpace? If so, can you tell me if you have needed to make any changes to the codebase? -Dallan From kenzie@MIT.EDU Sun Sep 28 22:25:21 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8T2PLgH007778 for ; Sun, 28 Sep 2003 22:25:21 -0400 (EDT) Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82])h8T2PKow026903 for ; Sun, 28 Sep 2003 22:25:20 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])h8T2PKA6029210 for ; Sun, 28 Sep 2003 22:25:20 -0400 (EDT) Received: from ADTPA.mit.edu (macknz.ne.client2.attbi.com [24.61.43.45]) )h8T2PJ5X023222 for ; Sun, 28 Sep 2003 22:25:19 -0400 (EDT) Message-Id: <5.0.2.1.2.20030928221008.035cfa60@hesiod> X-Sender: kenzie@hesiod (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Sun, 28 Sep 2003 22:23:16 -0400 To: dspace-general@MIT.EDU From: MacKenzie Smith Subject: Re: [Dspace-general] DSpace customisation In-Reply-To: <200309220911.21312.scott.yeadon@anu.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 29 Sep 2003 02:25:22 -0000 Hi Scott, The DSpace Federation project you asked about is still underway, but we've learned quite a bit on the subject since last fall. First of all, the DSpace software itself has not been extensively modified by other universities adopting it so far. Most of them have modified the UI to make it reflect their own institutional culture, and some have modified the submission process, added full-text indexing, etc. Three of the institutions we're working with are considering adding Shibboleth support over the default X.509 (certificates) or logon/password access control. The main area of technical development seems to be in modules that will be outside of DSpace itself, e.g. publishing tools or rendering applications for non-Web-native formats. The major effort at most institutions to implement DSpace as an institutional repository seems not to be in the technology at all, but rather in the definition of policies and business models that the library (or other part of the organization) needs to provide a production service to its researchers. As for avoiding upgrade problems if you make modifications, we try to keep the development process as open as possible (documenting future releases, as well as the code contribution process). The best way to ensure future compatibility is to communicate with us about the changes you're making, and offer them back to the main codebase when you're done! Hope this helps, MacKenzie/ At 09:11 AM 9/22/2003 +1000, Scott Yeadon wrote: >Hi, > >We're looking at introducing DSpace to ANU (Australian National University), >and I have just read a paper date Jan 2003 in D-Lib magazine entitled DSpace >- An OpenSource Dynamic Digital Repository, located at >http://www.dlib.org/dlib/january03/smith/01smith.html. The section entitled >"The DSpace Federation" contains a paragraph as follows: > >"In 2002, MIT formed collaborative partnerships with a small number of other >academic research institutions in the US, UK, and Canada, to address some >specific questions such as: what will it take to successfully deploy the >system at another institution? How much localization, how much customization, >and how much time and effort are needed?" > >I was wondering what sort of feedback (if any) had been received on these >topics, especially where non-trivial modifications werer required such as >more complex authorisation and low-level code modifications were required, >and how these we done to avoid issues when upgrading to future versions. > >Thanks. > >Scott. > >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general MacKenzie Smith Associate Director for Technology MIT Libraries Building 14S-208 77 Massachusetts Avenue Cambridge, MA 02139 (617)253-8184 kenzie@mit.edu From Kalbs@post.queensu.ca Mon Sep 29 12:42:36 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8TGgZgH017045 for ; Mon, 29 Sep 2003 12:42:35 -0400 (EDT) Received: from post.queensu.ca (post.QueensU.CA [130.15.126.6]) h8TGgXMf002456 for ; Mon, 29 Sep 2003 12:42:33 -0400 (EDT) Received: from cts-sk.post.queensu.ca (U8.N150.QueensU.CA [130.15.150.8]) by post.queensu.ca (8.10.1/8.10.1) with ESMTP id h8TGgW812568 for ; Mon, 29 Sep 2003 12:42:32 -0400 (EDT) Message-Id: <5.2.1.1.0.20030929123946.03c8a710@post.queensu.ca> X-Sender: kalbs@post.queensu.ca X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 29 Sep 2003 12:42:36 -0400 To: dspace-general@mit.edu From: Sam Kalb In-Reply-To: <200309291601.h8TG0fgK015283@pch.mit.edu> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_17935453==.ALT" Subject: [Dspace-general] Re: Dspace-general Digest, Vol 2, Issue 10 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 29 Sep 2003 16:42:36 -0000 --=====================_17935453==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed MacKenzie, Where can we get information about the institutions and the changes they have made - to assist some of us in setting up our DSpace projects? I am particularly interested in the addition of full-text indexing. Sam >Date: Sun, 28 Sep 2003 22:23:16 -0400 >From: MacKenzie Smith >To: dspace-general@MIT.EDU >Subject: Re: [Dspace-general] DSpace customisation >Message-ID: <5.0.2.1.2.20030928221008.035cfa60@hesiod> >In-Reply-To: <200309220911.21312.scott.yeadon@anu.edu.au> >Content-Type: text/plain; charset="us-ascii"; format=flowed >MIME-Version: 1.0 >Precedence: list >Message: 1 > >Hi Scott, > >The DSpace Federation project you asked about is still underway, >but we've learned quite a bit on the subject since last fall. First of all, >the DSpace software itself has not been extensively modified by >other universities adopting it so far. Most of them have modified the >UI to make it reflect their own institutional culture, and some have >modified the submission process, added full-text indexing, etc. >Three of the institutions we're working with are considering adding >Shibboleth support over the default X.509 (certificates) or >logon/password access control. The main area of technical >development seems to be in modules that will be outside of DSpace >itself, e.g. publishing tools or rendering applications for >non-Web-native formats. > >The major effort at most institutions to implement DSpace as >an institutional repository seems not to be in the technology >at all, but rather in the definition of policies and business models >that the library (or other part of the organization) needs to provide >a production service to its researchers. > >As for avoiding upgrade problems if you make modifications, >we try to keep the development process as open as possible >(documenting future releases, as well as the code contribution >process). The best way to ensure future compatibility is to >communicate with us about the changes you're making, and >offer them back to the main codebase when you're done! > >Hope this helps, > >MacKenzie/ > >At 09:11 AM 9/22/2003 +1000, Scott Yeadon wrote: > >Hi, > > > >We're looking at introducing DSpace to ANU (Australian National University), > >and I have just read a paper date Jan 2003 in D-Lib magazine entitled DSpace > >- An OpenSource Dynamic Digital Repository, located at > >http://www.dlib.org/dlib/january03/smith/01smith.html. The section entitled > >"The DSpace Federation" contains a paragraph as follows: > > > >"In 2002, MIT formed collaborative partnerships with a small number of other > >academic research institutions in the US, UK, and Canada, to address some > >specific questions such as: what will it take to successfully deploy the > >system at another institution? How much localization, how much > customization, > >and how much time and effort are needed?" > > > >I was wondering what sort of feedback (if any) had been received on these > >topics, especially where non-trivial modifications werer required such as > >more complex authorisation and low-level code modifications were required, > >and how these we done to avoid issues when upgrading to future versions. > > > >Thanks. > > > >Scott. > > > >_______________________________________________ > >Dspace-general mailing list > >Dspace-general@mit.edu > >http://mailman.mit.edu/mailman/listinfo/dspace-general > >MacKenzie Smith >Associate Director for Technology >MIT Libraries >Building 14S-208 >77 Massachusetts Avenue >Cambridge, MA 02139 >(617)253-8184 >kenzie@mit.edu > >------------------------------ > >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general > > >End of Dspace-general Digest, Vol 2, Issue 10 >********************************************* ---------------------------------------------------------------------- Sam Kalb Coordinator, Technical Services, Queen's University Libraries Kingston, Ontario, Canada K7L 5C4 Phone: (613) 533-2830; Fax: (613) 533-6819 Email: kalbs@post.queensu.ca URL (QTECH Web): stauffer.queensu.ca/techserv/qtechweb.html --=====================_17935453==.ALT Content-Type: text/html; charset="us-ascii" MacKenzie,
Where can we get information about the institutions and the changes they have made - to assist some of us in setting up our DSpace projects?  I am particularly interested in the addition of full-text indexing.
Sam

Date: Sun, 28 Sep 2003 22:23:16 -0400
From: MacKenzie Smith <kenzie@MIT.EDU>
To: dspace-general@MIT.EDU
Subject: Re: [Dspace-general] DSpace customisation
Message-ID: <5.0.2.1.2.20030928221008.035cfa60@hesiod>
In-Reply-To: <200309220911.21312.scott.yeadon@anu.edu.au>
Content-Type: text/plain; charset="us-ascii"; format=flowed
MIME-Version: 1.0
Precedence: list
Message: 1

Hi Scott,

The DSpace Federation project you asked about is still underway,
but we've learned quite a bit on the subject since last fall. First of all,
the DSpace software itself has not been extensively modified by
other universities adopting it so far. Most of them have modified the
UI to make it reflect their own institutional culture, and some have
modified the submission process, added full-text indexing, etc.
Three of the institutions we're working with are considering adding
Shibboleth support over the default X.509 (certificates) or
logon/password access control. The main area of technical
development seems to be in modules that will be outside of DSpace
itself, e.g. publishing tools or rendering applications for
non-Web-native formats.

The major effort at most institutions to implement DSpace as
an institutional repository seems not to be in the technology
at all, but rather in the definition of policies and business models
that the library (or other part of the organization) needs to provide
a production service to its researchers.

As for avoiding upgrade problems if you make modifications,
we try to keep the development process as open as possible
(documenting future releases, as well as the code contribution
process). The best way to ensure future compatibility is to
communicate with us about the changes you're making, and
offer them back to the main codebase when you're done!

Hope this helps,

MacKenzie/

At 09:11 AM 9/22/2003 +1000, Scott Yeadon wrote:
>Hi,
>
>We're looking at introducing DSpace to ANU (Australian National University),
>and I have just read a paper date Jan 2003 in D-Lib magazine entitled DSpace
>- An OpenSource Dynamic Digital Repository, located at
>http://www.dlib.org/dlib/january03/smith/01smith.html. The section entitled
>"The DSpace Federation" contains a paragraph as follows:
>
>"In 2002, MIT formed collaborative partnerships with a small number of other
>academic research institutions in the US, UK, and Canada, to address some
>specific questions such as: what will it take to successfully deploy the
>system at another institution? How much localization, how much customization,
>and how much time and effort are needed?"
>
>I was wondering what sort of feedback (if any) had been received on these
>topics, especially where non-trivial modifications werer required such as
>more complex authorisation and low-level code modifications were required,
>and how these we done to avoid issues when upgrading to future versions.
>
>Thanks.
>
>Scott.
>
>_______________________________________________
>Dspace-general mailing list
>Dspace-general@mit.edu
>http://mailman.mit.edu/mailman/listinfo/dspace-general

MacKenzie Smith
Associate Director for Technology
MIT Libraries
Building 14S-208
77 Massachusetts Avenue
Cambridge, MA  02139
(617)253-8184
kenzie@mit.edu

------------------------------

_______________________________________________
Dspace-general mailing list
Dspace-general@mit.edu
http://mailman.mit.edu/mailman/listinfo/dspace-general


End of Dspace-general Digest, Vol 2, Issue 10
*********************************************

----------------------------------------------------------------------
Sam Kalb                                
Coordinator, Technical Services,
Queen's University Libraries
Kingston, Ontario, Canada  K7L 5C4
Phone: (613) 533-2830; Fax: (613) 533-6819
Email: kalbs@post.queensu.ca
URL (QTECH Web): stauffer.queensu.ca/techserv/qtechweb.html --=====================_17935453==.ALT-- From Kalbs@post.queensu.ca Mon Sep 29 12:48:54 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8TGmsgH017137 for ; Mon, 29 Sep 2003 12:48:54 -0400 (EDT) Received: from post.queensu.ca (post.QueensU.CA [130.15.126.6]) h8TGmqMf005882 for ; Mon, 29 Sep 2003 12:48:52 -0400 (EDT) Received: from cts-sk.post.queensu.ca (U8.N150.QueensU.CA [130.15.150.8]) by post.queensu.ca (8.10.1/8.10.1) with ESMTP id h8TGmp817170 for ; Mon, 29 Sep 2003 12:48:51 -0400 (EDT) Message-Id: <5.2.1.1.0.20030929124843.01090db0@post.queensu.ca> X-Sender: kalbs@post.queensu.ca X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 29 Sep 2003 12:48:56 -0400 To: dspace-general@mit.edu From: Sam Kalb Subject: Re: [Dspace-general] DSpace customisation Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_18314625==.ALT" X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 29 Sep 2003 16:48:55 -0000 --=====================_18314625==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed MacKenzie, Where can we get information about the institutions and the changes they have made - to assist some of us in setting up our DSpace projects? I am particularly interested in the addition of full-text indexing. Sam >Date: Sun, 28 Sep 2003 22:23:16 -0400 >From: MacKenzie Smith >To: dspace-general@MIT.EDU >Subject: Re: [Dspace-general] DSpace customisation >Message-ID: <5.0.2.1.2.20030928221008.035cfa60@hesiod> >In-Reply-To: <200309220911.21312.scott.yeadon@anu.edu.au> >Content-Type: text/plain; charset="us-ascii"; format=flowed >MIME-Version: 1.0 >Precedence: list >Message: 1 > >Hi Scott, > >The DSpace Federation project you asked about is still underway, >but we've learned quite a bit on the subject since last fall. First of all, >the DSpace software itself has not been extensively modified by >other universities adopting it so far. Most of them have modified the >UI to make it reflect their own institutional culture, and some have >modified the submission process, added full-text indexing, etc. >Three of the institutions we're working with are considering adding >Shibboleth support over the default X.509 (certificates) or >logon/password access control. The main area of technical >development seems to be in modules that will be outside of DSpace >itself, e.g. publishing tools or rendering applications for >non-Web-native formats. > >The major effort at most institutions to implement DSpace as >an institutional repository seems not to be in the technology >at all, but rather in the definition of policies and business models >that the library (or other part of the organization) needs to provide >a production service to its researchers. > >As for avoiding upgrade problems if you make modifications, >we try to keep the development process as open as possible >(documenting future releases, as well as the code contribution >process). The best way to ensure future compatibility is to >communicate with us about the changes you're making, and >offer them back to the main codebase when you're done! > >Hope this helps, > >MacKenzie/ > >At 09:11 AM 9/22/2003 +1000, Scott Yeadon wrote: > >Hi, > > > >We're looking at introducing DSpace to ANU (Australian National University), > >and I have just read a paper date Jan 2003 in D-Lib magazine entitled DSpace > >- An OpenSource Dynamic Digital Repository, located at > >http://www.dlib.org/dlib/january03/smith/01smith.html. The section entitled > >"The DSpace Federation" contains a paragraph as follows: > > > >"In 2002, MIT formed collaborative partnerships with a small number of other > >academic research institutions in the US, UK, and Canada, to address some > >specific questions such as: what will it take to successfully deploy the > >system at another institution? How much localization, how much > customization, > >and how much time and effort are needed?" > > > >I was wondering what sort of feedback (if any) had been received on these > >topics, especially where non-trivial modifications werer required such as > >more complex authorisation and low-level code modifications were required, > >and how these we done to avoid issues when upgrading to future versions. > > > >Thanks. > > > >Scott. > > > >_______________________________________________ > >Dspace-general mailing list > >Dspace-general@mit.edu > >http://mailman.mit.edu/mailman/listinfo/dspace-general > >MacKenzie Smith >Associate Director for Technology >MIT Libraries >Building 14S-208 >77 Massachusetts Avenue >Cambridge, MA 02139 >(617)253-8184 >kenzie@mit.edu > >------------------------------ > >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general > > >End of Dspace-general Digest, Vol 2, Issue 10 >********************************************* ---------------------------------------------------------------------- Sam Kalb Coordinator, Technical Services, Queen's University Libraries Kingston, Ontario, Canada K7L 5C4 Phone: (613) 533-2830; Fax: (613) 533-6819 Email: kalbs@post.queensu.ca URL (QTECH Web): stauffer.queensu.ca/techserv/qtechweb.html --=====================_18314625==.ALT Content-Type: text/html; charset="us-ascii" MacKenzie,
Where can we get information about the institutions and the changes they have made - to assist some of us in setting up our DSpace projects?  I am particularly interested in the addition of full-text indexing.
Sam

Date: Sun, 28 Sep 2003 22:23:16 -0400
From: MacKenzie Smith <kenzie@MIT.EDU>
To: dspace-general@MIT.EDU
Subject: Re: [Dspace-general] DSpace customisation
Message-ID: <5.0.2.1.2.20030928221008.035cfa60@hesiod>
In-Reply-To: <200309220911.21312.scott.yeadon@anu.edu.au>
Content-Type: text/plain; charset="us-ascii"; format=flowed
MIME-Version: 1.0
Precedence: list
Message: 1

Hi Scott,

The DSpace Federation project you asked about is still underway,
but we've learned quite a bit on the subject since last fall. First of all,
the DSpace software itself has not been extensively modified by
other universities adopting it so far. Most of them have modified the
UI to make it reflect their own institutional culture, and some have
modified the submission process, added full-text indexing, etc.
Three of the institutions we're working with are considering adding
Shibboleth support over the default X.509 (certificates) or
logon/password access control. The main area of technical
development seems to be in modules that will be outside of DSpace
itself, e.g. publishing tools or rendering applications for
non-Web-native formats.

The major effort at most institutions to implement DSpace as
an institutional repository seems not to be in the technology
at all, but rather in the definition of policies and business models
that the library (or other part of the organization) needs to provide
a production service to its researchers.

As for avoiding upgrade problems if you make modifications,
we try to keep the development process as open as possible
(documenting future releases, as well as the code contribution
process). The best way to ensure future compatibility is to
communicate with us about the changes you're making, and
offer them back to the main codebase when you're done!

Hope this helps,

MacKenzie/

At 09:11 AM 9/22/2003 +1000, Scott Yeadon wrote:
>Hi,
>
>We're looking at introducing DSpace to ANU (Australian National University),
>and I have just read a paper date Jan 2003 in D-Lib magazine entitled DSpace
>- An OpenSource Dynamic Digital Repository, located at
>http://www.dlib.org/dlib/january03/smith/01smith.html. The section entitled
>"The DSpace Federation" contains a paragraph as follows:
>
>"In 2002, MIT formed collaborative partnerships with a small number of other
>academic research institutions in the US, UK, and Canada, to address some
>specific questions such as: what will it take to successfully deploy the
>system at another institution? How much localization, how much customization,
>and how much time and effort are needed?"
>
>I was wondering what sort of feedback (if any) had been received on these
>topics, especially where non-trivial modifications werer required such as
>more complex authorisation and low-level code modifications were required,
>and how these we done to avoid issues when upgrading to future versions.
>
>Thanks.
>
>Scott.
>
>_______________________________________________
>Dspace-general mailing list
>Dspace-general@mit.edu
>http://mailman.mit.edu/mailman/listinfo/dspace-general

MacKenzie Smith
Associate Director for Technology
MIT Libraries
Building 14S-208
77 Massachusetts Avenue
Cambridge, MA  02139
(617)253-8184
kenzie@mit.edu

------------------------------

_______________________________________________
Dspace-general mailing list
Dspace-general@mit.edu
http://mailman.mit.edu/mailman/listinfo/dspace-general


End of Dspace-general Digest, Vol 2, Issue 10
*********************************************

----------------------------------------------------------------------
Sam Kalb                                
Coordinator, Technical Services,
Queen's University Libraries
Kingston, Ontario, Canada  K7L 5C4
Phone: (613) 533-2830; Fax: (613) 533-6819
Email: kalbs@post.queensu.ca
URL (QTECH Web): stauffer.queensu.ca/techserv/qtechweb.html --=====================_18314625==.ALT-- From emurphy1@email.arizona.edu Mon Sep 29 14:42:16 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8TIgGgH019208 for ; Mon, 29 Sep 2003 14:42:16 -0400 (EDT) Received: from smtpgate.email.arizona.edu (deagol.email.Arizona.EDU [128.196.133.142])h8TIgCUj025456 for ; Mon, 29 Sep 2003 14:42:12 -0400 (EDT) Received: from ILCD45 (unknown [150.135.164.51]) by smtpgate.email.arizona.edu (Postfix) with ESMTP id 6EF46529A7 for ; Mon, 29 Sep 2003 11:42:11 -0700 (MST) From: "Ed Murphy" To: Date: Mon, 29 Sep 2003 11:42:11 -0700 Organization: The University of Arizona Message-ID: <000001c386b9$64cc2cc0$33a48796@ilc.arizona.edu> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C3867E.B86D54C0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new at email.arizona.edu X-Mailman-Approved-At: Mon, 29 Sep 2003 15:00:07 -0400 Subject: [Dspace-general] DSpace v1.2 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list Reply-To: emurphy1@email.arizona.edu List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 29 Sep 2003 18:42:17 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C3867E.B86D54C0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello, I was excited to see the next release of DSpace, v1.2, is being planned. We are very interested in the enhancement to allow one item to be stored in multiple collections. Is there a general target date for the release of DSpace v1.2 yet? If so, what is it? Thanks, Ed Murphy Applications Systems Analyst, Sr. Integrated Learning Center The University of Arizona Tucson, Arizona ------=_NextPart_000_0001_01C3867E.B86D54C0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
Hello,
 
I was = excited to see=20 the next release of DSpace, v1.2, is being planned.  We are very = interested=20 in the enhancement to allow one item to be stored in multiple = collections. =20 Is there a general target date for the release of DSpace v1.2 yet?  = If so,=20 what is it?
 
Thanks,
 
Ed=20 Murphy
 
Applications Systems=20 Analyst, Sr.
Integrated Learning=20 Center
The = University of=20 Arizona
Tucson,=20 Arizona
------=_NextPart_000_0001_01C3867E.B86D54C0-- From mjordan@sfu.ca Mon Sep 29 15:20:45 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8TJKigH020311 for ; Mon, 29 Sep 2003 15:20:44 -0400 (EDT) Received: from rm-rstar.sfu.ca (rm-rstar.sfu.ca [142.58.120.21]) h8TJKUUj009202 for ; Mon, 29 Sep 2003 15:20:30 -0400 (EDT) Received: from fraser.sfu.ca (daemon@fraser.sfu.ca [142.58.101.25]) h8TJKSY8012819 for ; Mon, 29 Sep 2003 12:20:28 -0700 (PDT) Received: (from mjordan@localhost) by fraser.sfu.ca (8.12.9/8.12.3/SFU-6.0C) id h8TJKSN2002657 for dspace-general@mit.edu; Mon, 29 Sep 2003 12:20:28 -0700 (PDT) Date: Mon, 29 Sep 2003 12:20:27 -0700 From: Mark Jordan To: dspace-general@mit.edu Message-ID: <20030929192027.GL8366@sfu.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: [Dspace-general] Nothing showing up in Authorization Tool X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 29 Sep 2003 19:20:45 -0000 Hello, Perhaps I'm missing some crucial step, so please feel free to tell me to RTFM a bit more closely if that's the case. I've set up a test community and collection, I've created a sumbitter group for the collection, but when I go into the Authorization Tool to give this group ad permission, nothing is showing up. I am selecting the collection title and clicking on the Edit button. The same symptoms happen when I use the Authorizations tool to modify community policies -- I select the community name and click on Edit policies, and a blank page shows up. The only lines in my dspace.log are ones like "2003-09-23 14:41:02,064 INFO org.dspace.app.webui.servlet.RetrieveServlet @ anonymous:session_id=FFFC1375F04446FC82223844069AF244:view_bitstream:bitstream_id=2", and I know the Anonymous group has read permissions on this collection since it's showing up in the public user interface. Anyone else experience the same thing? If so, what's the solution? Mark Mark Jordan Acting Coordinator of Library Systems W.A.C. Bennett Library, Simon Fraser University Burnaby, British Columbia, V5A 1S6, Canada Phone (604) 291 5753 / Fax (604) 291 3023 mjordan@sfu.ca / http://www.sfu.ca/~mjordan/ From david.stuve@hp.com Mon Sep 29 15:42:02 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8TJg2gH020702 for ; Mon, 29 Sep 2003 15:42:02 -0400 (EDT) Received: from palrel11.hp.com (palrel11.hp.com [156.153.255.246]) h8TJfvUj004001 for ; Mon, 29 Sep 2003 15:41:57 -0400 (EDT) Received: from xparelay1.ptp.hp.com (xparelay1.ptp.hp.com [15.1.28.62]) by palrel11.hp.com (Postfix) with ESMTP id B091B1C005A8; Mon, 29 Sep 2003 12:41:56 -0700 (PDT) Received: from xcorbh2.cv.hp.com (xcorbh2.cv.hp.com [15.7.113.190]) by xparelay1.ptp.hp.com (Postfix) with ESMTP id 8B0E41004B93; Mon, 29 Sep 2003 12:41:56 -0700 (PDT) Received: by xcorbh2.cv.hp.com with Internet Mail Service (5.5.2655.55) id ; Mon, 29 Sep 2003 12:41:56 -0700 Message-ID: <5755325D04C5834187459E1E17D81F6F0834F04C@xcor01.cv.hp.com> From: "STUVE,DAVID (HP-Corvallis,ex1)" To: "'Mark Jordan'" , dspace-general@mit.edu Subject: RE: [Dspace-general] Nothing showing up in Authorization Tool Date: Mon, 29 Sep 2003 12:41:55 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 29 Sep 2003 19:42:03 -0000 Hi Mark, This sounds like a problem that DSpace 1.1 had with creating policy entries that were NULLs (no value in the database table), especially when people would select "create policy" and then hit the browser's back button. The problem is tough to diagnose because for some reason those errors are quietly swallowed, generating no log entry and no error page - simply a blank screen. 1) Are you running DSpace 1.1 or 1.1.1? If 1.1, an upgrade will help. 2) If upgrading doesn't help, the next easy answer is to use psql or another Postgres tool and delete the null rows from the policy table. 3) The problem has never made it past #1 and #2. :-) But if you're the lucky first one, we can help more. Dave David Stuve / HP Labs Corvallis / David.Stuve@hp.com / 541-715-4106 -----Original Message----- From: Mark Jordan [mailto:mjordan@sfu.ca] Sent: Monday, September 29, 2003 12:20 PM To: dspace-general@mit.edu Subject: [Dspace-general] Nothing showing up in Authorization Tool Hello, Perhaps I'm missing some crucial step, so please feel free to tell me to RTFM a bit more closely if that's the case. I've set up a test community and collection, I've created a sumbitter group for the collection, but when I go into the Authorization Tool to give this group ad permission, nothing is showing up. I am selecting the collection title and clicking on the Edit button. The same symptoms happen when I use the Authorizations tool to modify community policies -- I select the community name and click on Edit policies, and a blank page shows up. The only lines in my dspace.log are ones like "2003-09-23 14:41:02,064 INFO org.dspace.app.webui.servlet.RetrieveServlet @ anonymous:session_id=FFFC1375F04446FC82223844069AF244:view_bitstream:bitstre am_id=2", and I know the Anonymous group has read permissions on this collection since it's showing up in the public user interface. Anyone else experience the same thing? If so, what's the solution? Mark Mark Jordan Acting Coordinator of Library Systems W.A.C. Bennett Library, Simon Fraser University Burnaby, British Columbia, V5A 1S6, Canada Phone (604) 291 5753 / Fax (604) 291 3023 mjordan@sfu.ca / http://www.sfu.ca/~mjordan/ _______________________________________________ Dspace-general mailing list Dspace-general@mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general From mjordan@sfu.ca Mon Sep 29 16:24:12 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8TKOBgH021908 for ; Mon, 29 Sep 2003 16:24:12 -0400 (EDT) Received: from rm-rstar.sfu.ca (rm-rstar.sfu.ca [142.58.120.21]) h8TKNvgm002654 for ; Mon, 29 Sep 2003 16:23:58 -0400 (EDT) Received: from fraser.sfu.ca (daemon@fraser.sfu.ca [142.58.101.25]) h8TKNCY8012643; Mon, 29 Sep 2003 13:23:12 -0700 (PDT) Received: (from mjordan@localhost) by fraser.sfu.ca (8.12.9/8.12.3/SFU-6.0C) id h8TKNC4e014565; Mon, 29 Sep 2003 13:23:12 -0700 (PDT) Date: Mon, 29 Sep 2003 13:23:12 -0700 From: Mark Jordan To: "STUVE,DAVID (HP-Corvallis,ex1)" Subject: Re: [Dspace-general] Nothing showing up in Authorization Tool Message-ID: <20030929202311.GN8366@sfu.ca> References: <5755325D04C5834187459E1E17D81F6F0834F04C@xcor01.cv.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5755325D04C5834187459E1E17D81F6F0834F04C@xcor01.cv.hp.com> User-Agent: Mutt/1.4.1i cc: dspace-general@mit.edu X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 29 Sep 2003 20:24:12 -0000 Hi Dave, Sorry I didn't include my version in my original email: it's 1.1. I downloaded dspace-1.1.1.tar.gz, and following the updating instructions at http://dspace.org/technology/system-docs/update.html#11_111, I ran ant -Dconfig=/dspace/config/dspace.cfg update and got the error Buildfile: build.xml update: BUILD FAILED /tmp/dspace-1.1.1-source/build.xml:184: /tmp/dspace-1.1.1-source/build/classes not found. Total time: 0 seconds Line 184 of build.xml specifies basedir="${basedir}/build/classes", basedir being defined previously as ".". When I run a 'find . -name classes' at the top of the untarred dspace-1.1.1-source directory, I don't find anything. The .jar files in the update are in the dspace-1.1.1-source/lib directory. Should I modify build.xml to use that directory? Sorry to introduce a new problem, Mark On Mon, Sep 29, 2003 at 12:41:55PM -0700, STUVE,DAVID (HP-Corvallis,ex1) wrote: > Hi Mark, > > This sounds like a problem that DSpace 1.1 had with creating policy entries > that were NULLs (no value in the database table), especially when people > would select "create policy" and then hit the browser's back button. The > problem is tough to diagnose because for some reason those errors are > quietly swallowed, generating no log entry and no error page - simply a > blank screen. > > 1) Are you running DSpace 1.1 or 1.1.1? If 1.1, an upgrade will help. > 2) If upgrading doesn't help, the next easy answer is to use psql or another > Postgres tool and delete the null rows from the policy table. > 3) The problem has never made it past #1 and #2. :-) But if you're the > lucky first one, we can help more. > > Dave > > David Stuve / HP Labs Corvallis / David.Stuve@hp.com / 541-715-4106 > > -----Original Message----- > From: Mark Jordan [mailto:mjordan@sfu.ca] > Sent: Monday, September 29, 2003 12:20 PM > To: dspace-general@mit.edu > Subject: [Dspace-general] Nothing showing up in Authorization Tool > > > Hello, > > Perhaps I'm missing some crucial step, so please feel free to tell me to > RTFM a bit more closely if that's the case. > > I've set up a test community and collection, I've created a sumbitter group > for the collection, but when I go into the > Authorization Tool to give this group ad permission, nothing is showing up. > I am selecting the collection title and clicking > on the Edit button. > > The same symptoms happen when I use the Authorizations tool to modify > community policies -- I select the community name and click on Edit > policies, and a blank page shows up. > > The only lines in my dspace.log are ones like "2003-09-23 14:41:02,064 INFO > org.dspace.app.webui.servlet.RetrieveServlet @ > anonymous:session_id=FFFC1375F04446FC82223844069AF244:view_bitstream:bitstre > am_id=2", and I know the Anonymous group has read > permissions on this collection since it's showing up in the public user > interface. > > Anyone else experience the same thing? If so, what's the solution? > > Mark > > > Mark Jordan > Acting Coordinator of Library Systems > W.A.C. Bennett Library, Simon Fraser University > Burnaby, British Columbia, V5A 1S6, Canada > Phone (604) 291 5753 / Fax (604) 291 3023 > mjordan@sfu.ca / http://www.sfu.ca/~mjordan/ > > > _______________________________________________ > Dspace-general mailing list > Dspace-general@mit.edu > http://mailman.mit.edu/mailman/listinfo/dspace-general -- Mark Jordan Acting Coordinator of Library Systems W.A.C. Bennett Library, Simon Fraser University Burnaby, British Columbia, V5A 1S6, Canada Phone (604) 291 5753 / Fax (604) 291 3023 mjordan@sfu.ca / http://www.sfu.ca/~mjordan/ From rrodgers@MIT.EDU Mon Sep 29 17:09:36 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8TL9ZgH023038 for ; Mon, 29 Sep 2003 17:09:35 -0400 (EDT) Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82])h8TL9LDw001837; Mon, 29 Sep 2003 17:09:29 -0400 (EDT) Received: from manawatu-mail-centre.mit.edu (MANAWATU-MAIL-CENTRE.MIT.EDU [18.7.7.71])h8TL5xp8009337; Mon, 29 Sep 2003 17:06:03 -0400 (EDT) Received: from dspace-03.mit.edu (DSPACE-03.MIT.EDU [18.51.2.148]) ) h8TL3PV6028207; Mon, 29 Sep 2003 17:03:25 -0400 (EDT) Received: (from rrodgers@localhost) by dspace-03.mit.edu (8.9.3) id RAA16246; Mon, 29 Sep 2003 17:03:24 -0400 Subject: Re: [Dspace-general] DSpace v1.2 From: Richard Rodgers To: emurphy1@email.arizona.edu In-Reply-To: <000001c386b9$64cc2cc0$33a48796@ilc.arizona.edu> References: <000001c386b9$64cc2cc0$33a48796@ilc.arizona.edu> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 29 Sep 2003 17:03:24 -0400 Message-Id: <1064869404.12403.83.camel@dspace-03.mit.edu> Mime-Version: 1.0 cc: dspace-general@MIT.EDU X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 29 Sep 2003 21:09:36 -0000 Hi Ed: We haven't fixed on an exact date yet, since we are still in the process of characterizing some of the functionality that we recently announced. But we hope to release 1.2 this calendar year. Regards, Richard Rodgers DSpace Federation Systems Manager On Mon, 2003-09-29 at 14:42, Ed Murphy wrote: > Hello, > > I was excited to see the next release of DSpace, v1.2, is being > planned. We are very interested in the enhancement to allow one item > to be stored in multiple collections. Is there a general target date > for the release of DSpace v1.2 yet? If so, what is it? > > Thanks, > > Ed Murphy > > Applications Systems Analyst, Sr. > Integrated Learning Center > The University of Arizona > Tucson, Arizona > ---- > > _______________________________________________ > Dspace-general mailing list > Dspace-general@mit.edu > http://mailman.mit.edu/mailman/listinfo/dspace-general From kenzie@MIT.EDU Mon Sep 29 17:57:13 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8TLvDgH023994 for ; Mon, 29 Sep 2003 17:57:13 -0400 (EDT) Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82])h8TLvCDu028940 for ; Mon, 29 Sep 2003 17:57:12 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])h8TLvBom014182 for ; Mon, 29 Sep 2003 17:57:11 -0400 (EDT) Received: from ADTPA.mit.edu (ADTPA.MIT.EDU [18.51.1.92]) ) h8TLvApl009067 for ; Mon, 29 Sep 2003 17:57:11 -0400 (EDT) Message-Id: <5.0.2.1.2.20030929175216.034e2898@hesiod> X-Sender: kenzie@hesiod (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Mon, 29 Sep 2003 17:55:07 -0400 To: dspace-general@MIT.EDU From: MacKenzie Smith Subject: Re: [Dspace-general] DSpace customisation In-Reply-To: <5.2.1.1.0.20030929123946.03c8a710@post.queensu.ca> References: <200309291601.h8TG0fgK015283@pch.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 29 Sep 2003 21:57:14 -0000 At 12:42 PM 9/29/2003 -0400, Sam Kalb wrote: >Where can we get information about the institutions and the changes they >have made - to assist some of us in setting up our DSpace projects? I am >particularly interested in the addition of full-text indexing. The institution that mentioned they were implementing this was Drexel, in Philadelphia. I haven't confirmed it. But we're also planning to add an option for full-text indexing with Lucene in the next release (1.2, due later this year, we hope). If someone else out there has worked on full-text indexing in DSpace hopefully they'll speak up and let us know! And feel free to ask on the dspace-tech list too, which is where most of the developers are lurking... Regards, MacKenzie/ MacKenzie Smith Associate Director for Technology MIT Libraries Building 14S-208 77 Massachusetts Avenue Cambridge, MA 02139 (617)253-8184 kenzie@mit.edu From gabriela.mircea@utoronto.ca Tue Sep 30 11:27:37 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8UFRbgH005131 for ; Tue, 30 Sep 2003 11:27:37 -0400 (EDT) Received: from bureau8.utcc.utoronto.ca (bureau8.utcc.utoronto.ca [128.100.132.18])h8UFRYRW021767 for ; Tue, 30 Sep 2003 11:27:35 -0400 (EDT) Received: from utl-193-94.library.utoronto.ca ([142.150.193.94] EHLO utoronto.ca ident: IDENT-NOT-QUERIED [port 2336]) by bureau8.utcc.utoronto.ca with ESMTP id <25400-9931>; Tue, 30 Sep 2003 11:27:27 -0400 Message-ID: <3F79A0D2.A8D539BF@utoronto.ca> Date: Tue, 30 Sep 2003 11:27:14 -0400 From: Gabriela Mircea Organization: University of Toronto Library X-Mailer: Mozilla 4.79 [en] (WinNT; U) X-Accept-Language: en,ro MIME-Version: 1.0 To: Sam Kalb Subject: Re: [Dspace-general] DSpace customisation References: <5.2.1.1.0.20030929124843.01090db0@post.queensu.ca> Content-Type: multipart/alternative; boundary="------------022C725645BE363E465AC27C" cc: dspace-general@mit.edu X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 30 Sep 2003 15:27:38 -0000 --------------022C725645BE363E465AC27C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Sam, We would be happy to assist you to set up your DSpace. We made some changes to DSpace to suit our needs, and we also worked on full-text indexing (with help from Drexel). It may not be the best way to do it, but the full-text search is now working for pdf, doc, txt, htm, html, and xls on our test server and it is perfectly integrated with the advanced search tool. You can try it at http://tort.library.utoronto.ca:8080/advanced-search, and choose "contents" from the drop-down menu. I look forward to our collaboration. Gabriela Mircea Information Technology Services Robarts Library, 130 St. George St. Toronto, ON, Canada, M5S 1A5 416 946 0114 Sam Kalb wrote: > MacKenzie, > Where can we get information about the institutions and the changes > they have made - to assist some of us in setting up our DSpace > projects? I am particularly interested in the addition of full-text > indexing. > Sam > > >> Date: Sun, 28 Sep 2003 22:23:16 -0400 >> From: MacKenzie Smith >> To: dspace-general@MIT.EDU >> Subject: Re: [Dspace-general] DSpace customisation >> Message-ID: <5.0.2.1.2.20030928221008.035cfa60@hesiod> >> In-Reply-To: <200309220911.21312.scott.yeadon@anu.edu.au> >> Content-Type: text/plain; charset="us-ascii"; format=flowed >> MIME-Version: 1.0 >> Precedence: list >> Message: 1 >> >> Hi Scott, >> >> The DSpace Federation project you asked about is still underway, >> but we've learned quite a bit on the subject since last fall. First >> of all, >> the DSpace software itself has not been extensively modified by >> other universities adopting it so far. Most of them have modified >> the >> UI to make it reflect their own institutional culture, and some have >> >> modified the submission process, added full-text indexing, etc. >> Three of the institutions we're working with are considering adding >> Shibboleth support over the default X.509 (certificates) or >> logon/password access control. The main area of technical >> development seems to be in modules that will be outside of DSpace >> itself, e.g. publishing tools or rendering applications for >> non-Web-native formats. >> >> The major effort at most institutions to implement DSpace as >> an institutional repository seems not to be in the technology >> at all, but rather in the definition of policies and business models >> >> that the library (or other part of the organization) needs to >> provide >> a production service to its researchers. >> >> As for avoiding upgrade problems if you make modifications, >> we try to keep the development process as open as possible >> (documenting future releases, as well as the code contribution >> process). The best way to ensure future compatibility is to >> communicate with us about the changes you're making, and >> offer them back to the main codebase when you're done! >> >> Hope this helps, >> >> MacKenzie/ >> >> At 09:11 AM 9/22/2003 +1000, Scott Yeadon wrote: >> >Hi, >> > >> >We're looking at introducing DSpace to ANU (Australian National >> University), >> >and I have just read a paper date Jan 2003 in D-Lib magazine >> entitled DSpace >> >- An OpenSource Dynamic Digital Repository, located at >> >http://www.dlib.org/dlib/january03/smith/01smith.html. The section >> entitled >> >"The DSpace Federation" contains a paragraph as follows: >> > >> >"In 2002, MIT formed collaborative partnerships with a small number >> of other >> >academic research institutions in the US, UK, and Canada, to >> address some >> >specific questions such as: what will it take to successfully >> deploy the >> >system at another institution? How much localization, how much >> customization, >> >and how much time and effort are needed?" >> > >> >I was wondering what sort of feedback (if any) had been received on >> these >> >topics, especially where non-trivial modifications werer required >> such as >> >more complex authorisation and low-level code modifications were >> required, >> >and how these we done to avoid issues when upgrading to future >> versions. >> > >> >Thanks. >> > >> >Scott. >> > >> >_______________________________________________ >> >Dspace-general mailing list >> >Dspace-general@mit.edu >> >http://mailman.mit.edu/mailman/listinfo/dspace-general >> >> MacKenzie Smith >> Associate Director for Technology >> MIT Libraries >> Building 14S-208 >> 77 Massachusetts Avenue >> Cambridge, MA 02139 >> (617)253-8184 >> kenzie@mit.edu >> >> ------------------------------ >> >> _______________________________________________ >> Dspace-general mailing list >> Dspace-general@mit.edu >> http://mailman.mit.edu/mailman/listinfo/dspace-general >> >> >> End of Dspace-general Digest, Vol 2, Issue 10 >> ********************************************* > > > ---------------------------------------------------------------------Sam > Kalb Coordinator, Technical Services,Queen's University > LibrariesKingston, Ontario, Canada K7L 5C4Phone: (613) 533-2830; Fax: > (613) 533-6819Email: kalbs@post.queensu.caURL (QTECH Web): > stauffer.queensu.ca/techserv/qtechweb.html > > ---------------------------------------------------------------- > _______________________________________________ > Dspace-general mailing list > Dspace-general@mit.edu > http://mailman.mit.edu/mailman/listinfo/dspace-general > --------------022C725645BE363E465AC27C Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Sam,

We would be happy to assist you to set up your DSpace. We made some changes to DSpace to suit our needs, and we also worked on full-text indexing (with help from Drexel). It may not be the best way to do it, but the full-text search is now working for  pdf, doc, txt, htm, html, and xls on our test server and it is perfectly integrated with the advanced search tool. You can try it at http://tort.library.utoronto.ca:8080/advanced-search, and choose "contents" from the drop-down menu.

I look forward to our collaboration.
 

Gabriela Mircea
Information Technology Services
Robarts Library, 130 St. George St.
Toronto, ON, Canada, M5S 1A5
416 946 0114
 

Sam Kalb wrote:

MacKenzie,
Where can we get information about the institutions and the changes they have made - to assist some of us in setting up our DSpace projects?  I am particularly interested in the addition of full-text indexing.
Sam
 
Date: Sun, 28 Sep 2003 22:23:16 -0400
From: MacKenzie Smith <kenzie@MIT.EDU>
To: dspace-general@MIT.EDU
Subject: Re: [Dspace-general] DSpace customisation
Message-ID: <5.0.2.1.2.20030928221008.035cfa60@hesiod>
In-Reply-To: <200309220911.21312.scott.yeadon@anu.edu.au>
Content-Type: text/plain; charset="us-ascii"; format=flowed
MIME-Version: 1.0
Precedence: list
Message: 1

Hi Scott,

The DSpace Federation project you asked about is still underway,
but we've learned quite a bit on the subject since last fall. First of all,
the DSpace software itself has not been extensively modified by
other universities adopting it so far. Most of them have modified the
UI to make it reflect their own institutional culture, and some have
modified the submission process, added full-text indexing, etc.
Three of the institutions we're working with are considering adding
Shibboleth support over the default X.509 (certificates) or
logon/password access control. The main area of technical
development seems to be in modules that will be outside of DSpace
itself, e.g. publishing tools or rendering applications for
non-Web-native formats.

The major effort at most institutions to implement DSpace as
an institutional repository seems not to be in the technology
at all, but rather in the definition of policies and business models
that the library (or other part of the organization) needs to provide
a production service to its researchers.

As for avoiding upgrade problems if you make modifications,
we try to keep the development process as open as possible
(documenting future releases, as well as the code contribution
process). The best way to ensure future compatibility is to
communicate with us about the changes you're making, and
offer them back to the main codebase when you're done!

Hope this helps,

MacKenzie/

At 09:11 AM 9/22/2003 +1000, Scott Yeadon wrote:
>Hi,
>
>We're looking at introducing DSpace to ANU (Australian National University),
>and I have just read a paper date Jan 2003 in D-Lib magazine entitled DSpace
>- An OpenSource Dynamic Digital Repository, located at
>http://www.dlib.org/dlib/january03/smith/01smith.html. The section entitled
>"The DSpace Federation" contains a paragraph as follows:
>
>"In 2002, MIT formed collaborative partnerships with a small number of other
>academic research institutions in the US, UK, and Canada, to address some
>specific questions such as: what will it take to successfully deploy the
>system at another institution? How much localization, how much customization,
>and how much time and effort are needed?"
>
>I was wondering what sort of feedback (if any) had been received on these
>topics, especially where non-trivial modifications werer required such as
>more complex authorisation and low-level code modifications were required,
>and how these we done to avoid issues when upgrading to future versions.
>
>Thanks.
>
>Scott.
>
>_______________________________________________
>Dspace-general mailing list
>Dspace-general@mit.edu
>http://mailman.mit.edu/mailman/listinfo/dspace-general

MacKenzie Smith
Associate Director for Technology
MIT Libraries
Building 14S-208
77 Massachusetts Avenue
Cambridge, MA  02139
(617)253-8184
kenzie@mit.edu

------------------------------

_______________________________________________
Dspace-general mailing list
Dspace-general@mit.edu
http://mailman.mit.edu/mailman/listinfo/dspace-general
 

End of Dspace-general Digest, Vol 2, Issue 10
*********************************************

----------------------------------------------------------------------Sam Kalb Coordinator, Technical Services,Queen's University LibrariesKingston, Ontario, Canada  K7L 5C4Phone: (613) 533-2830; Fax: (613) 533-6819Email: kalbs@post.queensu.caURL (QTECH Web): stauffer.queensu.ca/techserv/qtechweb.html 
_______________________________________________
Dspace-general mailing list
Dspace-general@mit.edu
http://mailman.mit.edu/mailman/listinfo/dspace-general

 
 
  --------------022C725645BE363E465AC27C-- From margretb@MIT.EDU Tue Sep 30 16:50:27 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8UKoRgH029513 for ; Tue, 30 Sep 2003 16:50:27 -0400 (EDT) Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82])h8UKoOnc004257; Tue, 30 Sep 2003 16:50:26 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])h8UKo9Z9007774; Tue, 30 Sep 2003 16:50:10 -0400 (EDT) Received: from dspace-01.mit.edu ([66.114.225.45]) )h8UKo7jX013017; Tue, 30 Sep 2003 16:50:08 -0400 (EDT) Message-Id: <5.2.1.1.2.20030930150051.02312980@po10.mit.edu> X-Sender: margretb@po10.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Tue, 30 Sep 2003 15:10:36 -0400 To: dspace-general@MIT.EDU, dspace-tech@sourceforge.lists.net From: Margret Branschofsky Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Dspace-general] Improvements to Administrator's User Interface X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 30 Sep 2003 20:50:27 -0000 Hello, One of the new features we are adding to the next version of DSpace is an improved Administrator's User Interface. I am going to be writing up the feature definition for this, so please send me suggestions for improving the admin. interface, your pet peeves, functions you would like to add...etc. This is your chance to have an impact on the tools you use. Margret Margret Branschofsky DSpace User Support Manager Digital Library Research Group Bldg. 14S-M24 (617)253-1293 margretb@mit.edu http://dspace.mit.edu From scott.yeadon@anu.edu.au Tue Sep 30 19:48:10 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h8UNm9gH015119 for ; Tue, 30 Sep 2003 19:48:10 -0400 (EDT) Received: from anu.edu.au (anumail4.anu.edu.au [150.203.2.44]) h8UNm78R020027 for ; Tue, 30 Sep 2003 19:48:08 -0400 (EDT) Received: from anumail.anu.edu.au (anumail.anu.edu.au [150.203.2.90]) by anu.edu.au (8.12.10/8.12.10) with ESMTP id h8UNm5IB007603; Wed, 1 Oct 2003 09:48:05 +1000 (EST) Received: from sts59101.anu.edu.au (sts59101.anu.edu.au [150.203.59.101]) by anumail.anu.edu.au (8.12.10/8.12.10) with ESMTP id h8UNm5Xf029504; Wed, 1 Oct 2003 09:48:05 +1000 (EST) Content-Type: text/plain; charset="us-ascii" From: Scott Yeadon To: mjordan@sfu.ca Date: Wed, 1 Oct 2003 09:47:09 +1000 User-Agent: KMail/1.4.1 MIME-Version: 1.0 Message-Id: <200310010947.09893.scott.yeadon@anu.edu.au> X-Sender: scott.yeadon@anu.edu.au X-Sender-Domain: anu.edu.au X-Spam-Status: Scanned X-Spam-Score: (-0.4) X-Spam-Tests: USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.36 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id h8UNm9gH015119 cc: dspace-general@mit.edu Subject: [Dspace-general] failed 1.1.1 build due to missing build/classes directory X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list Reply-To: scott.yeadon@anu.edu.au List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 30 Sep 2003 23:48:11 -0000 Mark, I had this problem, however by manually creating the directories the problem is resolved. {basedir} represents the directory you unzipped the install package to e.g. /tmp/dspace-1.1.1-source/build/classes The directory is basically a working directory for the installation process. Scott. From analice@dsi.uminho.pt Wed Oct 1 04:51:18 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h918pIgH025933 for ; Wed, 1 Oct 2003 04:51:18 -0400 (EDT) Received: from smtp.netcabo.pt (smtp.netcabo.pt [212.113.174.9]) h918pH9S008435 for ; Wed, 1 Oct 2003 04:51:17 -0400 (EDT) Received: from dsi.uminho.pt ([213.22.132.26]) by smtp.netcabo.pt with Microsoft SMTPSVC(5.0.2195.6713); Wed, 1 Oct 2003 09:46:34 +0100 Date: Wed, 1 Oct 2003 09:49:45 +0100 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; charset=US-ASCII; format=flowed From: Ana Alice Baptista To: dspace-general@mit.edu Content-Transfer-Encoding: 7bit Message-Id: <34A0DF38-F3EC-11D7-9206-000393CBB65E@dsi.uminho.pt> X-Mailer: Apple Mail (2.552) X-OriginalArrivalTime: 01 Oct 2003 08:46:34.0091 (UTC) FILETIME=[847CB3B0:01C387F8] Subject: [Dspace-general] User studies on DSpace X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 01 Oct 2003 08:51:19 -0000 Dear all, My name is Ana Baptista and I'm emailing you from Universidade do Minho, Portugal. We are implementing DSpace here at Uminho with (what we believe) the first Portuguese version of DSpace. We are now feeding the system with Thesis and Dissertations from the whole university. We are also starting to involve communities and we have started with 6 of them which will make available other scientific documents such as articles and reports. We hope to open the doors to our repository by the end of Octoober. We have some students willing to do research using DSpace. In particular one of them is interested in studying the users that are producers of scholarly resources stored in DSpace. With this in mind, I would like to ask you the following: - Are you doing similar studies in your intitutions? It seems to me that, if there are, all these researchers could share experiences that would benefit all of them. In particular for us it would be very helpful to know similar studies in other cultural contexts. - Do you know of any international organization willing to sponsor these kind of studies? I'm looking forward to hearing from you. Best regards, Ana Baptista From SGibbons@library.rochester.edu Wed Oct 1 14:58:14 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h91IwEgH005221 for ; Wed, 1 Oct 2003 14:58:14 -0400 (EDT) Received: from library.rochester.edu (rcl.lib.rochester.edu [128.151.244.122]) h91IwDSs014190 for ; Wed, 1 Oct 2003 14:58:13 -0400 (EDT) Received: from RCL-MTA by library.rochester.edu with Novell_GroupWise; Wed, 01 Oct 2003 15:02:55 -0400 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.2 Date: Wed, 01 Oct 2003 15:02:52 -0400 From: "Susan Gibbons" To: , Subject: Re: [Dspace-general] User studies on DSpace Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=_C7998ECF.137214F1" X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 01 Oct 2003 18:58:15 -0000 This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=_C7998ECF.137214F1 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Dear Ana: At the University of Rochester in New York we just received a federally funded grant to study how different disciplines work with grey literature (tech reports, pre-prints, conference papers, etc.) and make modifications to DSpace based on our findings. I'd be glad to email you a copy of the grant proposal, if you are interested. We'd be glad to share anything we learn from our studies and hope you will do the same with yours. Best wishes, Susan Gibbons Director, Digital Library Initiatives River Campus Libraries University of Rochester 585-275-6320 sgibbons@library.rochester.edu >>> Ana Alice Baptista 10/01/03 04:49AM >>> Dear all, My name is Ana Baptista and I'm emailing you from Universidade do Minho, Portugal. We are implementing DSpace here at Uminho with (what we believe) the first Portuguese version of DSpace. We are now feeding the system with Thesis and Dissertations from the whole university. We are also starting to involve communities and we have started with 6 of them which will make available other scientific documents such as articles and reports. We hope to open the doors to our repository by the end of Octoober. We have some students willing to do research using DSpace. In particular one of them is interested in studying the users that are producers of scholarly resources stored in DSpace. With this in mind, I would like to ask you the following: - Are you doing similar studies in your intitutions? It seems to me that, if there are, all these researchers could share experiences that would benefit all of them. In particular for us it would be very helpful to know similar studies in other cultural contexts. - Do you know of any international organization willing to sponsor these kind of studies? I'm looking forward to hearing from you. Best regards, Ana Baptista _______________________________________________ Dspace-general mailing list Dspace-general@mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general --=_C7998ECF.137214F1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Description: HTML
Dear Ana:
 
At the University of Rochester in New York we just received a federally funded grant to study how different disciplines work with grey literature (tech reports, pre-prints, conference papers, etc.) and make modifications to DSpace based on our findings.  I'd be glad to email you a copy of the grant proposal, if you are interested.
 
We'd be glad to share anything we learn from our studies and hope you will do the same with yours.
 
Best wishes,
 
Susan Gibbons
Director, Digital Library Initiatives
River Campus Libraries
University of Rochester
585-275-6320
sgibbons@library.rochester.edu

>>> Ana Alice Baptista <analice@dsi.uminho.pt> 10/01/03 04:49AM >>>
Dear all,

My name is Ana Baptista and I'm emailing you from Universidade do
Minho, Portugal.
We are implementing DSpace here at Uminho with (what we believe) the
first Portuguese version of DSpace. We are now feeding the system with
Thesis and Dissertations from the whole university. We are also
starting to involve communities and we have started with 6 of them
which will make available other scientific documents such as articles
and reports. We hope to open the doors to our repository by the end of
Octoober.

We have some students willing to do research using DSpace. In
particular one of them is interested in studying the users that are
producers of scholarly resources stored in DSpace. With this in mind, I
would like to ask you the following:

- Are you doing similar studies in your intitutions? It seems to me
that, if there are, all these researchers could share experiences that
would benefit all of them. In particular for us it would be very
helpful to know similar studies in other cultural contexts.

- Do you know of any international organization willing to sponsor
these kind of studies?

I'm looking forward to hearing from you.

Best regards,

Ana Baptista

_______________________________________________
Dspace-general mailing list
Dspace-general@mit.edu
http://mailman.mit.edu/mailman/listinfo/dspace-general
--=_C7998ECF.137214F1-- From tull.9@osu.edu Fri Oct 3 12:43:02 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h93Gh2gH020427 for ; Fri, 3 Oct 2003 12:43:02 -0400 (EDT) Received: from mail-mta5.service.ohio-state.edu (mail-mta5.service.ohio-state.edu [128.146.216.45])h93Gh02P014796 for ; Fri, 3 Oct 2003 12:43:00 -0400 (EDT) Received: from MAI105BS1.osu.edu (mai105bs1.lib.ohio-state.edu [128.146.9.207]) by mail-mta5.service.ohio-state.edu (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTP id <0HM6006RYX3O2X@mail-mta5.service.ohio-state.edu> for Dspace-general@mit.edu; Fri, 03 Oct 2003 12:43:00 -0400 (EDT) Date: Fri, 03 Oct 2003 11:47:00 -0400 From: Laura Tull Subject: Re: [Dspace-general] Improvements to Administrator's User Interface In-reply-to: <5.2.1.1.2.20030930150051.02312980@po10.mit.edu> X-Sender: tull.9@pop.service.ohio-state.edu To: Dspace-general@mit.edu Message-id: <4.3.2.7.2.20031003113956.02f538c0@pop.service.ohio-state.edu> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Content-type: multipart/alternative; boundary="Boundary_(ID_IAsoXf5kt+RpkVObkweLng)" X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Fri, 03 Oct 2003 16:43:03 -0000 --Boundary_(ID_IAsoXf5kt+RpkVObkweLng) Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT Margret, I'd like to see the ability to search for an item by title or author as well as handle. I never know the handle when I go into the Admin mode and then I have to go back and search for the item to find it. Can I assume there will be a help page for the Admin interface similar to the user's interface that will explain how to create and delete community, collection and set policies for them, etc. It seems that I ran into some issues with the order in which you had to do things. At 03:10 PM 9/30/2003 -0400, you wrote: >Hello, > >One of the new features we are adding to the next version of DSpace is an >improved Administrator's User Interface. I am going to be writing up the >feature definition for this, so please send me suggestions for improving >the admin. interface, your pet peeves, functions you would like to >add...etc. This is your chance to have an impact on the tools you use. > >Margret > >Margret Branschofsky >DSpace User Support Manager >Digital Library Research Group >Bldg. 14S-M24 >(617)253-1293 >margretb@mit.edu >http://dspace.mit.edu >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general *********************************** Laura Tull Systems Librarian Ohio State University Libraries 1858 Neil Avenue Mall Columbus OH 43210-1286 Phone: 614-247-6459 Fax: 614-292-7859 Email: tull.9@osu.edu *********************************** --Boundary_(ID_IAsoXf5kt+RpkVObkweLng) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT Margret,

I'd like to see the ability to search for an item by title or author as well as handle.  I never know the handle when I go into the Admin mode and then I have to go back and search for the item to find it.

Can I assume there will be a help page for the Admin interface similar to the user's interface that will explain how to create and delete community, collection and set policies for them, etc.  It seems that I ran into some issues with the order in which you had to do things. 



At 03:10 PM 9/30/2003 -0400, you wrote:
Hello,

One of the new features we are adding to the next version of DSpace is an improved Administrator's User Interface.  I am going to be writing up the feature definition for this, so please send me suggestions for improving the admin. interface, your pet peeves, functions you would like to add...etc.  This is your chance to have an impact on the tools you use.

Margret

Margret Branschofsky
DSpace User Support Manager
Digital Library Research Group
Bldg. 14S-M24
(617)253-1293
margretb@mit.edu
http://dspace.mit.edu
_______________________________________________
Dspace-general mailing list
Dspace-general@mit.edu
http://mailman.mit.edu/mailman/listinfo/dspace-general



***********************************
Laura Tull
Systems Librarian
Ohio State University Libraries
1858 Neil Avenue Mall
Columbus OH 43210-1286
Phone:  614-247-6459
Fax:  614-292-7859
Email:  tull.9@osu.edu
*********************************** --Boundary_(ID_IAsoXf5kt+RpkVObkweLng)-- From Ilene.Strongin-Garry@ichotelsgroup.com Sat Oct 4 12:02:42 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h94G2ggH003151 for ; Sat, 4 Oct 2003 12:02:42 -0400 (EDT) Received: from bhratlsmtp02.hiw.com (bhratlsmtp02.sixcontinentshotels.com [165.2.141.7])h94G2fih029297 for ; Sat, 4 Oct 2003 12:02:41 -0400 (EDT) Received: from 165.2.177.152 by bhratlsmtp02.hiw.com (InterScan E-Mail VirusWall NT); Sat, 04 Oct 2003 12:02:40 -0400 (Eastern Daylight Time) Received: by atlhub02.hiw.com with Internet Mail Service (5.5.2653.19) id ; Sat, 4 Oct 2003 12:02:48 -0400 Message-ID: <4201FDFD444BC84190DEF632181EB38F2AB612@bhratlexg03.hiw.com> From: "Strongin-Garry, Ilene (IHG)" To: "'dspace-general@mit.edu'" Date: Sat, 4 Oct 2003 12:02:36 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Dspace-general] RE: Dspace-general Digest, Vol 3, Issue 3 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Sat, 04 Oct 2003 16:02:43 -0000 I agree with this suggestion 100%%%%%%% -----Original Message----- From: dspace-general-request@mit.edu [mailto:dspace-general-request@mit.edu] Sent: Saturday, October 04, 2003 12:01 PM To: dspace-general@mit.edu Subject: Dspace-general Digest, Vol 3, Issue 3 Send Dspace-general mailing list submissions to dspace-general@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@mit.edu You can reach the person managing the list at dspace-general-owner@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: Improvements to Administrator's User Interface (Laura Tull) ---------------------------------------------------------------------- Date: Fri, 03 Oct 2003 11:47:00 -0400 From: Laura Tull To: Dspace-general@mit.edu Subject: Re: [Dspace-general] Improvements to Administrator's User Interface Message-ID: <4.3.2.7.2.20031003113956.02f538c0@pop.service.ohio-state.edu> In-Reply-To: <5.2.1.1.2.20030930150051.02312980@po10.mit.edu> Content-Type: multipart/mixed; boundary="------------InterScan_NT_MIME_Boundary" MIME-Version: 1.0 Precedence: list Message: 1 --------------InterScan_NT_MIME_Boundary Content-Type: multipart/alternative; boundary="Boundary_(ID_IAsoXf5kt+RpkVObkweLng)" --Boundary_(ID_IAsoXf5kt+RpkVObkweLng) Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT Margret, I'd like to see the ability to search for an item by title or author as well as handle. I never know the handle when I go into the Admin mode and then I have to go back and search for the item to find it. Can I assume there will be a help page for the Admin interface similar to the user's interface that will explain how to create and delete community, collection and set policies for them, etc. It seems that I ran into some issues with the order in which you had to do things. At 03:10 PM 9/30/2003 -0400, you wrote: >Hello, > >One of the new features we are adding to the next version of DSpace is an >improved Administrator's User Interface. I am going to be writing up the >feature definition for this, so please send me suggestions for improving >the admin. interface, your pet peeves, functions you would like to >add...etc. This is your chance to have an impact on the tools you use. > >Margret > >Margret Branschofsky >DSpace User Support Manager >Digital Library Research Group >Bldg. 14S-M24 >(617)253-1293 >margretb@mit.edu >http://dspace.mit.edu >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general *********************************** Laura Tull Systems Librarian Ohio State University Libraries 1858 Neil Avenue Mall Columbus OH 43210-1286 Phone: 614-247-6459 Fax: 614-292-7859 Email: tull.9@osu.edu *********************************** --Boundary_(ID_IAsoXf5kt+RpkVObkweLng) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT Margret,

I'd like to see the ability to search for an item by title or author as well as handle.  I never know the handle when I go into the Admin mode and then I have to go back and search for the item to find it.

Can I assume there will be a help page for the Admin interface similar to the user's interface that will explain how to create and delete community, collection and set policies for them, etc.  It seems that I ran into some issues with the order in which you had to do things. 



At 03:10 PM 9/30/2003 -0400, you wrote:
Hello,

One of the new features we are adding to the next version of DSpace is an improved Administrator's User Interface.  I am going to be writing up the feature definition for this, so please send me suggestions for improving the admin. interface, your pet peeves, functions you would like to add...etc.  This is your chance to have an impact on the tools you use.

Margret

Margret Branschofsky
DSpace User Support Manager
Digital Library Research Group
Bldg. 14S-M24
(617)253-1293
margretb@mit.edu
http://dspace.mit.edu
_______________________________________________
Dspace-general mailing list
Dspace-general@mit.edu
http://mailman.mit.edu/mailman/listinfo/dspace-general< /font>



***********************************
Laura Tull
Systems Librarian
Ohio State University Libraries
1858 Neil Avenue Mall
Columbus OH 43210-1286
Phone:  614-247-6459
Fax:  614-292-7859
Email:  tull.9@osu.edu
*********************************** --Boundary_(ID_IAsoXf5kt+RpkVObkweLng)-- ------------------------------ _______________________________________________ Dspace-general mailing list Dspace-general@mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general End of Dspace-general Digest, Vol 3, Issue 3 ******************************************** --------------InterScan_NT_MIME_Boundary-- From Rachel.Lee@ucpress.edu Sat Oct 4 12:10:01 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h94GA0gH003193 for ; Sat, 4 Oct 2003 12:10:00 -0400 (EDT) Received: from ucpress.edu (mail.ucpress.edu [63.197.93.16]) h94G9xih001390 for ; Sat, 4 Oct 2003 12:09:59 -0400 (EDT) Date: Sat, 4 Oct 2003 08:44:32 PST Message-Id: <10310040844.AA00229@ucpress.edu> From: "Rachel Lee" To: dspace-general@mit.edu X-Mailer: Precedence: bulk Subject: [Dspace-general] automated response X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Reply-To: Rachel.Lee@ucpress.edu List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Sat, 04 Oct 2003 16:10:01 -0000 I am away from the office until 14th October. I will respond to your message when I return. Urgent enquiries *only* should be addressed to rebekah.darksmith@ucpress.edu. thank you. From margretb@MIT.EDU Tue Oct 7 10:03:06 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h97E36gH010949 for ; Tue, 7 Oct 2003 10:03:06 -0400 (EDT) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72])h97E357a011352 for ; Tue, 7 Oct 2003 10:03:05 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])h97E34Lj028855 for ; Tue, 7 Oct 2003 10:03:04 -0400 (EDT) Received: from dspace-01.mit.edu (DSPACE-01.MIT.EDU [18.51.2.146]) (authenticated bits=0) (User authenticated as margretb@ATHENA.MIT.EDU)h97E33jX011942 for ; Tue, 7 Oct 2003 10:03:04 -0400 (EDT) Message-Id: <5.2.1.1.2.20031007100229.02140cb8@po10.mit.edu> X-Sender: margretb@po10.mit.edu X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Tue, 07 Oct 2003 10:02:48 -0400 To: dspace-general@MIT.EDU From: Margret Branschofsky Subject: Fwd: Re: [Dspace-general] Improvements to Administrator's User Interface Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 07 Oct 2003 14:03:07 -0000 >Date: Tue, 07 Oct 2003 10:01:45 -0400 >To: Jewel Ward >From: Margret Branschofsky >Subject: Re: [Dspace-general] Improvements to Administrator's User Interface > >Have you all seen the Administration User Interface Documentation which >comes with the system documentation? If so, is this documentation not >adequate? (http://dspace.org/technology/system-docs/admin-ui.html ). > >Margret > >At 03:37 PM 10/6/2003 -0600, Jewel Ward wrote: >>At 11:47 AM 10/3/2003 -0400, you wrote: >> >>>Can I assume there will be a help page for the Admin interface similar >>>to the user's interface that will explain how to create and delete >>>community, collection and set policies for them, etc. It seems that I >>>ran into some issues with the order in which you had to do things. >> >>Margret, >> >>I had the same problem. I'll try to think of things that are more >>specific and send them to you. >> >>Regards, >> >>Jewel >> >> >> >>>*********************************** >>>Laura Tull >>>Systems Librarian >>>Ohio State University Libraries >>>1858 Neil Avenue Mall >>>Columbus OH 43210-1286 >>>Phone: 614-247-6459 >>>Fax: 614-292-7859 >>>Email: tull.9@osu.edu >>>*********************************** >>>_______________________________________________ >>>Dspace-general mailing list >>>Dspace-general@mit.edu >>>http://mailman.mit.edu/mailman/listinfo/dspace-general >> >>-- >>Jewel H. Ward >>Graduate Research Assistant, Post-master's >>Los Alamos National Laboratory >>Research Library >>(505) 664-0368 >>jewelw@lanl.gov From jqj@darkwing.uoregon.edu Tue Oct 7 14:28:14 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h97ISEgH015775 for ; Tue, 7 Oct 2003 14:28:14 -0400 (EDT) Received: from darkwing.uoregon.edu (darkwing.uoregon.edu [128.223.142.13]) h97ISC1b020547 for ; Tue, 7 Oct 2003 14:28:13 -0400 (EDT) Received: from TWIG (twig.uoregon.edu [128.223.86.56]) by darkwing.uoregon.edu (8.12.10/8.12.10) with SMTP id h97ISBE9001399 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Tue, 7 Oct 2003 11:28:12 -0700 (PDT) From: "JQ Johnson" To: Date: Tue, 7 Oct 2003 11:28:12 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-Spam-Status: No, hits=-100.9 required=5.0tests=IN_REP_TO,MSGID_GOOD_EXCHANGE,USER_IN_WHITELISTversion=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <5.2.1.1.2.20031007100229.02140cb8@po10.mit.edu> Importance: Normal Subject: [Dspace-general] RE: Improvements to Administrator's User Interface X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 07 Oct 2003 18:28:14 -0000 A couple of suggestions, mixing minor UI changes with significant implementation changes: 1/ the whole ePeople system needs to be rethought and made more modular. At many institutions we want to tie into our central directory (LDAP, radius, or whatever) and give all of and only our people ePerson accounts, or at least to allow such people privileged access (perhaps what's needed is the notion of named guests, or a set of system-wide roles such as {guest,normal,communitycreator,superuser}). We need an easy way to associate LDAP-derived membership in departments with DSpace-specific groups that give access to the corresponding communities. Just looking at the current admin interface (/admin/edit-epeople), We need better tools for searching the list of ePeople ("Browse ePeople" may work for a few hundred ePeople, but not if you have 20,000) and modifying their properties both individually and as groups. We may need to more clearly separate system-level authorization from system-level authentication. 2/ We need an easy way to delegate responsibilities for community management to community-specific gatekeepers who could create collections, add members to groups specific to that community, etc. This implies that groups as presently implemented may be too broad. I think we need to have an access control mechanism that more directly ties into communities and collections. DSpace started this process with the special-semantics groups like COLLECTION_3_WFSTEP_1. But this should be carried much further. At a minimum, creation of a collection should automatically create the corresponding COLLECTION_n_ADD and add it to the ACL for the collection. Probably such a new group should inherit some membership from a community-level group. If groups as presently conceptualized continue, it should be possible to delegate ability to change membership in a particular group -- a non-administrator gatekeeper for a particular collection, for instance, should be able to modify the membership of COLLECTION_n_* groups. It's perhaps symptomatic of the problem that the admin documentation contains language errors. For instance, in http://dspace.org/technology/system-docs/admin-ui.html we read that "Permissions do not 'commute'" when the actual concept is that permissions do not inherit or are not transitive. But note that DEFAULT_*_* properties do sort of inherit! The "Communities/Collections" admin interface is quite usable as is for small numbers of collections, but doesn't work well if you have 200 communities and 500 collections. Creating a collection should automatically create a COLLECTION_n_ADD group for it. Probably lots of other changes to the collection creation/editing form would be useful as well. E.g. "Item template" seems ill thought out. 3/ items: we desperately need a way for a site to customize the submission process and change the metadata collected. I don't think we need to change the actual metadata schema; qDC is adequate. 4/ the admin interface for Items needs a better search facility. I don't want to have to think in terms of handles or internal IDs. 5/ Multiple versions of an item: unless a better item versioning system can be implemented soon, we need a way to allow unprivileged users to add bitstreams to an existing record (and to record and display timestamps on a per-bitstream basis). This might be the owner modifying a record, or might be people in some collection-specific group. 6/ Item authorizations in the current admin interface (Authorize->Manage An Item's Policies) are completely obscure. The notion of "Bundles" isn't reified anywhere else in the user interface. The fact that bundles have numbers and not names is a symptom of the problem. General observation: for power users it might be better instead of writing a bunch of custom UI code to simply expose the database more directly. If I could download a .csv file with the metadata for an item or the list of members in a group, edit it using Excel or whatever, then upload the resulting file, that would be a lot more flexible than the current approach. Absent such a feature, I'm tempted to connect to my DSpace database directly from Access or DBtools or some similar graphical SQL editor, but that is high-risk. JQ Johnson Office: 115F Knight Library Academic Education Coordinator mailto:jqj@darkwing.uoregon.edu 1299 University of Oregon phone: 1-541-346-1746; -3485 fax Eugene, OR 97403-1299 http://darkwing.uoregon.edu/~jqj/ From Ilene.Strongin-Garry@ichotelsgroup.com Tue Oct 7 15:41:21 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h97JfKgH016601 for ; Tue, 7 Oct 2003 15:41:21 -0400 (EDT) Received: from bhratlsmtp02.hiw.com (bhratlsmtp02.sixcontinentshotels.com [165.2.141.7])h97JfK1b005868 for ; Tue, 7 Oct 2003 15:41:20 -0400 (EDT) Received: from 165.2.177.152 by bhratlsmtp02.hiw.com (InterScan E-Mail VirusWall NT); Tue, 07 Oct 2003 15:41:18 -0400 (Eastern Daylight Time) Received: by atlhub02.hiw.com with Internet Mail Service (5.5.2653.19) id ; Tue, 7 Oct 2003 15:41:30 -0400 Message-ID: <4201FDFD444BC84190DEF632181EB38F2AB636@bhratlexg03.hiw.com> From: "Strongin-Garry, Ilene (IHG)" To: "'dspace-general@mit.edu'" Date: Tue, 7 Oct 2003 15:41:12 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Dspace-general] RE: Dspace-general Digest, Vol 3, Issue 5 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 07 Oct 2003 19:41:22 -0000 Other enhancements I'd like to see include: When submitting an item, you are asked to submit to a collection. However, once you choose the collection it cannot be changed without having to re-enter the entire amount of metadata and files. I would like to have the option to correct my collection choice. Secondly, it would be great to be able to add additional files to an item once it's in DSpace. I know you can edit metadata, but it would be great to be able to add files in case something has been accidentally left off or found later after an item has been submitted. -----Original Message----- From: dspace-general-request@mit.edu [mailto:dspace-general-request@mit.edu] Sent: Tuesday, October 07, 2003 12:01 PM To: dspace-general@mit.edu Subject: Dspace-general Digest, Vol 3, Issue 5 Send Dspace-general mailing list submissions to dspace-general@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@mit.edu You can reach the person managing the list at dspace-general-owner@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. Fwd: Re: [Dspace-general] Improvements to Administrator's User Interface (Margret Branschofsky) ---------------------------------------------------------------------- Date: Tue, 07 Oct 2003 10:02:48 -0400 From: Margret Branschofsky To: dspace-general@MIT.EDU Subject: Fwd: Re: [Dspace-general] Improvements to Administrator's User Interface Message-ID: <5.2.1.1.2.20031007100229.02140cb8@po10.mit.edu> Content-Type: text/plain; charset="us-ascii"; format=flowed MIME-Version: 1.0 Precedence: list Message: 1 >Date: Tue, 07 Oct 2003 10:01:45 -0400 >To: Jewel Ward >From: Margret Branschofsky >Subject: Re: [Dspace-general] Improvements to Administrator's User Interface > >Have you all seen the Administration User Interface Documentation which >comes with the system documentation? If so, is this documentation not >adequate? (http://dspace.org/technology/system-docs/admin-ui.html ). > >Margret > >At 03:37 PM 10/6/2003 -0600, Jewel Ward wrote: >>At 11:47 AM 10/3/2003 -0400, you wrote: >> >>>Can I assume there will be a help page for the Admin interface similar >>>to the user's interface that will explain how to create and delete >>>community, collection and set policies for them, etc. It seems that I >>>ran into some issues with the order in which you had to do things. >> >>Margret, >> >>I had the same problem. I'll try to think of things that are more >>specific and send them to you. >> >>Regards, >> >>Jewel >> >> >> >>>*********************************** >>>Laura Tull >>>Systems Librarian >>>Ohio State University Libraries >>>1858 Neil Avenue Mall >>>Columbus OH 43210-1286 >>>Phone: 614-247-6459 >>>Fax: 614-292-7859 >>>Email: tull.9@osu.edu >>>*********************************** >>>_______________________________________________ >>>Dspace-general mailing list >>>Dspace-general@mit.edu >>>http://mailman.mit.edu/mailman/listinfo/dspace-general >> >>-- >>Jewel H. Ward >>Graduate Research Assistant, Post-master's >>Los Alamos National Laboratory >>Research Library >>(505) 664-0368 >>jewelw@lanl.gov ------------------------------ _______________________________________________ Dspace-general mailing list Dspace-general@mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general End of Dspace-general Digest, Vol 3, Issue 5 ******************************************** From scott.yeadon@anu.edu.au Wed Oct 8 03:08:53 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h9878qgH021366 for ; Wed, 8 Oct 2003 03:08:53 -0400 (EDT) Received: from anu.edu.au (anumail4.anu.edu.au [150.203.2.44]) h9876VDk006867; Wed, 8 Oct 2003 03:06:32 -0400 (EDT) Received: from anumail.anu.edu.au (anumail.anu.edu.au [150.203.2.90]) by anu.edu.au (8.12.10/8.12.10) with ESMTP id h9876TIB008752; Wed, 8 Oct 2003 17:06:29 +1000 (EST) Received: from sts59101.anu.edu.au (sts59101.anu.edu.au [150.203.59.101]) by anumail.anu.edu.au (8.12.10/8.12.10) with ESMTP id h9876TXf026903; Wed, 8 Oct 2003 17:06:29 +1000 (EST) Content-Type: text/plain; charset="us-ascii" From: Scott Yeadon To: margretb@MIT.EDU Date: Wed, 8 Oct 2003 17:05:16 +1000 User-Agent: KMail/1.4.1 MIME-Version: 1.0 Message-Id: <200310081705.16171.scott.yeadon@anu.edu.au> X-Sender: scott.yeadon@anu.edu.au X-Sender-Domain: anu.edu.au X-Spam-Status: Scanned X-Spam-Score: (0.1) X-Spam-Tests: CLICK_BELOW,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.36 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id h9878qgH021366 cc: dspace-general@MIT.EDU cc: dspace-tech@sourceforge.lists.net Subject: [Dspace-general] RE: Improvements to Administrator's User Interface X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list Reply-To: scott.yeadon@anu.edu.au List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 08 Oct 2003 07:08:53 -0000 Hi Margaret, Below are our suggestions that ANU would like to see. They are ordered from most important to least important. 1. Administration at Community and collection levels For our implementation we want our users to establish and manage their own communities and collections without being able to change communities and collections which they don't have administrator access for. Currently there is only an overall administrator and we need an additional administrator layer. 2. Allow searching on items using metadata searches rather than handles Item handles really don't mean much to users, when looking for an item metadata such as titles and authors is used. 3. Metadata should be configurable at community, collection and item levels. Currently only one standard metadata set is available across a single DSpace instance. We would like to be able to allow the creation of multiple simultaneous metadata schemas. These schemas should be able to be attached at a community, collection and item level. The submission forms can then generated dynmically using the metadata schema. We would like to also be able to create default metadata schema and forms. For example when a user selected a type of "image" then default metadata schema and forms could be assigned for the submission process rather than the user having to select or define a schema, or work their way through irrelevant metadata forms. 4. If clicking on the "Add EPerson" button a person is automatically added. There is no cancel operation on the Add EPerson screen. The new EPerson should not be added unless the administrator explicitly clicks on the "Save Edits" button. 5. Would be good to be able to edit items from the Edit collection screen. This should allow users to edit items belonging to the collection being added. Currently you have to go out of the collection to edit items that belong to it. 6. Navigation within multiscreen operations. The breadcrumb links do not always represent where you are in the function hierarchy meaning the back button needs to be used on some occasions. As there appears to be problems when using the back button, the breadcrumbs need to be complete and session state information needs to be maintained so that the back button can be used. 7. When editing authorisations it would speed things up if you could select more than one access type. For example if I want a Group to have Read, Write, Add access, I should be able to select all thes in one operation rather than have to perform three separate operations. 8. On the community, collection, item authorisation pages it would be useful to be able to click on the group and have a popup displaying which EPersons belonged to the group. Currently you have to go out and back into the Group maintenance page to see this. 9. Similar to above, when viewing the groups it would be useful to be able to see which collections the groups had access to. 10. Look at performance improvements for update/delete queries, for example by using threads or asynchronous background transactions while the user moves to the next screen. This may also be an issue for drawing of screens for example when a repository has a large number of collections, groups, etc rendering may become slow. This could be improved through filtering what is displayed by providing search and browse facilities similar to what is currently in place for collections. 11. Consistent placement and use of buttons would be useful to avoid confusion. For example, on some screens you need to make a change and also click an "Update" button whereas on others you only need to make a change for it to take effect. On several screens where multiple operations may be performed (such as metadata, bitstream registries) the "New" button is placed at the bottom of the screen, where it may be better to put it at the top since the page returns to the top once the change has been applied. 12. Would be good to be able to apply advanced wildcard authorisation policies to collections, not just items and bitstreams. 13. Many of the tables run off the screen making it impossible to view the information without scrolling left-to-right. If the table cannot be made to fit on the screen it would be useful to allow columns to be hidden (similar to the hide/show functionality of tools like MS Excel/Access) Hope that helps. If you would like any clarification on these requests, please feel free to contact me. Thanks. Scott. From Ilene.Strongin-Garry@ichotelsgroup.com Wed Oct 8 14:09:51 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h98I9ogH007859 for ; Wed, 8 Oct 2003 14:09:50 -0400 (EDT) Received: from bhratlsmtp02.hiw.com (bhratlsmtp02.sixcontinentshotels.com [165.2.141.7])h98I9l6I019466 for ; Wed, 8 Oct 2003 14:09:47 -0400 (EDT) Received: from 165.2.177.152 by bhratlsmtp02.hiw.com (InterScan E-Mail VirusWall NT); Wed, 08 Oct 2003 14:09:45 -0400 (Eastern Daylight Time) Received: by atlhub02.hiw.com with Internet Mail Service (5.5.2653.19) id ; Wed, 8 Oct 2003 14:09:58 -0400 Message-ID: <4201FDFD444BC84190DEF632181EB38F2AB669@bhratlexg03.hiw.com> From: "Strongin-Garry, Ilene (IHG)" To: "'dspace-general@mit.edu'" Date: Wed, 8 Oct 2003 14:09:46 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Dspace-general] RE: Dspace-general Digest, Vol 3, Issue 6 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 08 Oct 2003 18:09:51 -0000 I agree with the need for integrating epeople with other outside sources like Microsoft Outlook. We are a work population in the 1000's and once more people start using DSpace, the Epeople system will become very time consuming. -----Original Message----- From: dspace-general-request@mit.edu [mailto:dspace-general-request@mit.edu] Sent: Wednesday, October 08, 2003 12:04 PM To: dspace-general@mit.edu Subject: Dspace-general Digest, Vol 3, Issue 6 Send Dspace-general mailing list submissions to dspace-general@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@mit.edu You can reach the person managing the list at dspace-general-owner@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: Improvements to Administrator's User Interface (JQ Johnson) 2. RE: Dspace-general Digest, Vol 3, Issue 5 (Strongin-Garry, Ilene (IHG)) 3. RE: Improvements to Administrator's User Interface (Scott Yeadon) ---------------------------------------------------------------------- Date: Tue, 7 Oct 2003 11:28:12 -0700 From: "JQ Johnson" To: Subject: [Dspace-general] RE: Improvements to Administrator's User Interface Message-ID: In-Reply-To: <5.2.1.1.2.20031007100229.02140cb8@po10.mit.edu> Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: list Message: 1 A couple of suggestions, mixing minor UI changes with significant implementation changes: 1/ the whole ePeople system needs to be rethought and made more modular. At many institutions we want to tie into our central directory (LDAP, radius, or whatever) and give all of and only our people ePerson accounts, or at least to allow such people privileged access (perhaps what's needed is the notion of named guests, or a set of system-wide roles such as {guest,normal,communitycreator,superuser}). We need an easy way to associate LDAP-derived membership in departments with DSpace-specific groups that give access to the corresponding communities. Just looking at the current admin interface (/admin/edit-epeople), We need better tools for searching the list of ePeople ("Browse ePeople" may work for a few hundred ePeople, but not if you have 20,000) and modifying their properties both individually and as groups. We may need to more clearly separate system-level authorization from system-level authentication. 2/ We need an easy way to delegate responsibilities for community management to community-specific gatekeepers who could create collections, add members to groups specific to that community, etc. This implies that groups as presently implemented may be too broad. I think we need to have an access control mechanism that more directly ties into communities and collections. DSpace started this process with the special-semantics groups like COLLECTION_3_WFSTEP_1. But this should be carried much further. At a minimum, creation of a collection should automatically create the corresponding COLLECTION_n_ADD and add it to the ACL for the collection. Probably such a new group should inherit some membership from a community-level group. If groups as presently conceptualized continue, it should be possible to delegate ability to change membership in a particular group -- a non-administrator gatekeeper for a particular collection, for instance, should be able to modify the membership of COLLECTION_n_* groups. It's perhaps symptomatic of the problem that the admin documentation contains language errors. For instance, in http://dspace.org/technology/system-docs/admin-ui.html we read that "Permissions do not 'commute'" when the actual concept is that permissions do not inherit or are not transitive. But note that DEFAULT_*_* properties do sort of inherit! The "Communities/Collections" admin interface is quite usable as is for small numbers of collections, but doesn't work well if you have 200 communities and 500 collections. Creating a collection should automatically create a COLLECTION_n_ADD group for it. Probably lots of other changes to the collection creation/editing form would be useful as well. E.g. "Item template" seems ill thought out. 3/ items: we desperately need a way for a site to customize the submission process and change the metadata collected. I don't think we need to change the actual metadata schema; qDC is adequate. 4/ the admin interface for Items needs a better search facility. I don't want to have to think in terms of handles or internal IDs. 5/ Multiple versions of an item: unless a better item versioning system can be implemented soon, we need a way to allow unprivileged users to add bitstreams to an existing record (and to record and display timestamps on a per-bitstream basis). This might be the owner modifying a record, or might be people in some collection-specific group. 6/ Item authorizations in the current admin interface (Authorize->Manage An Item's Policies) are completely obscure. The notion of "Bundles" isn't reified anywhere else in the user interface. The fact that bundles have numbers and not names is a symptom of the problem. General observation: for power users it might be better instead of writing a bunch of custom UI code to simply expose the database more directly. If I could download a .csv file with the metadata for an item or the list of members in a group, edit it using Excel or whatever, then upload the resulting file, that would be a lot more flexible than the current approach. Absent such a feature, I'm tempted to connect to my DSpace database directly from Access or DBtools or some similar graphical SQL editor, but that is high-risk. JQ Johnson Office: 115F Knight Library Academic Education Coordinator mailto:jqj@darkwing.uoregon.edu 1299 University of Oregon phone: 1-541-346-1746; -3485 fax Eugene, OR 97403-1299 http://darkwing.uoregon.edu/~jqj/ ------------------------------ Date: Tue, 7 Oct 2003 15:41:12 -0400 From: "Strongin-Garry, Ilene (IHG)" To: "'dspace-general@mit.edu'" Subject: [Dspace-general] RE: Dspace-general Digest, Vol 3, Issue 5 Message-ID: <4201FDFD444BC84190DEF632181EB38F2AB636@bhratlexg03.hiw.com> Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Precedence: list Message: 2 Other enhancements I'd like to see include: When submitting an item, you are asked to submit to a collection. However, once you choose the collection it cannot be changed without having to re-enter the entire amount of metadata and files. I would like to have the option to correct my collection choice. Secondly, it would be great to be able to add additional files to an item once it's in DSpace. I know you can edit metadata, but it would be great to be able to add files in case something has been accidentally left off or found later after an item has been submitted. -----Original Message----- From: dspace-general-request@mit.edu [mailto:dspace-general-request@mit.edu] Sent: Tuesday, October 07, 2003 12:01 PM To: dspace-general@mit.edu Subject: Dspace-general Digest, Vol 3, Issue 5 Send Dspace-general mailing list submissions to dspace-general@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@mit.edu You can reach the person managing the list at dspace-general-owner@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. Fwd: Re: [Dspace-general] Improvements to Administrator's User Interface (Margret Branschofsky) ---------------------------------------------------------------------- Date: Tue, 07 Oct 2003 10:02:48 -0400 From: Margret Branschofsky To: dspace-general@MIT.EDU Subject: Fwd: Re: [Dspace-general] Improvements to Administrator's User Interface Message-ID: <5.2.1.1.2.20031007100229.02140cb8@po10.mit.edu> Content-Type: text/plain; charset="us-ascii"; format=flowed MIME-Version: 1.0 Precedence: list Message: 1 >Date: Tue, 07 Oct 2003 10:01:45 -0400 >To: Jewel Ward >From: Margret Branschofsky >Subject: Re: [Dspace-general] Improvements to Administrator's User Interface > >Have you all seen the Administration User Interface Documentation which >comes with the system documentation? If so, is this documentation not >adequate? (http://dspace.org/technology/system-docs/admin-ui.html ). > >Margret > >At 03:37 PM 10/6/2003 -0600, Jewel Ward wrote: >>At 11:47 AM 10/3/2003 -0400, you wrote: >> >>>Can I assume there will be a help page for the Admin interface similar >>>to the user's interface that will explain how to create and delete >>>community, collection and set policies for them, etc. It seems that I >>>ran into some issues with the order in which you had to do things. >> >>Margret, >> >>I had the same problem. I'll try to think of things that are more >>specific and send them to you. >> >>Regards, >> >>Jewel >> >> >> >>>*********************************** >>>Laura Tull >>>Systems Librarian >>>Ohio State University Libraries >>>1858 Neil Avenue Mall >>>Columbus OH 43210-1286 >>>Phone: 614-247-6459 >>>Fax: 614-292-7859 >>>Email: tull.9@osu.edu >>>*********************************** >>>_______________________________________________ >>>Dspace-general mailing list >>>Dspace-general@mit.edu >>>http://mailman.mit.edu/mailman/listinfo/dspace-general >> >>-- >>Jewel H. Ward >>Graduate Research Assistant, Post-master's >>Los Alamos National Laboratory >>Research Library >>(505) 664-0368 >>jewelw@lanl.gov ------------------------------ _______________________________________________ Dspace-general mailing list Dspace-general@mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general End of Dspace-general Digest, Vol 3, Issue 5 ******************************************** ------------------------------ Date: Wed, 8 Oct 2003 17:05:16 +1000 From: Scott Yeadon To: margretb@MIT.EDU Cc: dspace-general@MIT.EDU Cc: dspace-tech@sourceforge.lists.net Subject: [Dspace-general] RE: Improvements to Administrator's User Interface Message-ID: <200310081705.16171.scott.yeadon@anu.edu.au> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: list Reply-To: scott.yeadon@anu.edu.au Message: 3 Hi Margaret, Below are our suggestions that ANU would like to see. They are ordered from most important to least important. 1. Administration at Community and collection levels For our implementation we want our users to establish and manage their own communities and collections without being able to change communities and collections which they don't have administrator access for. Currently there is only an overall administrator and we need an additional administrator layer. 2. Allow searching on items using metadata searches rather than handles Item handles really don't mean much to users, when looking for an item metadata such as titles and authors is used. 3. Metadata should be configurable at community, collection and item levels. Currently only one standard metadata set is available across a single DSpace instance. We would like to be able to allow the creation of multiple simultaneous metadata schemas. These schemas should be able to be attached at a community, collection and item level. The submission forms can then generated dynmically using the metadata schema. We would like to also be able to create default metadata schema and forms. For example when a user selected a type of "image" then default metadata schema and forms could be assigned for the submission process rather than the user having to select or define a schema, or work their way through irrelevant metadata forms. 4. If clicking on the "Add EPerson" button a person is automatically added. There is no cancel operation on the Add EPerson screen. The new EPerson should not be added unless the administrator explicitly clicks on the "Save Edits" button. 5. Would be good to be able to edit items from the Edit collection screen. This should allow users to edit items belonging to the collection being added. Currently you have to go out of the collection to edit items that belong to it. 6. Navigation within multiscreen operations. The breadcrumb links do not always represent where you are in the function hierarchy meaning the back button needs to be used on some occasions. As there appears to be problems when using the back button, the breadcrumbs need to be complete and session state information needs to be maintained so that the back button can be used. 7. When editing authorisations it would speed things up if you could select more than one access type. For example if I want a Group to have Read, Write, Add access, I should be able to select all thes in one operation rather than have to perform three separate operations. 8. On the community, collection, item authorisation pages it would be useful to be able to click on the group and have a popup displaying which EPersons belonged to the group. Currently you have to go out and back into the Group maintenance page to see this. 9. Similar to above, when viewing the groups it would be useful to be able to see which collections the groups had access to. 10. Look at performance improvements for update/delete queries, for example by using threads or asynchronous background transactions while the user moves to the next screen. This may also be an issue for drawing of screens for example when a repository has a large number of collections, groups, etc rendering may become slow. This could be improved through filtering what is displayed by providing search and browse facilities similar to what is currently in place for collections. 11. Consistent placement and use of buttons would be useful to avoid confusion. For example, on some screens you need to make a change and also click an "Update" button whereas on others you only need to make a change for it to take effect. On several screens where multiple operations may be performed (such as metadata, bitstream registries) the "New" button is placed at the bottom of the screen, where it may be better to put it at the top since the page returns to the top once the change has been applied. 12. Would be good to be able to apply advanced wildcard authorisation policies to collections, not just items and bitstreams. 13. Many of the tables run off the screen making it impossible to view the information without scrolling left-to-right. If the table cannot be made to fit on the screen it would be useful to allow columns to be hidden (similar to the hide/show functionality of tools like MS Excel/Access) Hope that helps. If you would like any clarification on these requests, please feel free to contact me. Thanks. Scott. ------------------------------ _______________________________________________ Dspace-general mailing list Dspace-general@mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general End of Dspace-general Digest, Vol 3, Issue 6 ******************************************** From tull.9@osu.edu Thu Oct 9 14:53:54 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h99Irrqb011381 for ; Thu, 9 Oct 2003 14:53:53 -0400 (EDT) Received: from mail-mta3.service.ohio-state.edu (mail-mta3.service.ohio-state.edu [128.146.216.43])h99IrqQp010481 for ; Thu, 9 Oct 2003 14:53:52 -0400 (EDT) Received: from MAI105BS1.osu.edu (mai105bs1.lib.ohio-state.edu [128.146.9.207]) by mail-mta3.service.ohio-state.edu (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTP id <0HMI001V275Q45@mail-mta3.service.ohio-state.edu> for dspace-general@mit.edu; Thu, 09 Oct 2003 14:53:52 -0400 (EDT) Date: Thu, 09 Oct 2003 14:22:45 -0400 From: Laura Tull X-Sender: tull.9@pop.service.ohio-state.edu To: dspace-general@mit.edu Message-id: <4.3.2.7.2.20031009141923.029c7778@pop.service.ohio-state.edu> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Content-type: multipart/alternative; boundary="Boundary_(ID_YLnKlDHSiU45T62YKhe1xA)" Subject: [Dspace-general] Indexing more fields in Dspace X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Thu, 09 Oct 2003 18:53:54 -0000 --Boundary_(ID_YLnKlDHSiU45T62YKhe1xA) Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT We just added a collection for a newsletter. We added all of the titles of the articles within the newsletter to the description field, which doesn't appear to be indexed. Example: http://hdl.handle.net/1811/53 I didn't see anything about indexing additional fields on the feature request list. This is a field we would like to see indexed. Is there anything in the works for this already? *********************************** Laura Tull Systems Librarian Ohio State University Libraries 1858 Neil Avenue Mall Columbus OH 43210-1286 Phone: 614-247-6459 Fax: 614-292-7859 Email: tull.9@osu.edu *********************************** --Boundary_(ID_YLnKlDHSiU45T62YKhe1xA) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT We just added a collection for a newsletter. We added all of the titles of the articles within the newsletter to the description field, which doesn't appear to be indexed.

Example: http://hdl.handle.net/1811/53

I didn't see anything about indexing additional fields on the feature request list.  This is a field we would like to see indexed.  Is there anything in the works for this already?


***********************************
Laura Tull
Systems Librarian
Ohio State University Libraries
1858 Neil Avenue Mall
Columbus OH 43210-1286
Phone:  614-247-6459
Fax:  614-292-7859
Email:  tull.9@osu.edu
*********************************** --Boundary_(ID_YLnKlDHSiU45T62YKhe1xA)-- From gabriela.mircea@utoronto.ca Tue Oct 14 11:16:01 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h9EFG0qb016542 for ; Tue, 14 Oct 2003 11:16:00 -0400 (EDT) Received: from bureau8.utcc.utoronto.ca (bureau8.utcc.utoronto.ca [128.100.132.18])h9EFFxsM016308 for ; Tue, 14 Oct 2003 11:15:59 -0400 (EDT) Received: from utl-194-187.library.utoronto.ca ([142.150.194.187] EHLO utoronto.ca ident: IDENT-NOT-QUERIED [port 1239]) by bureau8.utcc.utoronto.ca with ESMTP id <25337-13726>; Tue, 14 Oct 2003 11:15:49 -0400 Message-ID: <3F8C1318.2090800@utoronto.ca> Date: Tue, 14 Oct 2003 11:15:36 -0400 From: Gabriela Mircea User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.01 MIME-Version: 1.0 To: dspace-general@mit.edu Subject: [Dspace-general] data sets - metadata References: <5.2.1.1.2.20031007100229.02140cb8@po10.mit.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 14 Oct 2003 15:16:01 -0000 Hi all, We have some data sets that we would like to put into DSpace, but I am not sure how we should handle the metadata. Does anyone have data sets in DSpace, and are you willing to share the way that metadata was organized? We should probably add some more fields. The problem is not how to add the fields (technical), but what descriptors should we use for data sets. Are there any standards? Thank you in advance, Gabriela From jqj@darkwing.uoregon.edu Tue Oct 14 12:15:31 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h9EGFVqb017867 for ; Tue, 14 Oct 2003 12:15:31 -0400 (EDT) Received: from darkwing.uoregon.edu (darkwing.uoregon.edu [128.223.142.13]) h9EGFTO8013405 for ; Tue, 14 Oct 2003 12:15:30 -0400 (EDT) Received: from TWIG (twig.uoregon.edu [128.223.86.56]) by darkwing.uoregon.edu (8.12.10/8.12.10) with SMTP id h9EGFSJg022476 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Tue, 14 Oct 2003 09:15:28 -0700 (PDT) From: "JQ Johnson" To: Subject: RE: [Dspace-general] data sets - metadata Date: Tue, 14 Oct 2003 09:15:28 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal In-Reply-To: <3F8C1318.2090800@utoronto.ca> X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 14 Oct 2003 16:15:31 -0000 I'm very interested in this question also. Note that the format of the data in computer file or DSPace format registry terms (Excel file, text file, Access .mdb file, etc.) may be much less relevant than the internal format of the data (for instance, a text file might be a comma-separated spreadsheet dataset or an SPSS dataset or the raw SQL commands needed to reconstitute a SQL database or ...). Perhaps more important than the raw observational data is the internal descriptive data that may or may not accompany the data itself -- the codebook, if you will. Note that in some data formats this is a separate file, while in others it may be integrated into the data format. This is truly metadata, but it's sure as anything not qDC! Perhaps equally important is the description of the data collection and data cleaning technique -- the sort of information that is typically included in the methods section of a paper based on the raw data. If we really care about having data sets useful in the future, then it's important that the data set include links to such a methods section. Such information is highly discipline specific; the appropriate metadata for a gene sequence is rather different from that for a statistical survey of domestic abuse victims. Many data sets are made available as supplements to published research; for example, many journals such as _Science_ now provide web based repositories for appendices to articles they publish. At a bare minimum, the DC-style metadata for a data set that corresponds to a published paper should include a citation for the published paper. Let's start with the qDC. coverage.* are natural fields to fill in as is unqualified format. I'd say that relation.isbasedon and other relation.* fields are also critical to include. I'd also say that a policy that required a human-readable codebook as one of the bitstreams associated with a dataset (stored as one or more bitstreams in the same item) would be extremely important. But then what should the format fields refer to? They are item-level, so how do we relate the format.* values to the particular bitstreams they apply to? [This seems to be a major weakness in the current DSpace architecture] Our observation as we've begun to explore statistical data for our institutional repository is that most researchers are very careless about documenting their data in ways that would make it useful to other researchers in the future. We believe that the simple repository is only a tiny fraction of the real issue, and that the important thing is to provide advice and formal structures that make it easy for researchers to document their data collection process. I suspect that trying to answer the question if posed as "data sets" is going to be a failure, and that we should pose the question in terms of some particular kind of data set such as statistical sample observations. "Data set" is so broad that it even includes a set of bibliography entries (in bibtex, endnote, refer, MARC, or whatever format). So the first thing to do is for us to focus on a particular kind of data. JQ Johnson Office: 115F Knight Library Academic Education Coordinator mailto:jqj@darkwing.uoregon.edu 1299 University of Oregon phone: 1-541-346-1746; -3485 fax Eugene, OR 97403-1299 http://darkwing.uoregon.edu/~jqj/ -----Original Message----- From: dspace-general-bounces@mit.edu [mailto:dspace-general-bounces@mit.edu]On Behalf Of Gabriela Mircea Sent: Tuesday, October 14, 2003 8:16 AM To: dspace-general@mit.edu Subject: [Dspace-general] data sets - metadata Hi all, We have some data sets that we would like to put into DSpace, but I am not sure how we should handle the metadata. Does anyone have data sets in DSpace, and are you willing to share the way that metadata was organized? We should probably add some more fields. The problem is not how to add the fields (technical), but what descriptors should we use for data sets. Are there any standards? Thank you in advance, Gabriela _______________________________________________ Dspace-general mailing list Dspace-general@mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general From sbell@library.rochester.edu Wed Oct 15 12:42:05 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h9FGg4qb009212 for ; Wed, 15 Oct 2003 12:42:04 -0400 (EDT) Received: from library.rochester.edu (rcl.lib.rochester.edu [128.151.244.122]) h9FGg4bP003797 for ; Wed, 15 Oct 2003 12:42:04 -0400 (EDT) Received: from RCL-MTA by library.rochester.edu with Novell_GroupWise; Wed, 15 Oct 2003 12:47:17 -0400 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.3 Date: Wed, 15 Oct 2003 12:46:57 -0400 From: "Suzanne Bell" To: Subject: RE: [Dspace-general] data sets - metadata Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id h9FGg4qb009212 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 15 Oct 2003 16:42:05 -0000 Hello folks- Would the work of the Data Documentation Initiative be germaine to this issue, I wonder? I have to admit I've not had any direct involvement with this project, but I know they've been working very hard on this issue (metadata for datasets) for several years. They have a good website at: http://www.icpsr.umich.edu/DDI/ (their focus is social science data, not scientific) -Suzanne ******************************************* Suzanne Bell, Economics/Data Librarian University of Rochester 585/275-9317 sbell@library.rochester.edu From robert.tansley@hp.com Wed Oct 15 16:24:40 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h9FKOeqb015302 for ; Wed, 15 Oct 2003 16:24:40 -0400 (EDT) Received: from palrel10.hp.com (palrel10.hp.com [156.153.255.245]) h9FKOUIO024819 for ; Wed, 15 Oct 2003 16:24:31 -0400 (EDT) Received: from hplms2.hpl.hp.com (hplms2.hpl.hp.com [15.0.152.33]) by palrel10.hp.com (Postfix) with ESMTP id B9C0C1C00F8A; Wed, 15 Oct 2003 13:24:29 -0700 (PDT) Received: from hplex1.hpl.hp.com (hplex1.hpl.hp.com [15.0.152.182]) h9FKOS6n009701; Wed, 15 Oct 2003 13:24:29 -0700 (PDT) Received: from 15.0.152.182 by hplex1.hpl.hp.com (InterScan E-Mail VirusWall NT); Wed, 15 Oct 2003 13:24:28 -0700 Received: by hplex1.hpl.hp.com with Internet Mail Service (5.5.2653.19) id <4WL7VVGG>; Wed, 15 Oct 2003 13:24:28 -0700 Message-ID: <40700B4C02ABD5119F00009027876644084DF262@hplex1.hpl.hp.com> From: "Tansley, Robert" To: "'Laura Tull'" , dspace-general@mit.edu Subject: RE: [Dspace-general] Indexing more fields in Dspace Date: Wed, 15 Oct 2003 13:24:27 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 15 Oct 2003 20:24:41 -0000 You can easily get that field indexed by having someone edit the DSIndexer.java code in the DSpace source tree. I know this isn't ideal; perhaps the fields that are indexed should be another configuration parameter/set of parameters, and maybe made part of the Dublin Core Registry page in the admin UI. If anyone wants to implement this functionality please let us know! Robert Tansley / Hewlett-Packard Laboratories / (+1) 617 551 7624 -----Original Message----- From: Laura Tull [mailto:tull.9@osu.edu] Sent: 09 October 2003 14:23 To: dspace-general@mit.edu Subject: [Dspace-general] Indexing more fields in Dspace We just added a collection for a newsletter. We added all of the titles of the articles within the newsletter to the description field, which doesn't appear to be indexed. Example: http://hdl.handle.net/1811/53 I didn't see anything about indexing additional fields on the feature request list. This is a field we would like to see indexed. Is there anything in the works for this already? From mcneillh@MIT.EDU Mon Oct 20 13:20:24 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h9KHKOqb029047 for ; Mon, 20 Oct 2003 13:20:24 -0400 (EDT) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72])h9KHKN8i006020 for ; Mon, 20 Oct 2003 13:20:23 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])h9KHKMT3021569; Mon, 20 Oct 2003 13:20:23 -0400 (EDT) Received: from dewey-12.mit.edu (DEWEY-12.MIT.EDU [18.171.0.103]) ) h9KHKMjX016074; Mon, 20 Oct 2003 13:20:22 -0400 (EDT) Message-Id: <5.2.1.1.2.20031020124444.02289e40@po11.mit.edu> X-Sender: mcneillh@po11.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 20 Oct 2003 13:20:27 -0400 To: dspace-general@MIT.EDU From: Katherine McNeill-Harman Subject: RE: [Dspace-general] data sets - metadata In-Reply-To: <5.2.1.1.2.20031014145546.01cff130@po10.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: mcneillh@MIT.EDU X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 20 Oct 2003 17:20:24 -0000 Hi everyone, This is a great discussion, and I too am particularly interested in this subject. I'm the Data Services Librarian here at MIT, and have been discussing issues particular to data sets with others (here & at other institutions). For one perspective, I did a poster session on this topic at this year's meeting of IASSIST (the International Association for Social Science Information Service and Technology), see http://macfadden.mit.edu:9500/presentations/iassist/. Following are some thoughts on this specific issue. First, though, are there others on the list interested in discussing data set issues on an ongoing basis? I've discussed with others the possibility of establishing a separate email list on the topic, if there's enough interest. Let me know if you would find this valuable, or if you'd rather just keep the discussion on the general list for now. Regarding this issue, Suzanne brought up a good standard that we're looking at. However, as was discussed, there are two kinds of metadata we're discussing: 1) the metadata used in DSpace to describe the items (we're using Dublin Core, but looking into different ways to take advantage of other metadata standards, such as DDI, see the SIMILE project at http://web.mit.edu/simile/www/) 2) the metadata about the data file in the form of the codebook, that for us will be one of the files (in addition to the data file) associated w/a given item in the system; ideally for social science data, this would be marked up in the DDI XML standard, but it's unclear as of yet if/how this would interface w/the main search system But, as JQ said, sometimes the metadata is integrated w/the data (I believe this sometimes happens more in scientific communities). JQ made some other important points, many with which we're still struggling, including how to have the system understand the internal/external structures of data files and how to encourage high-quality documentation of data. And, as he alluded, treatment of statistical data may be different from that for "raw" data sets that yet require analysis. Some of these will be managed at a system-wide level, while others (such as requiring/standardizing codebook-level metadata) are left up to our communities (e.g. departments) who deposit to DSpace; so organizational issues are as important to understand as are technical ones. One question, what is qDC? Is it a standard for describing scientific data? For those of us not familiar. Let's keep up the interesting discussion! Kate McNeill-Harman Data Services Librarian, MIT >From: "Suzanne Bell" >To: >Subject: RE: [Dspace-general] data sets - metadata > >Hello folks- > >Would the work of the Data Documentation Initiative be germaine to this >issue, I wonder? I have to admit I've not had any direct involvement with >this project, but I know they've been working very hard on this issue >(metadata for datasets) for several years. They have a good website at: > http://www.icpsr.umich.edu/DDI/ >(their focus is social science data, not scientific) > > -Suzanne >>From: "JQ Johnson" >>To: >>Subject: RE: [Dspace-general] data sets - metadata >>Date: Tue, 14 Oct 2003 09:15:28 -0700 >> >>I'm very interested in this question also. Note that the format of the >>data in computer file or DSPace format registry terms (Excel file, text >>file, Access .mdb file, etc.) may be much less relevant than the internal >>format of the data (for instance, a text file might be a comma-separated >>spreadsheet dataset or an SPSS dataset or the raw SQL commands needed to >>reconstitute a SQL database or ...). >> >>Perhaps more important than the raw observational data is the internal >>descriptive data that may or may not accompany the data itself -- the >>codebook, if you will. Note that in some data formats this is a separate >>file, while in others it may be integrated into the data format. This is >>truly metadata, but it's sure as anything not qDC! >> >>Perhaps equally important is the description of the data collection and >>data cleaning technique -- the sort of information that is typically >>included in the methods section of a paper based on the raw data. If we >>really care about having data sets useful in the future, then it's >>important that the data set include links to such a methods >>section. Such information is highly discipline specific; the appropriate >>metadata for a gene sequence is rather different from that for a >>statistical survey of domestic abuse victims. >> >>Many data sets are made available as supplements to published research; >>for example, many journals such as _Science_ now provide web based >>repositories for appendices to articles they publish. At a bare minimum, >>the DC-style metadata for a data set that corresponds to a published >>paper should include a citation for the published paper. >> >>Let's start with the qDC. coverage.* are natural fields to fill in as is >>unqualified format. I'd say that relation.isbasedon and other relation.* >>fields are also critical to include. I'd also say that a policy that >>required a human-readable codebook as one of the bitstreams associated >>with a dataset (stored as one or more bitstreams in the same item) would >>be extremely important. But then what should the format fields refer >>to? They are item-level, so how do we relate the format.* values to the >>particular bitstreams they apply to? [This seems to be a major weakness >>in the current DSpace architecture] >> >>Our observation as we've begun to explore statistical data for our >>institutional repository is that most researchers are very careless about >>documenting their data in ways that would make it useful to other >>researchers in the future. We believe that the simple repository is only >>a tiny fraction of the real issue, and that the important thing is to >>provide advice and formal structures that make it easy for researchers to >>document their data collection process. >> >>I suspect that trying to answer the question if posed as "data sets" is >>going to be a failure, and that we should pose the question in terms of >>some particular kind of data set such as statistical sample observations. >>"Data set" is so broad that it even includes a set of bibliography >>entries (in bibtex, endnote, refer, MARC, or whatever format). So the >>first thing to do is for us to focus on a particular kind of data. >> >>JQ Johnson Office: 115F Knight Library >>Academic Education Coordinator mailto:jqj@darkwing.uoregon.edu >>1299 University of Oregon phone: 1-541-346-1746; -3485 fax >>Eugene, OR 97403-1299 http://darkwing.uoregon.edu/~jqj/ >> >>-----Original Message----- >>From: dspace-general-bounces@mit.edu >>[mailto:dspace-general-bounces@mit.edu]On Behalf Of Gabriela Mircea >>Sent: Tuesday, October 14, 2003 8:16 AM >>To: dspace-general@mit.edu >>Subject: [Dspace-general] data sets - metadata >> >>Hi all, >> >>We have some data sets that we would like to put into DSpace, but I am >>not sure how we should handle the metadata. Does anyone have data sets >>in DSpace, and are you willing to share the way that metadata was organized? >>We should probably add some more fields. The problem is not how to add >>the fields (technical), but what descriptors should we use for data sets. >>Are there any standards? >> >>Thank you in advance, >> >>Gabriela >>_______________________________________________ >>Dspace-general mailing list >>Dspace-general@mit.edu >>http://mailman.mit.edu/mailman/listinfo/dspace-general > >___________________________________________ >Katherine McNeill-Harman >Data Services Reference Librarian >Dewey Library for Management and Social Sciences >Massachusetts Institute of Technology >77 Massachusetts Avenue, E53-100 >Cambridge, MA 02139 >mcneillh@mit.edu >617-253-0787 From jqj@darkwing.uoregon.edu Mon Oct 20 13:30:56 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h9KHUuqb029751 for ; Mon, 20 Oct 2003 13:30:56 -0400 (EDT) Received: from darkwing.uoregon.edu (darkwing.uoregon.edu [128.223.142.13]) h9KHUt8i012382 for ; Mon, 20 Oct 2003 13:30:55 -0400 (EDT) Received: from TWIG (twig.uoregon.edu [128.223.86.56]) by darkwing.uoregon.edu (8.12.10/8.12.10) with SMTP id h9KHUrJg015418 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 20 Oct 2003 10:30:53 -0700 (PDT) From: "JQ Johnson" To: Date: Mon, 20 Oct 2003 10:30:53 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal In-Reply-To: <5.2.1.1.2.20031020124444.02289e40@po11.mit.edu> cc: dspace-general@MIT.EDU Subject: [Dspace-general] spam alert X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 20 Oct 2003 17:30:57 -0000 Our institutional spam filters have started to complain about mail to dspace-general@mit.edu. Here's the report for email I got just now: pts rule name description ---- ---------------------- ------------------------------------------------ -- 1.9 WEIRD_PORT URI: Uses non-standard port number for HTTP 2.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net [Blocked - see ] 1.3 RCVD_IN_NJABL_RELAY RBL: NJABL: sender is confirmed open relay [18.7.21.86 listed in dnsbl.njabl.org] 0.1 RCVD_IN_NJABL RBL: Received via a relay in dnsbl.njabl.org [18.7.21.86 listed in dnsbl.njabl.org] We'd be very appreciative if MIT could clean up the software on melbourne-city-street.mit.edu to eliminate the potential for its use as an open relay. If that can be done, then it will disappear from the NJABL and SPAMCOP blacklists. JQ Johnson Office: 115F Knight Library Academic Education Coordinator mailto:jqj@darkwing.uoregon.edu 1299 University of Oregon phone: 1-541-346-1746; -3485 fax Eugene, OR 97403-1299 http://darkwing.uoregon.edu/~jqj/ From rrodgers@MIT.EDU Tue Oct 21 14:40:50 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h9LIeoqb029885 for ; Tue, 21 Oct 2003 14:40:50 -0400 (EDT) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72])h9LIen83024545 for ; Tue, 21 Oct 2003 14:40:49 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])h9LIemEw010116 for ; Tue, 21 Oct 2003 14:40:48 -0400 (EDT) Received: from dspace-03.mit.edu (DSPACE-03.MIT.EDU [18.51.2.148]) ) h9LIemjW007466 for ; Tue, 21 Oct 2003 14:40:48 -0400 (EDT) Received: (from rrodgers@localhost) by dspace-03.mit.edu (8.9.3) id OAA22298; Tue, 21 Oct 2003 14:40:48 -0400 From: Richard Rodgers To: dspace-general@MIT.EDU Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 21 Oct 2003 14:40:46 -0400 Message-Id: <1066761646.25056.73.camel@dspace-03.mit.edu> Mime-Version: 1.0 Subject: [Dspace-general] DSpace 1.2 Feature Descriptions X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 21 Oct 2003 18:40:50 -0000 As promised, what follows are descriptions of several of the proposed new features for DSpace 1.2. Please post comments and suggestions to this list: we welcome your input! Content Thumbnail Support In DSpace's item display graphical content currently only has text to describe it - users would like to see thumbnails, a more intuitive representation. Clicking on the thumbnail would then deliver the content to the user. Users may want to supply their own thumbnails, but the vast majority would probably prefer to have the system generate thumbnails for them. There will probably be four methods of adding thumbnails to an item: the system could generate automatically during the workflow of submission, a batch process accessing the repository could add thumbnail bundles to items lacking them, or users could submit thumbnails along with the item (highly unlikely!), or the system could generate thumbnails dynamically. To integrate thumbnail generation into a workflow, DSpace needs to be able to take advantage of all of the tools available to generate thumbnails, and many are not written in Java. Many of these tools are also specific types of content - some are image tools, PDF utilities, or a even a script tying multiple tools together. A 'plug-in' architecture could handle these scenarios well: a group of classes wrap whatever tools are needed to generate thumbnails, and register for certain types of submitted content. As content is submitted, its type is checked and it is handed off to the classes that want to process submitted content of that type. A batch tool could also be created that used the same registry of content handlers, looking for items without thumbnails, and then attempting to create thumbnails when possible. Storing thumbnails shouldn't involve too many changes to the system. (None, if the thumbnails are generated dynamically.) DSpace was architected with alternate views of content in mind, where items can have multiple bundles, each containing a different representation of the item's content. A thumbnail could simply be another bundle within the item. The item display page could look for a thumbnail bundle containing images for each bitstream in the primary bundle (we may need a type field to identify the primary bundle vs. a PDF or thumbnail or extracted text bundle,) and then display the thumbnail next to the file name. The thumbnail becomes an official part of the item, or a flag could be used to indicate that the thumbnail is an annotation by the system rather than a part of the original submission. Full Text Searching Currently DSpace users can only search the metadata for items - the text that may be within the content is not searchable. Users would like to search the full text of items within DSpace. It may also be handy for users to have access to the extracted text for an item, possibly in the 'full' item display. Our search engine Lucene can easily index the full text from items, so the challenge is really extracting and storing the full text of submitted items. This problem is remarkably similar to the generation of thumbnails: generating a 'text' representation of an item's content is very similar to generating a thumbnail representation of that content. DSpace's object model supports different representations of content with bundles - each bundle stores a representation. Like thumbnail generation, there are many tools available to extract text from content, many of which are not in Java, and many are specific to certain types of content. Again, a plug-in architecture would handle representation generation well - as content is submitted, classes registered for the type of that content are invoked and annotate the item with a full-text bundle, which would then be recognized and indexed by the search system. A plug-in architecture would be handy for integrating with workflows, or as part of a batch process to be run as part of regular content 'maintenance.' Again, these bundles may need to be typed; in this case a 'full text' bundle type would be a hint for the indexer that it could index the contents of that bundle. Also like thumbnails, the extracted text for content becomes an official part of the item, perhaps with a flag to indicate that it is an annotation by the system and was not part of the original submission. Items Shared by Multiple Collections Currently DSpace assumes that items are part of a single collection. Users would like to share items between collections, even generation 'virtual' collections that are groupings of items from other collections. DSpace's data model supports mapping items to multiple collections, but the GUI tools do not. If an item is shared between collections, then the question arises over who controls it. One solution is to assign an owning collection to an item. The administrator of the owning collection can modify the item, and assign viewing permissions - other collection administrators do not have such control - they can only place a reference to the item in their collection. Administrators who could not access an item themselves would of course not be able to reference the item in their collection. Since items in multiple collections are references and not copies, if an item is for some reason removed or withdrawn, then the references will also appear to be removed or withdrawn. A possible problem in the future to watch out for will be when collection administrators want to attach metadata to or annotate these references. From kenzie@MIT.EDU Tue Oct 21 14:42:11 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h9LIgBqb029911 for ; Tue, 21 Oct 2003 14:42:11 -0400 (EDT) Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82])h9LIgAs3022538; Tue, 21 Oct 2003 14:42:10 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])h9LIg9i2027462; Tue, 21 Oct 2003 14:42:09 -0400 (EDT) Received: from ADTPA.mit.edu (ADTPA.MIT.EDU [18.51.1.92]) (authenticated bits=0) (User authenticated as kenzie@ATHENA.MIT.EDU)h9LIg89L007969 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT); Tue, 21 Oct 2003 14:42:08 -0400 (EDT) Message-Id: <5.2.1.1.2.20031021142524.01e3bdd8@hesiod> X-Sender: kenzie@hesiod X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Tue, 21 Oct 2003 14:39:38 -0400 To: "JQ Johnson" From: MacKenzie Smith Subject: Re: [Dspace-general] spam alert In-Reply-To: References: <5.2.1.1.2.20031020124444.02289e40@po11.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: dspace-general@MIT.EDU X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 21 Oct 2003 18:42:12 -0000 Hi JQ, dspace-general is using MIT's centrally managed listserv services and mail relay, which are run by our central computer services group. They've been working with AOL, spamcop, etc to demonstrate how they're eliminating spam and to introduce smtp authentication. As far as we know, spamcop should be removing MIT from their list soon. Beyond this, there's not much we in the Libraries can do about it, but if actual spam is becoming a problem then we'll convert the list to a moderated one. Thanks for the heads up, MacKenzie/ At 10:30 AM 10/20/2003 -0700, JQ Johnson wrote: >Our institutional spam filters have started to complain about mail to >dspace-general@mit.edu. Here's the report for email I got just now: > > pts rule name description >---- ---------------------- ------------------------------------------------ >-- > 1.9 WEIRD_PORT URI: Uses non-standard port number for HTTP > 2.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net > [Blocked - see >] > 1.3 RCVD_IN_NJABL_RELAY RBL: NJABL: sender is confirmed open relay > [18.7.21.86 listed in dnsbl.njabl.org] > 0.1 RCVD_IN_NJABL RBL: Received via a relay in dnsbl.njabl.org > [18.7.21.86 listed in dnsbl.njabl.org] > >We'd be very appreciative if MIT could clean up the software on >melbourne-city-street.mit.edu to eliminate the potential for its use as an >open relay. If that can be done, then it will disappear from the NJABL and >SPAMCOP blacklists. > >JQ Johnson Office: 115F Knight Library >Academic Education Coordinator mailto:jqj@darkwing.uoregon.edu >1299 University of Oregon phone: 1-541-346-1746; -3485 fax >Eugene, OR 97403-1299 http://darkwing.uoregon.edu/~jqj/ > > > >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general MacKenzie Smith Associate Director for Technology MIT Libraries Building 14S-208 77 Massachusetts Avenue Cambridge, MA 02139 (617)253-8184 kenzie@mit.edu From Ilene.Strongin-Garry@ichotelsgroup.com Wed Oct 22 13:49:58 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h9MHnwqb022359 for ; Wed, 22 Oct 2003 13:49:58 -0400 (EDT) Received: from bhratlsmtp02.hiw.com (bhratlsmtp02.sixcontinentshotels.com [165.2.141.7])h9MHntbY019378 for ; Wed, 22 Oct 2003 13:49:56 -0400 (EDT) Received: from 165.2.177.152 by bhratlsmtp02.hiw.com (InterScan E-Mail VirusWall NT); Wed, 22 Oct 2003 13:49:54 -0400 (Eastern Daylight Time) Received: by atlhub02.hiw.com with Internet Mail Service (5.5.2653.19) id ; Wed, 22 Oct 2003 13:49:57 -0400 Message-ID: <4201FDFD444BC84190DEF632181EB38F2AB7E9@bhratlexg03.hiw.com> From: "Strongin-Garry, Ilene (IHG)" To: "'dspace-general@mit.edu'" Date: Wed, 22 Oct 2003 13:49:49 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Dspace-general] DSpace 1.2 Feature Descriptions X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 22 Oct 2003 17:49:58 -0000 The features named are definitely desired. Full-text searching is probably first on the list. We would also like to be able to put an item into more than one collection. Also would like to see an Administer Interface that lets administrators search for items not just be ID, but also by title or keywords or authors (as was mentioned by another user in a previous DSpace digest). I've also had a request for better ASCII recognition (in the case of symbols like umlauts and currency. Also the following would be great: When submitting an item, you are asked to submit to a collection. However, once you choose the collection it cannot be changed without having to re-enter the entire amount of metadata and files. I would like to have the option to correct my collection choice. Secondly, it would be great to be able to add additional files to an item once it's in DSpace. I know you can edit metadata, but it would be great to be able to add files in case something has been accidentally left off or found later after an item has been submitted. -----Original Message----- From: dspace-general-request@mit.edu [mailto:dspace-general-request@mit.edu] Sent: Wednesday, October 22, 2003 12:01 PM To: dspace-general@mit.edu Subject: Dspace-general Digest, Vol 3, Issue 13 Send Dspace-general mailing list submissions to dspace-general@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@mit.edu You can reach the person managing the list at dspace-general-owner@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. DSpace 1.2 Feature Descriptions (Richard Rodgers) 2. Re: spam alert (MacKenzie Smith) ---------------------------------------------------------------------- Date: 21 Oct 2003 14:40:46 -0400 From: Richard Rodgers To: dspace-general@MIT.EDU Subject: [Dspace-general] DSpace 1.2 Feature Descriptions Message-ID: <1066761646.25056.73.camel@dspace-03.mit.edu> Content-Type: text/plain MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: list Message: 1 As promised, what follows are descriptions of several of the proposed new features for DSpace 1.2. Please post comments and suggestions to this list: we welcome your input! Content Thumbnail Support In DSpace's item display graphical content currently only has text to describe it - users would like to see thumbnails, a more intuitive representation. Clicking on the thumbnail would then deliver the content to the user. Users may want to supply their own thumbnails, but the vast majority would probably prefer to have the system generate thumbnails for them. There will probably be four methods of adding thumbnails to an item: the system could generate automatically during the workflow of submission, a batch process accessing the repository could add thumbnail bundles to items lacking them, or users could submit thumbnails along with the item (highly unlikely!), or the system could generate thumbnails dynamically. To integrate thumbnail generation into a workflow, DSpace needs to be able to take advantage of all of the tools available to generate thumbnails, and many are not written in Java. Many of these tools are also specific types of content - some are image tools, PDF utilities, or a even a script tying multiple tools together. A 'plug-in' architecture could handle these scenarios well: a group of classes wrap whatever tools are needed to generate thumbnails, and register for certain types of submitted content. As content is submitted, its type is checked and it is handed off to the classes that want to process submitted content of that type. A batch tool could also be created that used the same registry of content handlers, looking for items without thumbnails, and then attempting to create thumbnails when possible. Storing thumbnails shouldn't involve too many changes to the system. (None, if the thumbnails are generated dynamically.) DSpace was architected with alternate views of content in mind, where items can have multiple bundles, each containing a different representation of the item's content. A thumbnail could simply be another bundle within the item. The item display page could look for a thumbnail bundle containing images for each bitstream in the primary bundle (we may need a type field to identify the primary bundle vs. a PDF or thumbnail or extracted text bundle,) and then display the thumbnail next to the file name. The thumbnail becomes an official part of the item, or a flag could be used to indicate that the thumbnail is an annotation by the system rather than a part of the original submission. Full Text Searching Currently DSpace users can only search the metadata for items - the text that may be within the content is not searchable. Users would like to search the full text of items within DSpace. It may also be handy for users to have access to the extracted text for an item, possibly in the 'full' item display. Our search engine Lucene can easily index the full text from items, so the challenge is really extracting and storing the full text of submitted items. This problem is remarkably similar to the generation of thumbnails: generating a 'text' representation of an item's content is very similar to generating a thumbnail representation of that content. DSpace's object model supports different representations of content with bundles - each bundle stores a representation. Like thumbnail generation, there are many tools available to extract text from content, many of which are not in Java, and many are specific to certain types of content. Again, a plug-in architecture would handle representation generation well - as content is submitted, classes registered for the type of that content are invoked and annotate the item with a full-text bundle, which would then be recognized and indexed by the search system. A plug-in architecture would be handy for integrating with workflows, or as part of a batch process to be run as part of regular content 'maintenance.' Again, these bundles may need to be typed; in this case a 'full text' bundle type would be a hint for the indexer that it could index the contents of that bundle. Also like thumbnails, the extracted text for content becomes an official part of the item, perhaps with a flag to indicate that it is an annotation by the system and was not part of the original submission. Items Shared by Multiple Collections Currently DSpace assumes that items are part of a single collection. Users would like to share items between collections, even generation 'virtual' collections that are groupings of items from other collections. DSpace's data model supports mapping items to multiple collections, but the GUI tools do not. If an item is shared between collections, then the question arises over who controls it. One solution is to assign an owning collection to an item. The administrator of the owning collection can modify the item, and assign viewing permissions - other collection administrators do not have such control - they can only place a reference to the item in their collection. Administrators who could not access an item themselves would of course not be able to reference the item in their collection. Since items in multiple collections are references and not copies, if an item is for some reason removed or withdrawn, then the references will also appear to be removed or withdrawn. A possible problem in the future to watch out for will be when collection administrators want to attach metadata to or annotate these references. ------------------------------ Date: Tue, 21 Oct 2003 14:39:38 -0400 From: MacKenzie Smith To: "JQ Johnson" Cc: dspace-general@MIT.EDU Subject: Re: [Dspace-general] spam alert Message-ID: <5.2.1.1.2.20031021142524.01e3bdd8@hesiod> In-Reply-To: References: <5.2.1.1.2.20031020124444.02289e40@po11.mit.edu> Content-Type: text/plain; charset="us-ascii"; format=flowed MIME-Version: 1.0 Precedence: list Message: 2 Hi JQ, dspace-general is using MIT's centrally managed listserv services and mail relay, which are run by our central computer services group. They've been working with AOL, spamcop, etc to demonstrate how they're eliminating spam and to introduce smtp authentication. As far as we know, spamcop should be removing MIT from their list soon. Beyond this, there's not much we in the Libraries can do about it, but if actual spam is becoming a problem then we'll convert the list to a moderated one. Thanks for the heads up, MacKenzie/ At 10:30 AM 10/20/2003 -0700, JQ Johnson wrote: >Our institutional spam filters have started to complain about mail to >dspace-general@mit.edu. Here's the report for email I got just now: > > pts rule name description >---- ---------------------- ------------------------------------------------ >-- > 1.9 WEIRD_PORT URI: Uses non-standard port number for HTTP > 2.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net > [Blocked - see >] > 1.3 RCVD_IN_NJABL_RELAY RBL: NJABL: sender is confirmed open relay > [18.7.21.86 listed in dnsbl.njabl.org] > 0.1 RCVD_IN_NJABL RBL: Received via a relay in dnsbl.njabl.org > [18.7.21.86 listed in dnsbl.njabl.org] > >We'd be very appreciative if MIT could clean up the software on >melbourne-city-street.mit.edu to eliminate the potential for its use as an >open relay. If that can be done, then it will disappear from the NJABL and >SPAMCOP blacklists. > >JQ Johnson Office: 115F Knight Library >Academic Education Coordinator mailto:jqj@darkwing.uoregon.edu >1299 University of Oregon phone: 1-541-346-1746; -3485 fax >Eugene, OR 97403-1299 http://darkwing.uoregon.edu/~jqj/ > > > >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general MacKenzie Smith Associate Director for Technology MIT Libraries Building 14S-208 77 Massachusetts Avenue Cambridge, MA 02139 (617)253-8184 kenzie@mit.edu ------------------------------ _______________________________________________ Dspace-general mailing list Dspace-general@mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general End of Dspace-general Digest, Vol 3, Issue 13 ********************************************* From aramnarine@library.uwi.tt Wed Oct 22 14:48:15 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h9MImFqb023635 for ; Wed, 22 Oct 2003 14:48:15 -0400 (EDT) Received: from enggate.uwi.tt (enggate.uwi.tt [196.3.139.34]) h9MImDv1006375 for ; Wed, 22 Oct 2003 14:48:14 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by enggate.uwi.tt (Postfix) with ESMTP id 0553510318 for ; Wed, 22 Oct 2003 14:47:39 -0400 (AST) Received: from enggate.uwi.tt ([127.0.0.1]) by localhost (bsd.eng.uwi.tt [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 00481-03 for ; Wed, 22 Oct 2003 14:47:37 -0400 (AST) Received: from ldc.eng.uwi.tt (ldc.eng.uwi.tt [192.168.20.31]) by enggate.uwi.tt (Postfix) with ESMTP id 7DE42102FE for ; Wed, 22 Oct 2003 14:47:37 -0400 (AST) Received: from santw40libry001.salibry.library.uwi.tt (santw40libry001.library.uwi.tt [192.168.20.189]) by ldc.eng.uwi.tt (8.9.1/8.9.1) with ESMTP id NAA07686 for ; Wed, 22 Oct 2003 13:08:41 +0400 (GMT) Received: by SANTW40LIBRY001 with Internet Mail Service (5.5.2653.19) id ; Wed, 22 Oct 2003 13:24:21 -0400 Message-ID: <21530F7443DED311AC3500C04F238E88A3BD13@SANTW40LIBRY001> From: Angela Ramnarine To: dspace-general@mit.edu Date: Wed, 22 Oct 2003 13:24:21 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Virus-Scanned: by amavisd-new at uwi.tt Subject: [Dspace-general] RE: Dspace-general Digest, Vol 3, Issue 13 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 22 Oct 2003 18:48:16 -0000 Already done. Angela -----Original Message----- From: dspace-general-request@mit.edu [mailto:dspace-general-request@mit.edu] Sent: Wednesday, October 22, 2003 12:01 PM To: dspace-general@mit.edu Subject: Dspace-general Digest, Vol 3, Issue 13 Send Dspace-general mailing list submissions to dspace-general@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@mit.edu You can reach the person managing the list at dspace-general-owner@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. DSpace 1.2 Feature Descriptions (Richard Rodgers) 2. Re: spam alert (MacKenzie Smith) ---------------------------------------------------------------------- Date: 21 Oct 2003 14:40:46 -0400 From: Richard Rodgers To: dspace-general@MIT.EDU Subject: [Dspace-general] DSpace 1.2 Feature Descriptions Message-ID: <1066761646.25056.73.camel@dspace-03.mit.edu> Content-Type: text/plain MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: list Message: 1 As promised, what follows are descriptions of several of the proposed new features for DSpace 1.2. Please post comments and suggestions to this list: we welcome your input! Content Thumbnail Support In DSpace's item display graphical content currently only has text to describe it - users would like to see thumbnails, a more intuitive representation. Clicking on the thumbnail would then deliver the content to the user. Users may want to supply their own thumbnails, but the vast majority would probably prefer to have the system generate thumbnails for them. There will probably be four methods of adding thumbnails to an item: the system could generate automatically during the workflow of submission, a batch process accessing the repository could add thumbnail bundles to items lacking them, or users could submit thumbnails along with the item (highly unlikely!), or the system could generate thumbnails dynamically. To integrate thumbnail generation into a workflow, DSpace needs to be able to take advantage of all of the tools available to generate thumbnails, and many are not written in Java. Many of these tools are also specific types of content - some are image tools, PDF utilities, or a even a script tying multiple tools together. A 'plug-in' architecture could handle these scenarios well: a group of classes wrap whatever tools are needed to generate thumbnails, and register for certain types of submitted content. As content is submitted, its type is checked and it is handed off to the classes that want to process submitted content of that type. A batch tool could also be created that used the same registry of content handlers, looking for items without thumbnails, and then attempting to create thumbnails when possible. Storing thumbnails shouldn't involve too many changes to the system. (None, if the thumbnails are generated dynamically.) DSpace was architected with alternate views of content in mind, where items can have multiple bundles, each containing a different representation of the item's content. A thumbnail could simply be another bundle within the item. The item display page could look for a thumbnail bundle containing images for each bitstream in the primary bundle (we may need a type field to identify the primary bundle vs. a PDF or thumbnail or extracted text bundle,) and then display the thumbnail next to the file name. The thumbnail becomes an official part of the item, or a flag could be used to indicate that the thumbnail is an annotation by the system rather than a part of the original submission. Full Text Searching Currently DSpace users can only search the metadata for items - the text that may be within the content is not searchable. Users would like to search the full text of items within DSpace. It may also be handy for users to have access to the extracted text for an item, possibly in the 'full' item display. Our search engine Lucene can easily index the full text from items, so the challenge is really extracting and storing the full text of submitted items. This problem is remarkably similar to the generation of thumbnails: generating a 'text' representation of an item's content is very similar to generating a thumbnail representation of that content. DSpace's object model supports different representations of content with bundles - each bundle stores a representation. Like thumbnail generation, there are many tools available to extract text from content, many of which are not in Java, and many are specific to certain types of content. Again, a plug-in architecture would handle representation generation well - as content is submitted, classes registered for the type of that content are invoked and annotate the item with a full-text bundle, which would then be recognized and indexed by the search system. A plug-in architecture would be handy for integrating with workflows, or as part of a batch process to be run as part of regular content 'maintenance.' Again, these bundles may need to be typed; in this case a 'full text' bundle type would be a hint for the indexer that it could index the contents of that bundle. Also like thumbnails, the extracted text for content becomes an official part of the item, perhaps with a flag to indicate that it is an annotation by the system and was not part of the original submission. Items Shared by Multiple Collections Currently DSpace assumes that items are part of a single collection. Users would like to share items between collections, even generation 'virtual' collections that are groupings of items from other collections. DSpace's data model supports mapping items to multiple collections, but the GUI tools do not. If an item is shared between collections, then the question arises over who controls it. One solution is to assign an owning collection to an item. The administrator of the owning collection can modify the item, and assign viewing permissions - other collection administrators do not have such control - they can only place a reference to the item in their collection. Administrators who could not access an item themselves would of course not be able to reference the item in their collection. Since items in multiple collections are references and not copies, if an item is for some reason removed or withdrawn, then the references will also appear to be removed or withdrawn. A possible problem in the future to watch out for will be when collection administrators want to attach metadata to or annotate these references. ------------------------------ Date: Tue, 21 Oct 2003 14:39:38 -0400 From: MacKenzie Smith To: "JQ Johnson" Cc: dspace-general@MIT.EDU Subject: Re: [Dspace-general] spam alert Message-ID: <5.2.1.1.2.20031021142524.01e3bdd8@hesiod> In-Reply-To: References: <5.2.1.1.2.20031020124444.02289e40@po11.mit.edu> Content-Type: text/plain; charset="us-ascii"; format=flowed MIME-Version: 1.0 Precedence: list Message: 2 Hi JQ, dspace-general is using MIT's centrally managed listserv services and mail relay, which are run by our central computer services group. They've been working with AOL, spamcop, etc to demonstrate how they're eliminating spam and to introduce smtp authentication. As far as we know, spamcop should be removing MIT from their list soon. Beyond this, there's not much we in the Libraries can do about it, but if actual spam is becoming a problem then we'll convert the list to a moderated one. Thanks for the heads up, MacKenzie/ At 10:30 AM 10/20/2003 -0700, JQ Johnson wrote: >Our institutional spam filters have started to complain about mail to >dspace-general@mit.edu. Here's the report for email I got just now: > > pts rule name description >---- ---------------------- ------------------------------------------------ >-- > 1.9 WEIRD_PORT URI: Uses non-standard port number for HTTP > 2.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net > [Blocked - see >] > 1.3 RCVD_IN_NJABL_RELAY RBL: NJABL: sender is confirmed open relay > [18.7.21.86 listed in dnsbl.njabl.org] > 0.1 RCVD_IN_NJABL RBL: Received via a relay in dnsbl.njabl.org > [18.7.21.86 listed in dnsbl.njabl.org] > >We'd be very appreciative if MIT could clean up the software on >melbourne-city-street.mit.edu to eliminate the potential for its use as an >open relay. If that can be done, then it will disappear from the NJABL and >SPAMCOP blacklists. > >JQ Johnson Office: 115F Knight Library >Academic Education Coordinator mailto:jqj@darkwing.uoregon.edu >1299 University of Oregon phone: 1-541-346-1746; -3485 fax >Eugene, OR 97403-1299 http://darkwing.uoregon.edu/~jqj/ > > > >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general MacKenzie Smith Associate Director for Technology MIT Libraries Building 14S-208 77 Massachusetts Avenue Cambridge, MA 02139 (617)253-8184 kenzie@mit.edu ------------------------------ _______________________________________________ Dspace-general mailing list Dspace-general@mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general End of Dspace-general Digest, Vol 3, Issue 13 ********************************************* From ajhatfie@iupui.edu Wed Oct 22 18:03:50 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h9MM3oqb026866 for ; Wed, 22 Oct 2003 18:03:50 -0400 (EDT) Received: from julesburg.uits.indiana.edu (julesburg.uits.indiana.edu [129.79.1.75])h9MM3nK9004627 for ; Wed, 22 Oct 2003 18:03:49 -0400 (EDT) Received: from iu-mssg-smtp01.ads.iu.edu (iu-mssg-smtp01.exchange.iu.edu [129.79.1.218])h9MM3lKm008130 for ; Wed, 22 Oct 2003 17:03:47 -0500 (EST) Received: from iu-mssg-mbx03.ads.iu.edu ([129.79.1.212]) by iu-mssg-smtp01.ads.iu.edu with Microsoft SMTPSVC(5.0.2195.6713); Wed, 22 Oct 2003 17:03:10 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: [Dspace-general] DSpace 1.2 Feature Descriptions Date: Wed, 22 Oct 2003 17:03:09 -0500 Message-ID: <34FCF4854FC72B478C655EFD2CE8FD34E91E32@iu-mssg-mbx03.exchange.iu.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Dspace-general] DSpace 1.2 Feature Descriptions Thread-Index: AcOYxTCelaW/h/M6TVW6XbxPsdjJwgAIffTA From: "Hatfield, Amy J" To: X-OriginalArrivalTime: 22 Oct 2003 22:03:10.0304 (UTC) FILETIME=[47ECC600:01C398E8] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id h9MM3oqb026866 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 22 Oct 2003 22:03:51 -0000 I emphatically agree that full text indexing should be a priority! I also feel that the ability of items to 'belong' to more than one Collection and the ability to create 'Virtual' Collections, with a single 'owner' Collection, is desirable. Finally, the suggestion, "...it would be great to be able to add files in case something has been accidentally left off or found later after an item has been submitted.", is right on target. I would like to see this functionality as well. It could be that an Item ends up with cumulative versions and it would be so fantastic if the versions could be added to the same Item allowing end users to view the different versions in 1 place. Very powerful! Thanks, Amy Amy Jo Hatfield Information Systems Librarian Ruth Lilly Medical Library 317-278-8402 ajhatfie@iupui.edu -----Original Message----- From: dspace-general-bounces@mit.edu [mailto:dspace-general-bounces@mit.edu] On Behalf Of Strongin-Garry, Ilene (IHG) Sent: Wednesday, October 22, 2003 12:50 PM To: 'dspace-general@mit.edu' Subject: [Dspace-general] DSpace 1.2 Feature Descriptions The features named are definitely desired. Full-text searching is probably first on the list. We would also like to be able to put an item into more than one collection. Also would like to see an Administer Interface that lets administrators search for items not just be ID, but also by title or keywords or authors (as was mentioned by another user in a previous DSpace digest). I've also had a request for better ASCII recognition (in the case of symbols like umlauts and currency. Also the following would be great: When submitting an item, you are asked to submit to a collection. However, once you choose the collection it cannot be changed without having to re-enter the entire amount of metadata and files. I would like to have the option to correct my collection choice. Secondly, it would be great to be able to add additional files to an item once it's in DSpace. I know you can edit metadata, but it would be great to be able to add files in case something has been accidentally left off or found later after an item has been submitted. -----Original Message----- From: dspace-general-request@mit.edu [mailto:dspace-general-request@mit.edu] Sent: Wednesday, October 22, 2003 12:01 PM To: dspace-general@mit.edu Subject: Dspace-general Digest, Vol 3, Issue 13 Send Dspace-general mailing list submissions to dspace-general@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@mit.edu You can reach the person managing the list at dspace-general-owner@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. DSpace 1.2 Feature Descriptions (Richard Rodgers) 2. Re: spam alert (MacKenzie Smith) ---------------------------------------------------------------------- Date: 21 Oct 2003 14:40:46 -0400 From: Richard Rodgers To: dspace-general@MIT.EDU Subject: [Dspace-general] DSpace 1.2 Feature Descriptions Message-ID: <1066761646.25056.73.camel@dspace-03.mit.edu> Content-Type: text/plain MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: list Message: 1 As promised, what follows are descriptions of several of the proposed new features for DSpace 1.2. Please post comments and suggestions to this list: we welcome your input! Content Thumbnail Support In DSpace's item display graphical content currently only has text to describe it - users would like to see thumbnails, a more intuitive representation. Clicking on the thumbnail would then deliver the content to the user. Users may want to supply their own thumbnails, but the vast majority would probably prefer to have the system generate thumbnails for them. There will probably be four methods of adding thumbnails to an item: the system could generate automatically during the workflow of submission, a batch process accessing the repository could add thumbnail bundles to items lacking them, or users could submit thumbnails along with the item (highly unlikely!), or the system could generate thumbnails dynamically. To integrate thumbnail generation into a workflow, DSpace needs to be able to take advantage of all of the tools available to generate thumbnails, and many are not written in Java. Many of these tools are also specific types of content - some are image tools, PDF utilities, or a even a script tying multiple tools together. A 'plug-in' architecture could handle these scenarios well: a group of classes wrap whatever tools are needed to generate thumbnails, and register for certain types of submitted content. As content is submitted, its type is checked and it is handed off to the classes that want to process submitted content of that type. A batch tool could also be created that used the same registry of content handlers, looking for items without thumbnails, and then attempting to create thumbnails when possible. Storing thumbnails shouldn't involve too many changes to the system. (None, if the thumbnails are generated dynamically.) DSpace was architected with alternate views of content in mind, where items can have multiple bundles, each containing a different representation of the item's content. A thumbnail could simply be another bundle within the item. The item display page could look for a thumbnail bundle containing images for each bitstream in the primary bundle (we may need a type field to identify the primary bundle vs. a PDF or thumbnail or extracted text bundle,) and then display the thumbnail next to the file name. The thumbnail becomes an official part of the item, or a flag could be used to indicate that the thumbnail is an annotation by the system rather than a part of the original submission. Full Text Searching Currently DSpace users can only search the metadata for items - the text that may be within the content is not searchable. Users would like to search the full text of items within DSpace. It may also be handy for users to have access to the extracted text for an item, possibly in the 'full' item display. Our search engine Lucene can easily index the full text from items, so the challenge is really extracting and storing the full text of submitted items. This problem is remarkably similar to the generation of thumbnails: generating a 'text' representation of an item's content is very similar to generating a thumbnail representation of that content. DSpace's object model supports different representations of content with bundles - each bundle stores a representation. Like thumbnail generation, there are many tools available to extract text from content, many of which are not in Java, and many are specific to certain types of content. Again, a plug-in architecture would handle representation generation well - as content is submitted, classes registered for the type of that content are invoked and annotate the item with a full-text bundle, which would then be recognized and indexed by the search system. A plug-in architecture would be handy for integrating with workflows, or as part of a batch process to be run as part of regular content 'maintenance.' Again, these bundles may need to be typed; in this case a 'full text' bundle type would be a hint for the indexer that it could index the contents of that bundle. Also like thumbnails, the extracted text for content becomes an official part of the item, perhaps with a flag to indicate that it is an annotation by the system and was not part of the original submission. Items Shared by Multiple Collections Currently DSpace assumes that items are part of a single collection. Users would like to share items between collections, even generation 'virtual' collections that are groupings of items from other collections. DSpace's data model supports mapping items to multiple collections, but the GUI tools do not. If an item is shared between collections, then the question arises over who controls it. One solution is to assign an owning collection to an item. The administrator of the owning collection can modify the item, and assign viewing permissions - other collection administrators do not have such control - they can only place a reference to the item in their collection. Administrators who could not access an item themselves would of course not be able to reference the item in their collection. Since items in multiple collections are references and not copies, if an item is for some reason removed or withdrawn, then the references will also appear to be removed or withdrawn. A possible problem in the future to watch out for will be when collection administrators want to attach metadata to or annotate these references. ------------------------------ Date: Tue, 21 Oct 2003 14:39:38 -0400 From: MacKenzie Smith To: "JQ Johnson" Cc: dspace-general@MIT.EDU Subject: Re: [Dspace-general] spam alert Message-ID: <5.2.1.1.2.20031021142524.01e3bdd8@hesiod> In-Reply-To: References: <5.2.1.1.2.20031020124444.02289e40@po11.mit.edu> Content-Type: text/plain; charset="us-ascii"; format=flowed MIME-Version: 1.0 Precedence: list Message: 2 Hi JQ, dspace-general is using MIT's centrally managed listserv services and mail relay, which are run by our central computer services group. They've been working with AOL, spamcop, etc to demonstrate how they're eliminating spam and to introduce smtp authentication. As far as we know, spamcop should be removing MIT from their list soon. Beyond this, there's not much we in the Libraries can do about it, but if actual spam is becoming a problem then we'll convert the list to a moderated one. Thanks for the heads up, MacKenzie/ At 10:30 AM 10/20/2003 -0700, JQ Johnson wrote: >Our institutional spam filters have started to complain about mail to >dspace-general@mit.edu. Here's the report for email I got just now: > > pts rule name description >---- ---------------------- ------------------------------------------------ >-- > 1.9 WEIRD_PORT URI: Uses non-standard port number for HTTP > 2.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net > [Blocked - see >] > 1.3 RCVD_IN_NJABL_RELAY RBL: NJABL: sender is confirmed open relay > [18.7.21.86 listed in dnsbl.njabl.org] > 0.1 RCVD_IN_NJABL RBL: Received via a relay in dnsbl.njabl.org > [18.7.21.86 listed in dnsbl.njabl.org] > >We'd be very appreciative if MIT could clean up the software on >melbourne-city-street.mit.edu to eliminate the potential for its use as an >open relay. If that can be done, then it will disappear from the NJABL and >SPAMCOP blacklists. > >JQ Johnson Office: 115F Knight Library >Academic Education Coordinator mailto:jqj@darkwing.uoregon.edu >1299 University of Oregon phone: 1-541-346-1746; -3485 fax >Eugene, OR 97403-1299 http://darkwing.uoregon.edu/~jqj/ > > > >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general MacKenzie Smith Associate Director for Technology MIT Libraries Building 14S-208 77 Massachusetts Avenue Cambridge, MA 02139 (617)253-8184 kenzie@mit.edu ------------------------------ _______________________________________________ Dspace-general mailing list Dspace-general@mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general End of Dspace-general Digest, Vol 3, Issue 13 ********************************************* _______________________________________________ Dspace-general mailing list Dspace-general@mit.edu http://mailman.mit.edu/mailman/listinfo/dspace-general From ardp@drtc.isibang.ac.in Thu Oct 23 01:16:59 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h9N5Gwqb000968 for ; Thu, 23 Oct 2003 01:16:59 -0400 (EDT) Received: from drtc.isibang.ac.in ([202.54.37.89])h9N5GrKr008664 for ; Thu, 23 Oct 2003 01:16:57 -0400 (EDT) Received: from aaa ([192.168.2.36]) by drtc.isibang.ac.in (8.12.8/8.12.8) with SMTP id h9N5JSGO007936 for ; Thu, 23 Oct 2003 10:49:29 +0530 Message-ID: <004f01c39925$a5e517c0$2402a8c0@isibang.ac.in> From: "ard" To: Date: Thu, 23 Oct 2003 10:52:26 +0530 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004C_01C39953.BF635800" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [Dspace-general] X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Thu, 23 Oct 2003 05:17:00 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_004C_01C39953.BF635800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have configured Dspace on Redhat 9.0, using apache+ssl+tomcat4.0.6 Though in Apache configuration, I have used user and Group as Apache (as against the suggestion to use dspace user). It is working. Will there be any side effects for this. The problem is, if I change the user, group as something other than apache many of my other software do not work (e.g. squirrelmail). Please let me know. -- ard ------=_NextPart_000_004C_01C39953.BF635800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I have=20 configured Dspace on Redhat 9.0, using = apache+ssl+tomcat4.0.6

Though=20 in Apache configuration, I have used user
and Group as Apache (as = against the=20 suggestion to
use dspace user).  It is working.  Will there = be
any side effects for this.  The problem is, if I
change = the user,=20 group as something other than
apache many of my other software do not = work
(e.g. squirrelmail).  Please let me = know.
 
-- ard

 
------=_NextPart_000_004C_01C39953.BF635800-- From harnad@ecs.soton.ac.uk Sun Oct 26 05:45:40 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id h9QAjeqb022409 for ; Sun, 26 Oct 2003 05:45:40 -0500 (EST) Received: from raven.ecs.soton.ac.uk (raven.ecs.soton.ac.uk [152.78.70.1]) h9QAjc3A024838 for ; Sun, 26 Oct 2003 05:45:39 -0500 (EST) Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1]) by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id KAA21702; Sun, 26 Oct 2003 10:45:37 GMT Received: from pandora (pandora [152.78.68.157]) by pigeon.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id KAA05414; Sun, 26 Oct 2003 10:43:44 GMT Newsgroups: bionet.journals.note Date: Sun, 26 Oct 2003 10:43:42 +0000 (GMT) From: Stevan Harnad X-Sender: harnad@pandora To: September 1998 American Scientist Forum In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Sun, 26 Oct 2003 09:47:08 -0500 Subject: [Dspace-general] Re: Berlin Declaration on Open Access X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Sun, 26 Oct 2003 10:45:41 -0000 Below is a web series of powerpoint slides. The first one is the excerpted core of the Berlin Declaration, followed by a series of suggestions about how the Declaration could be implemented by universities and research-funders. Please note that the implementation suggestions are my own; they are *not* part of the Berlin Declaration. http://www.ecs.soton.ac.uk/~harnad/Temp/berlin.htm The original powerpoints for the above are also available and permission is granted to anyone who wishes to use them in promoting open access. They are part of a longer series of powerpoints, also linked below, for which permission is likewise granted to use them to promote open access. (Please give credit to Tim Brody, my doctoral student, who helped me create them): http://www.ecs.soton.ac.uk/~harnad/Temp/berlin.ppt http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving.ppt http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving.htm Stevan Harnad NOTE: Complete archive of the ongoing discussion of providing open access to the peer-reviewed research literature online is available at the American Scientist September Forum (98 & 99 & 00 & 01 & 02 & 03): http://amsci-forum.amsci.org/archives/september98-forum.html http://www.cogsci.soton.ac.uk/~harnad/Hypermail/Amsci/index.html Posted discussion to: september98-forum@amsci-forum.amsci.org Dual Open-Access Strategy: BOAI-2: Publish your article in a suitable open-access journal whenever one exists. BOAI-1: Otherwise, publish your article in a suitable toll-access journal and also self-archive it. http://www.soros.org/openaccess/read.shtml From bialangiano@yahoo.com.br Mon Nov 3 07:59:06 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hA3Cx6qb013270 for ; Mon, 3 Nov 2003 07:59:06 -0500 (EST) Received: from web21506.mail.yahoo.com (web21506.mail.yahoo.com [66.163.169.17])hA3Cx593024452 for ; Mon, 3 Nov 2003 07:59:05 -0500 (EST) Message-ID: <20031103125905.43816.qmail@web21506.mail.yahoo.com> Received: from [200.17.212.1] by web21506.mail.yahoo.com via HTTP; Mon, 03 Nov 2003 09:59:05 ART Date: Mon, 3 Nov 2003 09:59:05 -0300 (ART) From: =?iso-8859-1?q?Beatriz=20Langiano?= To: dspace-general@mit.edu MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: [Dspace-general] thesaurus X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 03 Nov 2003 12:59:07 -0000 Hi, my name is Beatriz. I'd like to know how can I use thesaurus in dspace. Please, explain-me step by step. Thanks, Beatriz Yahoo! Mail - o melhor webmail do Brasil http://mail.yahoo.com.br From bialangiano@yahoo.com.br Mon Nov 3 08:46:53 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hA3Dkqqb016493 for ; Mon, 3 Nov 2003 08:46:52 -0500 (EST) Received: from web21507.mail.yahoo.com (web21507.mail.yahoo.com [66.163.169.18])hA3Dkq93018653 for ; Mon, 3 Nov 2003 08:46:52 -0500 (EST) Message-ID: <20031103134651.53764.qmail@web21507.mail.yahoo.com> Received: from [200.17.212.1] by web21507.mail.yahoo.com via HTTP; Mon, 03 Nov 2003 10:46:51 ART Date: Mon, 3 Nov 2003 10:46:51 -0300 (ART) From: =?iso-8859-1?q?Beatriz=20Langiano?= To: dspace-general@mit.edu MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: [Dspace-general] Exporting items X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 03 Nov 2003 13:46:53 -0000 Hi, I'm using the dsrun tool to export items of dspace, but I don't know how can I use the argument --number=seq_num. What is seq_num? Thanks, Beatriz Yahoo! Mail - o melhor webmail do Brasil http://mail.yahoo.com.br From margretb@MIT.EDU Mon Nov 3 12:14:55 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hA3HEtqb029837 for ; Mon, 3 Nov 2003 12:14:55 -0500 (EST) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72])hA3HEseQ001861; Mon, 3 Nov 2003 12:14:54 -0500 (EST) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])hA3HErho021930; Mon, 3 Nov 2003 12:14:53 -0500 (EST) Received: from dspace-01.mit.edu (DSPACE-01.MIT.EDU [18.51.2.146]) ) hA3HEq4f011175; Mon, 3 Nov 2003 12:14:52 -0500 (EST) Message-Id: <5.2.1.1.2.20031103113401.01cde818@po10.mit.edu> X-Sender: margretb@po10.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 03 Nov 2003 12:14:26 -0500 To: Beatriz Langiano , dspace-general@MIT.EDU From: Margret Branschofsky Subject: Re: [Dspace-general] thesaurus In-Reply-To: <20031103125905.43816.qmail@web21506.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_4588167==.ALT" X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 03 Nov 2003 17:14:56 -0000 --=====================_4588167==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Hello Beatriz, DSpace doesn't support the use of thesauri directly in the system at this time. However, our metadata does allow you to specify a classification system for subject fields (although the present submission interface does not yet support this.) In our next release you will be able to customize the metadata submission form to include the above fields and you will also be able to add drop-down boxes to all subject fields which you can use for controlled vocabulary, similar to the way the TYPE field now works. I hope this answers your question, Margret Branschofsky DSpace User Support Manager Digital Library Research Group Bldg. 14S-M24 (617)253-1293 margretb@mit.edu http://dspace.mit.edu At 09:59 AM 11/3/2003 -0300, Beatriz Langiano wrote: >Hi, my name is Beatriz. >I'd like to know how can I use thesaurus in dspace. >Please, explain-me step by step. >Thanks, Beatriz > > > >Yahoo! Mail - o melhor webmail do Brasil >http://mail.yahoo.com.br >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general --=====================_4588167==.ALT Content-Type: text/html; charset="us-ascii" Hello Beatriz,

DSpace doesn't support the use of thesauri directly in the system at this time.  However, our metadata does allow you to specify a classification system for subject fields (although the present submission interface does not yet support this.)

In our next release you will be able to customize the metadata submission form to include the above fields and you will also be able to add drop-down boxes to all subject fields which you can use for controlled vocabulary, similar to the way the TYPE field now works.

I hope this answers your question,

Margret Branschofsky
DSpace User Support Manager
Digital Library Research Group
Bldg. 14S-M24
(617)253-1293
margretb@mit.edu
http://dspace.mit.edu

 
At 09:59 AM 11/3/2003 -0300, Beatriz Langiano wrote:
Hi, my name is Beatriz.
I'd like to know how can I use thesaurus in dspace.
Please, explain-me step by step.
Thanks, Beatriz



Yahoo! Mail - o melhor webmail do Brasil
http://mail.yahoo.com.br
_______________________________________________
Dspace-general mailing list
Dspace-general@mit.edu
http://mailman.mit.edu/mailman/listinfo/dspace-general
--=====================_4588167==.ALT-- From bialangiano@yahoo.com.br Tue Nov 4 08:26:09 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hA4DQ9qb024568 for ; Tue, 4 Nov 2003 08:26:09 -0500 (EST) Received: from web21508.mail.yahoo.com (web21508.mail.yahoo.com [66.163.169.19])hA4DQ8og008596 for ; Tue, 4 Nov 2003 08:26:08 -0500 (EST) Message-ID: <20031104132607.33690.qmail@web21508.mail.yahoo.com> Received: from [200.17.212.1] by web21508.mail.yahoo.com via HTTP; Tue, 04 Nov 2003 10:26:07 ART Date: Tue, 4 Nov 2003 10:26:07 -0300 (ART) From: =?iso-8859-1?q?Beatriz=20Langiano?= Subject: Re: [Dspace-general] thesaurus To: Margret Branschofsky , dspace-general@MIT.EDU In-Reply-To: <5.2.1.1.2.20031103113401.01cde818@po10.mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 04 Nov 2003 13:26:10 -0000 Hello Margret, but a DSpace doesn't support the use of thesauri, how can I get this metadado and specify my "inferences" ? Thanks, Beatriz --- Margret Branschofsky escreveu: > Hello Beatriz, > > DSpace doesn't support the use of thesauri directly > in the system at this > time. However, our metadata does allow you to > specify a classification > system for subject fields (although the present > submission interface does > not yet support this.) > > In our next release you will be able to customize > the metadata submission > form to include the above fields and you will also > be able to add drop-down > boxes to all subject fields which you can use for > controlled vocabulary, > similar to the way the TYPE field now works. > > I hope this answers your question, > > Margret Branschofsky > DSpace User Support Manager > Digital Library Research Group > Bldg. 14S-M24 > (617)253-1293 > margretb@mit.edu > http://dspace.mit.edu > > > At 09:59 AM 11/3/2003 -0300, Beatriz Langiano wrote: > >Hi, my name is Beatriz. > >I'd like to know how can I use thesaurus in dspace. > >Please, explain-me step by step. > >Thanks, Beatriz > > > > > > > >Yahoo! Mail - o melhor webmail do Brasil > >http://mail.yahoo.com.br > >_______________________________________________ > >Dspace-general mailing list > >Dspace-general@mit.edu > >http://mailman.mit.edu/mailman/listinfo/dspace-general > Yahoo! Mail - 6MB, anti-spam e antivírus gratuito. Crie sua conta agora: http://mail.yahoo.com.br From margretb@MIT.EDU Tue Nov 4 11:48:12 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hA4GmCqb002197 for ; Tue, 4 Nov 2003 11:48:12 -0500 (EST) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72])hA4GmAhB023707; Tue, 4 Nov 2003 11:48:10 -0500 (EST) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])hA4GmAKu014642; Tue, 4 Nov 2003 11:48:10 -0500 (EST) Received: from dspace-01.mit.edu (pool-68-163-101-52.bos.east.verizon.net [68.163.101.52]) )hA4Gm74f006228; Tue, 4 Nov 2003 11:48:08 -0500 (EST) Message-Id: <5.2.1.1.2.20031104112126.01aa3d80@po10.mit.edu> X-Sender: margretb@po10.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Tue, 04 Nov 2003 11:47:41 -0500 To: Beatriz Langiano , dspace-general@MIT.EDU, dspace-tech@lists.sourceforge.net From: Margret Branschofsky Subject: Re: [Dspace-general] thesaurus In-Reply-To: <20031104132607.33690.qmail@web21508.mail.yahoo.com> References: <5.2.1.1.2.20031103113401.01cde818@po10.mit.edu> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_8372438==.ALT" X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 04 Nov 2003 16:48:13 -0000 --=====================_8372438==.ALT Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Hi Beatriz, Are you asking how to use metadata fields that are not supported in our=20 submission forms, like the following: subject. lcc - Library of Congress Classification Number subject. lcsh - Library of Congress Subject Heading subject. mesh - Medical Subject Headings subject.other? One way to include these is to use the item importer to get metadata into=20 DSpace. I'm copying this question to dspace-tech in case there are other=20 suggestions. Margret Branschofsky DSpace User Support Manager Digital Library Research Group Bldg. 14S-M24 (617)253-1293 margretb@mit.edu http://dspace.mit.edu Margret At 10:26 AM 11/4/2003 -0300, Beatriz Langiano wrote: >Hello Margret, but a DSpace doesn't support the use of >thesauri, how can I get this metadado and specify my >"inferences" ? > >Thanks, Beatriz > > > --- Margret Branschofsky escreveu: > > Hello Beatriz, > > > > DSpace doesn't support the use of thesauri directly > > in the system at this > > time. However, our metadata does allow you to > > specify a classification > > system for subject fields (although the present > > submission interface does > > not yet support this.) > > > > In our next release you will be able to customize > > the metadata submission > > form to include the above fields and you will also > > be able to add drop-down > > boxes to all subject fields which you can use for > > controlled vocabulary, > > similar to the way the TYPE field now works. > > > > I hope this answers your question, > > > > Margret Branschofsky > > DSpace User Support Manager > > Digital Library Research Group > > Bldg. 14S-M24 > > (617)253-1293 > > margretb@mit.edu > > http://dspace.mit.edu > > > > > > At 09:59 AM 11/3/2003 -0300, Beatriz Langiano wrote: > > >Hi, my name is Beatriz. > > >I'd like to know how can I use thesaurus in dspace. > > >Please, explain-me step by step. > > >Thanks, Beatriz > > > > > > > > > > > >Yahoo! Mail - o melhor webmail do Brasil > > >http://mail.yahoo.com.br > > >_______________________________________________ > > >Dspace-general mailing list > > >Dspace-general@mit.edu > > > >http://mailman.mit.edu/mailman/listinfo/dspace-general > > > >Yahoo! Mail - 6MB, anti-spam e antiv=EDrus gratuito. Crie sua conta agora: >http://mail.yahoo.com.br >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general --=====================_8372438==.ALT Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Beatriz,

Are you asking how to use metadata fields that are not supported in our submission forms, like the following:
subject. lcc  - Library of Congress Classification Number=20
subject. lcsh - Library of Congress Subject Heading=20
subject. mesh - Medical Subject Headings
subject.other?
One way to include these is to use the item importer to get metadata into DSpace.  I'm copying this question to dspace-tech in case there are other suggestions.   

Margret Branschofsky
DSpace User Support Manager
Digital Library Research Group
Bldg. 14S-M24
(617)253-1293
margretb@mit.edu
http://dspace.mit.edu

Margret



At 10:26 AM 11/4/2003 -0300, Beatriz Langiano wrote:
Hello Margret, but a DSpace doesn'= t support the use of
thesauri, how can I get this metadado and specify  my
"inferences" ?

Thanks, Beatriz


 --- Margret Branschofsky <margretb@MIT.EDU> escreveu:
> Hello Beatriz,
>
> DSpace doesn't support the use of thesauri directly
> in the system at this
> time.  However, our metadata does allow you to
> specify a classification
> system for subject fields (although the present
> submission interface does
> not yet support this.)
>
> In our next release you will be able to customize
> the metadata submission
> form to include the above fields and you will also
> be able to add drop-down
> boxes to all subject fields which you can use for
> controlled vocabulary,
> similar to the way the TYPE field now works.
>
> I hope this answers your question,
>
> Margret Branschofsky
> DSpace User Support Manager
> Digital Library Research Group
> Bldg. 14S-M24
> (617)253-1293
> margretb@mit.edu
> http://dspace.mit.edu
>
>
> At 09:59 AM 11/3/2003 -0300, Beatriz Langiano wrote:
> >Hi, my name is Beatriz.
> >I'd like to know how can I use thesaurus in dspace.
> >Please, explain-me step by step.
> >Thanks, Beatriz
> >
> >
> >
> >Yahoo! Mail - o melhor webmail do Brasil
> >http://mail.yahoo.com.br
> >_______________________________________________
> >Dspace-general mailing list
> >Dspace-general@mit.edu
>
>http://mailman.mit.edu/mailman/listinfo/dspace-general
> 

Yahoo! Mail - 6MB, anti-spam e antiv=EDrus gratuito. Crie sua conta agora:
http://mail.yahoo.com.br
_______________________________________________
Dspace-general mailing list
Dspace-general@mit.edu
http://mailman.mit.edu/mailman/listinfo/dspace-general
--=====================_8372438==.ALT-- From bialangiano@yahoo.com.br Tue Nov 4 14:24:23 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hA4JONqb013056 for ; Tue, 4 Nov 2003 14:24:23 -0500 (EST) Received: from web21509.mail.yahoo.com (web21509.mail.yahoo.com [66.163.169.58])hA4JOLH1004895 for ; Tue, 4 Nov 2003 14:24:21 -0500 (EST) Message-ID: <20031104192421.8666.qmail@web21509.mail.yahoo.com> Received: from [200.17.212.1] by web21509.mail.yahoo.com via HTTP; Tue, 04 Nov 2003 16:24:21 ART Date: Tue, 4 Nov 2003 16:24:21 -0300 (ART) From: =?iso-8859-1?q?Beatriz=20Langiano?= To: dspace-general@mit.edu MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: [Dspace-general] Import/ Export Items in DSpace X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 04 Nov 2003 19:24:23 -0000 Hello, my name is Beatriz. I'm studyind about DSpace and I'd like to import/expot some items. I'm using the "dsrun" tool, but this tool has command-line arguments, and I don't know what informations I must complete for this arguments. Somebody could explain me step by step this arguments? The command-line to export is: dsrun org.dspace.app.itemexport.ItemExport --type=COLLECTION --id=collID --dest=dest_dir --number=seq_num What accurately must I put in place of org.dspace.app.itemexport.ItemExport? And what is the seq_number? Thanks, Beatriz Yahoo! Mail - 6MB, anti-spam e antivírus gratuito. Crie sua conta agora: http://mail.yahoo.com.br From kenzie@MIT.EDU Wed Nov 5 00:34:10 2003 Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hA55Y9qb025521 for ; Wed, 5 Nov 2003 00:34:09 -0500 (EST) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])hA55XTI4012114; Wed, 5 Nov 2003 00:33:29 -0500 (EST) Received: from ADTPA.mit.edu (dsc03-ivn-ca-205-185-194-246.rasserver.net [205.185.194.246]) (authenticated bits=0) (User authenticated as kenzie@ATHENA.MIT.EDU)hA55XKDJ011215 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT); Wed, 5 Nov 2003 00:33:25 -0500 (EST) Message-Id: <5.2.1.1.2.20031105002219.016a1838@hesiod> X-Sender: kenzie@hesiod X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Wed, 05 Nov 2003 00:30:30 -0500 To: Beatriz Langiano , dspace-general@MIT.EDU From: MacKenzie Smith Subject: Re: [Dspace-general] Import/ Export Items in DSpace In-Reply-To: <20031104192421.8666.qmail@web21509.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id hA55Y9qb025521 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 05 Nov 2003 05:34:10 -0000 Hello Beatriz, These are pretty technical questions you're asking, so I think you might have more success if you post them to the dspace-tech list, to which you can subscribe on the DSpace page at SourceForge. You can also take a look at the public documentation on the import/export functions which address your questions here: http://dspace.org/technology/system-docs/application.html#itemimporter Best wishes, MacKenzie Smith At 04:24 PM 11/4/2003 -0300, Beatriz Langiano wrote: >Hello, my name is Beatriz. > >I'm studyind about DSpace and I'd like to import/expot >some items. I'm using the "dsrun" tool, >but this tool has command-line arguments, and I don't >know what informations I must complete for this >arguments. >Somebody could explain me step by step this arguments? > > >The command-line to export is: > >dsrun org.dspace.app.itemexport.ItemExport >--type=COLLECTION --id=collID --dest=dest_dir >--number=seq_num > > >What accurately must I put in place of >org.dspace.app.itemexport.ItemExport? > >And what is the seq_number? > >Thanks, Beatriz > > >Yahoo! Mail - 6MB, anti-spam e antivírus gratuito. Crie sua conta agora: >http://mail.yahoo.com.br >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general MacKenzie Smith Associate Director for Technology MIT Libraries Building 14S-208 77 Massachusetts Avenue Cambridge, MA 02139 (617)253-8184 kenzie@mit.edu From bialangiano@yahoo.com.br Wed Nov 5 09:36:51 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hA5Eaoqb002170 for ; Wed, 5 Nov 2003 09:36:50 -0500 (EST) Received: from web21501.mail.yahoo.com (web21501.mail.yahoo.com [66.163.169.12])hA5EanHj021060 for ; Wed, 5 Nov 2003 09:36:49 -0500 (EST) Message-ID: <20031105143649.8419.qmail@web21501.mail.yahoo.com> Received: from [200.17.212.1] by web21501.mail.yahoo.com via HTTP; Wed, 05 Nov 2003 11:36:49 ART Date: Wed, 5 Nov 2003 11:36:49 -0300 (ART) From: =?iso-8859-1?q?Beatriz=20Langiano?= To: Dspace-general@mit.edu MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: [Dspace-general] Export Item X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 05 Nov 2003 14:36:51 -0000 Hi, I need export items of my dspace system . So I'm using the dsrun command line tool. Somebody could explain me what is the first argument of this command? The command is : dsrun "org.dspace.app.itemexport.ItemExport" ..... what must I put in place of this? Thanks, Beatriz Yahoo! Mail - 6MB, anti-spam e antivírus gratuito. Crie sua conta agora: http://mail.yahoo.com.br From gabriela.mircea@utoronto.ca Wed Nov 5 09:49:18 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hA5EnIqb002462 for ; Wed, 5 Nov 2003 09:49:18 -0500 (EST) Received: from bureau8.utcc.utoronto.ca (bureau8.utcc.utoronto.ca [128.100.132.18])hA5EnDHj028735 for ; Wed, 5 Nov 2003 09:49:14 -0500 (EST) Received: from utl-194-187.library.utoronto.ca ([142.150.194.187] EHLO utoronto.ca ident: IDENT-NOT-QUERIED [port 4265]) by bureau8.utcc.utoronto.ca with ESMTP id <25245-25832>; Wed, 5 Nov 2003 09:48:26 -0500 Message-ID: <3FA90DBA.6040704@utoronto.ca> Date: Wed, 05 Nov 2003 09:48:26 -0500 From: Gabriela Mircea User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.01 MIME-Version: 1.0 To: Beatriz Langiano Subject: Re: [Dspace-general] Export Item References: <20031105143649.8419.qmail@web21501.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit cc: Dspace-general@mit.edu X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 05 Nov 2003 14:49:19 -0000 Hi Beatriz, Below is an example: dsrun org.dspace.app.itemexport.ItemExport COLLECTION 1 /home/dspace/export 1 seq_num - can be any number; "The exporter will begin numbering the simple archives with the sequence number that you supply" dest_dir - any directory; it has to be created before you start exporting collID - the internal ID of the collection; in the admin UI Communities/ Collections is the "DB ID" (on the same line with the collection name) I hope this helps, Gabriela Beatriz Langiano wrote: >Hi, >I need export items of my dspace system . So I'm using >the dsrun command line tool. >Somebody could explain me what is the first argument >of this command? >The command is : > >dsrun "org.dspace.app.itemexport.ItemExport" ..... > >what must I put in place of this? >Thanks, Beatriz > > > > > >Yahoo! Mail - 6MB, anti-spam e antivírus gratuito. Crie sua conta agora: >http://mail.yahoo.com.br >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general > > -- Gabriela Mircea Information Technology Services Robarts Library, 130 St. George St. Toronto, ON, Canada, M5S 1A5 416 946 0114 From bialangiano@yahoo.com.br Fri Nov 7 08:33:45 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hA7DXjqb010354 for ; Fri, 7 Nov 2003 08:33:45 -0500 (EST) Received: from web21508.mail.yahoo.com (web21508.mail.yahoo.com [66.163.169.19])hA7DXiDU018260 for ; Fri, 7 Nov 2003 08:33:44 -0500 (EST) Message-ID: <20031107133344.50455.qmail@web21508.mail.yahoo.com> Received: from [200.17.212.1] by web21508.mail.yahoo.com via HTTP; Fri, 07 Nov 2003 10:33:44 ART Date: Fri, 7 Nov 2003 10:33:44 -0300 (ART) From: =?iso-8859-1?q?Beatriz=20Langiano?= To: Lista Dspace MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: [Dspace-general] Import Item X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Fri, 07 Nov 2003 13:33:46 -0000 Hi, I'm trying to add a item to dspace, so I'm using the dsrun tool. The comand is: dsrun org.dspace.app.itemimport.ItemImport --add --eperson=joe@user.com --collection=collectionID --source=items_dir --mapfile=mapfile What exactaly is the mapfile argument? I read the help, but I didn't understand. Thanks, Beatriz Yahoo! Mail - 6MB, anti-spam e antivírus gratuito. Crie sua conta agora: http://mail.yahoo.com.br From dovey@datatext.co.za Thu Nov 13 04:11:06 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hAD9B5qb019009 for ; Thu, 13 Nov 2003 04:11:06 -0500 (EST) Received: from maties2.sun.ac.za (maties2.sun.ac.za [146.232.128.10]) hAD9B3W9027636 for ; Thu, 13 Nov 2003 04:11:04 -0500 (EST) Received: from k1027.jsg.sun.ac.za ([146.232.74.235] helo=Dovey1) by maties2.sun.ac.za with smtp (Exim 4.05) id 1AKDVB-00078R-00 for dspace-general@mit.edu; Thu, 13 Nov 2003 11:10:57 +0200 Message-ID: <017001c3a9c6$0cbbf850$eb4ae892@stb.sun.ac.za> From: "John Dovey" To: References: <20031107133344.50455.qmail@web21508.mail.yahoo.com> Date: Thu, 13 Nov 2003 11:10:57 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *1AKDVB-00078R-00*PRjxHYJxG/s* Subject: [Dspace-general] Fedora install of Dspace X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Thu, 13 Nov 2003 09:11:07 -0000 Could I ask whether anyone has installed Dspace on Fedora Core 1 and if so what Gotchas there might be? Thanx John From tsf@cogeco.ca Mon Nov 17 13:20:31 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hAHIKVqb010613 for ; Mon, 17 Nov 2003 13:20:31 -0500 (EST) Received: from fep3.cogeco.net (smtp.cogeco.net [216.221.81.25]) hAHIKShu006796 for ; Mon, 17 Nov 2003 13:20:30 -0500 (EST) Received: from customer (d235-152-216.home1.cgocable.net [24.235.152.216]) by fep3.cogeco.net (Postfix) with SMTP id 915B31297 for ; Mon, 17 Nov 2003 13:20:23 -0500 (EST) Message-ID: <002501c3ad37$9f772ce0$d898eb18@pego2.on.cogeco.ca> From: "M. Dale Rodger" To: Date: Mon, 17 Nov 2003 13:21:24 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Subject: [Dspace-general] X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 17 Nov 2003 18:20:32 -0000 tsf@cogeco.ca From bialangiano@yahoo.com.br Tue Nov 18 11:49:18 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hAIGnIqb027344 for ; Tue, 18 Nov 2003 11:49:18 -0500 (EST) Received: from web21501.mail.yahoo.com (web21501.mail.yahoo.com [66.163.169.12])hAIGnHPZ028418 for ; Tue, 18 Nov 2003 11:49:17 -0500 (EST) Message-ID: <20031118164916.51695.qmail@web21501.mail.yahoo.com> Received: from [200.17.212.1] by web21501.mail.yahoo.com via HTTP; Tue, 18 Nov 2003 13:49:16 ART Date: Tue, 18 Nov 2003 13:49:16 -0300 (ART) From: =?iso-8859-1?q?Beatriz=20Langiano?= To: DSpace tech list , Lista Dspace MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: [Dspace-general] Electronics magazines X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 18 Nov 2003 16:49:19 -0000 Hi, Is possible submit electronics magazines in dspace? In general, what must be done to work with this magazines in Dspace? Thanks, Beatriz ______________________________________________________________________ Yahoo! Mail: 6MB, anti-spam e antivírus gratuito! Crie sua conta agora: http://mail.yahoo.com.br From bialangiano@yahoo.com.br Tue Nov 25 10:17:52 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hAPFHqqb015946 for ; Tue, 25 Nov 2003 10:17:52 -0500 (EST) Received: from web21509.mail.yahoo.com (web21509.mail.yahoo.com [66.163.169.58])hAPFHoLi025970 for ; Tue, 25 Nov 2003 10:17:51 -0500 (EST) Message-ID: <20031125151748.6061.qmail@web21509.mail.yahoo.com> Received: from [200.17.212.1] by web21509.mail.yahoo.com via HTTP; Tue, 25 Nov 2003 12:17:48 ART Date: Tue, 25 Nov 2003 12:17:48 -0300 (ART) From: =?iso-8859-1?q?Beatriz=20Langiano?= To: DSpace tech list , Lista Dspace MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: [Dspace-general] Elestronic Magazines in DSpace X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 25 Nov 2003 15:17:52 -0000 Hi, I'm student of a brazilian university and we'd like to submitted electronic magazines in our DSpace, but we don't know how do this. In terms of workflow steps, does somebody know what is necessary we change them to do this? Does somebody knows any university that use electronic magazines in DSpace? Thanks, Beatriz ______________________________________________________________________ Yahoo! Mail: 6MB, anti-spam e antivírus gratuito! Crie sua conta agora: http://mail.yahoo.com.br From kenzie@MIT.EDU Tue Nov 25 17:10:08 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hAPMA8qb025959 for ; Tue, 25 Nov 2003 17:10:08 -0500 (EST) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72])hAPMA7G8017395; Tue, 25 Nov 2003 17:10:07 -0500 (EST) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])hAPM8R6G004935; Tue, 25 Nov 2003 17:09:08 -0500 (EST) Received: from ADTPA.mit.edu (ADTPA.MIT.EDU [18.51.1.92]) (authenticated bits=0) (User authenticated as kenzie@ATHENA.MIT.EDU)hAPM6YZs002639 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT); Tue, 25 Nov 2003 17:06:34 -0500 (EST) Message-Id: <5.2.1.1.2.20031125164547.011a81d0@hesiod> X-Sender: kenzie@hesiod X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Tue, 25 Nov 2003 17:03:19 -0500 To: DSpace tech list , Lista Dspace From: MacKenzie Smith Subject: Re: [Dspace-general] Elestronic Magazines in DSpace In-Reply-To: <20031125151748.6061.qmail@web21509.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id hAPMA8qb025959 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 25 Nov 2003 22:10:08 -0000 Hello Beatriz, I think the reason no one has answered your question yet is that it's a little too vague and doesn't give any context to your problem. For example, I'm not sure what you mean by "electronic magazines". Are you talking about websites? Or PDFs? Are these commercially published (so copyright restricted) or not? Is there already metadata for them, or would someone have to create that? As to what workflow steps you need to define, that is completely up to you to decide, depending on your local policies about what you'll accept into the system. You can deposit the material directly using the batch upload tools, or create a special workflow with additional steps to do metadata editing, quality control, and so on. It depends on who will be doing the work, what their relationship to the system is, and how much you care about the quality of the results. There is no single answer to your question. If your question is really just technical (e.g. how do I setup a workflow for a new collection) then you can find this in the system documentation or ask again on the dspace-tech list with more detail. Otherwise could you try to make your question a little more specific? I'm sure someone can help you out a little. Best wishes, MacKenzie/ At 12:17 PM 11/25/2003 -0300, Beatriz Langiano wrote: >Hi, > >I'm student of a brazilian university and we'd like to >submitted electronic magazines in our DSpace, but we >don't know how do this. >In terms of workflow steps, does somebody know what is >necessary we change them to do this? >Does somebody knows any university that use electronic >magazines in DSpace? > >Thanks, Beatriz > > > > > >______________________________________________________________________ > >Yahoo! Mail: 6MB, anti-spam e antivírus gratuito! Crie sua conta agora: >http://mail.yahoo.com.br >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general MacKenzie Smith Associate Director for Technology MIT Libraries Building 14S-208 77 Massachusetts Avenue Cambridge, MA 02139 (617)253-8184 kenzie@mit.edu From Francis.Brouns@ou.nl Tue Dec 2 08:54:48 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hB2Dsmqb013394 for ; Tue, 2 Dec 2003 08:54:48 -0500 (EST) Received: from aix-4.ouh.nl (relay.ouh.nl [145.20.126.12]) hB2DslZE007017 for ; Tue, 2 Dec 2003 08:54:47 -0500 (EST) Received: (from root@localhost) by aix-4.ouh.nl (8.12.10.Beta2/8.12.10.Beta2) id hB2DsksB195820 for dspace-general@mit.edu; Tue, 2 Dec 2003 14:54:46 +0100 Received: from srv-hrl-18.pwo.ou.nl (exch-owa.ou.nl [145.20.33.20]) hB2DsW2t195812 for ; Tue, 2 Dec 2003 14:54:37 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Date: Tue, 2 Dec 2003 14:54:29 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Dspace bitstream formats Thread-Index: AcO42844P+FCEq+PTPuEJbXx0GYuLg== From: "Francis Brouns" To: X-Virus-Scanned: by amavisd-new Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id hB2Dsmqb013394 Subject: [Dspace-general] Dspace bitstream formats X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 02 Dec 2003 13:54:49 -0000 Hello, we recently installed Dspace and are exploring its' features. The documentation describes that there are 3 types of bitstream formats in Dspace: supported, known and unknown. So are PDF, text and XML supported formats. However, in our Dspace application all these formats are listed as known, not as supported. Is this something we should worry about or correct? The admin tool for the Bitstream Format Registry allows the 'supported' option. Kind regards, Francis Brouns From Francis.Brouns@ou.nl Tue Dec 2 09:01:54 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hB2E1sqb014556 for ; Tue, 2 Dec 2003 09:01:54 -0500 (EST) Received: from aix-4.ouh.nl (mailserv2.ouh.nl [145.20.126.12]) hB2E1r4I012204 for ; Tue, 2 Dec 2003 09:01:53 -0500 (EST) Received: (from root@localhost) by aix-4.ouh.nl (8.12.10.Beta2/8.12.10.Beta2) id hB2E1qPa401250 for dspace-general@mit.edu; Tue, 2 Dec 2003 15:01:52 +0100 Received: from srv-hrl-18.pwo.ou.nl (exch-owa.ou.nl [145.20.33.20]) hB2E1i2t401242 for ; Tue, 2 Dec 2003 15:01:44 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Date: Tue, 2 Dec 2003 15:01:40 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: hiding communities or collections Thread-Index: AcO43M9LOY9+yeEmTs+r8Q3idgnm/Q== From: "Francis Brouns" To: X-Virus-Scanned: by amavisd-new Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id hB2E1sqb014556 Subject: [Dspace-general] hiding communities or collections X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 02 Dec 2003 14:01:55 -0000 Hello, we plan to use Dspace for our organisation. The intention is to create communities and collections that are publicly available, but also several that are restricted to internal use. This is a mixed model. For example we have a community for which most collections are available to the public but one or two are intended for internal use. We can prevent unregistered users from submitting items to these collections. However, we would like to hide them at all from unregistered users. Is this possible? Kind regards, Francis Brouns From Francis.Brouns@ou.nl Tue Dec 2 09:47:57 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hB2Elvqb015263 for ; Tue, 2 Dec 2003 09:47:57 -0500 (EST) Received: from aix-4.ouh.nl (ns.ouh.nl [145.20.126.12])hB2EluZE006844 for ; Tue, 2 Dec 2003 09:47:56 -0500 (EST) Received: (from root@localhost) by aix-4.ouh.nl (8.12.10.Beta2/8.12.10.Beta2) id hB2Elts0401274 for dspace-general@mit.edu; Tue, 2 Dec 2003 15:47:55 +0100 Received: from srv-hrl-18.pwo.ou.nl (exch-owa.ou.nl [145.20.33.20]) hB2Elk2t401266 for ; Tue, 2 Dec 2003 15:47:47 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Date: Tue, 2 Dec 2003 15:47:43 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: servlet.jar Thread-Index: AcO44z4Fj9/4BSUMS4mGksZ8ApoItw== From: "Francis Brouns" To: X-Virus-Scanned: by amavisd-new Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id hB2Elvqb015263 Subject: [Dspace-general] servlet.jar X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 02 Dec 2003 14:47:57 -0000 Hello, we recently installed DSpace and see the following message in catalina.out: Starting service Tomcat-Standalone Apache Tomcat/4.1.24 WebappClassLoader: validateJarFile(/opt/jakarta/tomcat/webapps/dspace-oai/WEB-INF/lib/servl et.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class WebappClassLoader: validateJarFile(/opt/jakarta/tomcat/webapps/ROOT/WEB-INF/lib/servlet.jar ) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class Apparently servlet.jar is not loaded. We installed Dspace 1.1.1. on Suse 8, following the guidelines for a Tomcat Standalone installation. Tomcat version is 4.1.24. servlet.jar is present in the Dspace WEB-INF directory. How can we correct this? Kind regards, Francis Brouns From robert.tansley@hp.com Tue Dec 2 17:10:47 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hB2MAkqb022666 for ; Tue, 2 Dec 2003 17:10:46 -0500 (EST) Received: from palrel10.hp.com (palrel10.hp.com [156.153.255.245]) hB2MAi4I013417 for ; Tue, 2 Dec 2003 17:10:45 -0500 (EST) Received: from hplms2.hpl.hp.com (hplms2.hpl.hp.com [15.0.152.33]) by palrel10.hp.com (Postfix) with ESMTP id 8719B1C00B29; Tue, 2 Dec 2003 14:10:44 -0800 (PST) Received: from hplex1.hpl.hp.com (hplex1.hpl.hp.com [15.0.152.182]) hB2MAhQZ017741; Tue, 2 Dec 2003 14:10:44 -0800 (PST) Received: from 15.0.152.182 by hplex1.hpl.hp.com (InterScan E-Mail VirusWall NT); Tue, 02 Dec 2003 14:10:43 -0800 Received: by hplex1.hpl.hp.com with Internet Mail Service (5.5.2653.19) id ; Tue, 2 Dec 2003 14:10:43 -0800 Message-ID: <40700B4C02ABD5119F00009027876644084DF331@hplex1.hpl.hp.com> From: "Tansley, Robert" To: Francis Brouns , dspace-general@mit.edu Subject: RE: [Dspace-general] hiding communities or collections Date: Tue, 2 Dec 2003 14:10:42 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 02 Dec 2003 22:10:47 -0000 > we plan to use Dspace for our organisation. The intention is > to create communities and collections that are publicly > available, but also several that are restricted to internal > use. This is a mixed model. For example we have a community > for which most collections are available to the public but > one or two are intended for internal use. We can prevent > unregistered users from submitting items to these > collections. However, we would like to hide them at all from > unregistered users. Is this possible? Hello, This isn't possible at present. The authorisation system in DSpace does let you specify READ permission for communities and collections but at the moment the UI will display all communities and collections regardless. However, the code changes to hide communities and collections wouldn't be that great. Robert Tansley / Hewlett-Packard Laboratories / (+1) 617 551 7624 From robert.tansley@hp.com Tue Dec 2 17:16:24 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hB2MGOqb022754 for ; Tue, 2 Dec 2003 17:16:24 -0500 (EST) Received: from palrel10.hp.com (palrel10.hp.com [156.153.255.245]) hB2MGM4I018082 for ; Tue, 2 Dec 2003 17:16:22 -0500 (EST) Received: from hplms2.hpl.hp.com (hplms2.hpl.hp.com [15.0.152.33]) by palrel10.hp.com (Postfix) with ESMTP id E8FF61C02150; Tue, 2 Dec 2003 14:16:21 -0800 (PST) Received: from hplex1.hpl.hp.com (hplex1.hpl.hp.com [15.0.152.182]) hB2MGKQZ018233; Tue, 2 Dec 2003 14:16:21 -0800 (PST) Received: from 15.0.152.182 by hplex1.hpl.hp.com (InterScan E-Mail VirusWall NT); Tue, 02 Dec 2003 14:16:20 -0800 Received: by hplex1.hpl.hp.com with Internet Mail Service (5.5.2653.19) id ; Tue, 2 Dec 2003 14:16:20 -0800 Message-ID: <40700B4C02ABD5119F00009027876644084DF332@hplex1.hpl.hp.com> From: "Tansley, Robert" To: Francis Brouns , dspace-general@mit.edu Subject: RE: [Dspace-general] Dspace bitstream formats Date: Tue, 2 Dec 2003 14:16:19 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 02 Dec 2003 22:16:25 -0000 > Hello, > > we recently installed Dspace and are exploring its' features. > The documentation describes that there are 3 types of > bitstream formats in > Dspace: supported, known and unknown. So are PDF, text and > XML supported formats. However, in our Dspace application all > these formats are listed as known, not as supported. > > Is this something we should worry about or correct? The admin > tool for the Bitstream Format Registry allows the 'supported' option. The 'support level' for a Bitstream Format is intended to show your users what level of support *you* (the institution running DSpace) will give Bitstreams in that format. This is explained in the functional overview section of the documentation: http://dspace.org/technology/system-docs/functional.html#data_model The DSpace code ships with all of the levels as 'known'; that's because we don't want to presume what level of support and commitment your institution will give your users for each format. You should review the registry yourself and set the support levels as you feel is appropriate. Robert Tansley / Hewlett-Packard Laboratories / (+1) 617 551 7624 From kenzie@MIT.EDU Fri Dec 5 18:40:40 2003 Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hB5Nedqb001605 for ; Fri, 5 Dec 2003 18:40:39 -0500 (EST) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])hB5NedDe007293 for ; Fri, 5 Dec 2003 18:40:39 -0500 (EST) Received: from ADTPA.mit.edu (ADTPA.MIT.EDU [18.51.1.92]) (authenticated bits=0) (User authenticated as kenzie@ATHENA.MIT.EDU)hB5NecRw009092 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Fri, 5 Dec 2003 18:40:39 -0500 (EST) Message-Id: <5.2.1.1.2.20031205183240.01e6af78@hesiod> X-Sender: kenzie@hesiod X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Fri, 05 Dec 2003 18:37:07 -0500 To: dspace-general@MIT.EDU From: MacKenzie Smith Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Dspace-general] DSpace user group meeting in March 2004 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Fri, 05 Dec 2003 23:40:40 -0000 Greetings all, This is an advance notice that on March 10 and 11th, 2004, the MIT Libraries will host an open invitation DSpace user group meeting on the MIT campus. In early January we will set up a registration page on the DSpace Federation website at http://dspace.org/ with the logistics, and send out a call for presentations. The DSpace software has just turned 1, and its use by institutions world-wide continues to grow, and to move from experimental and pilot projects into production institutional repository services. Users of the software have asked us for an opportunity to get together and hear about what's going on at MIT and HP, and at other institutions that are using and improving the system. We would also like to use this opportunity to get input from the greater community of DSpace users about the Federation and how they would like it to be shaped to meet their needs. The format will be two days, including presentations from other projects and organizations who want to communicate or collaborate with the DSpace Federation, as well as DSpace users who have interesting ideas to communicate to their peers about the system and its uses. We will reserve the last half day for discussion of the future of the DSpace Federation. Note that this will *not* be a how-to workshop on DSpace -- there will be other opportunities for that in the coming year. Stay tuned for more information in the near future, and we hope to see you in March! MacKenzie Smith Associate Director for Technology MIT Libraries Building 14S-208 77 Massachusetts Avenue Cambridge, MA 02139 (617)253-8184 kenzie@mit.edu From harnad@ecs.soton.ac.uk Mon Dec 8 12:07:09 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hB8H79qb008041 for ; Mon, 8 Dec 2003 12:07:09 -0500 (EST) Received: from raven.ecs.soton.ac.uk (raven.ecs.soton.ac.uk [152.78.70.1]) hB8H78XE019913 for ; Mon, 8 Dec 2003 12:07:08 -0500 (EST) Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1]) by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id RAA24439; Mon, 8 Dec 2003 17:06:55 GMT Received: from pandora (pandora [152.78.68.157]) by pigeon.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id RAA06924; Mon, 8 Dec 2003 17:06:54 GMT Newsgroups: bionet.journals.note Date: Mon, 8 Dec 2003 17:06:52 +0000 (GMT) From: Stevan Harnad X-Sender: harnad@pandora To: American Scientist Open Access Forum In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information X-ECS-MailScanner: Found to be clean cc: dspace-general@mit.edu Subject: [Dspace-general] Re: Estimates on data and cost per department for institutional archives? X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 08 Dec 2003 17:07:10 -0000 On Mon, 8 Dec 2003, JQ Johnson wrote: > At most institutions the average annual peer-reviewed production [per > author is]... minuscule, even if you are successful in getting widespread > adoption by your faculty... > Let's say you got total buy-in... > [A]lthough the cost of storage and server is minimal, the cost of archival > is potentially very large. > If you agree with Stevan you don't care much about long-term access. > We don't agree... There is a deep misunderstanding here, and its elements are all there in the foregoing paragraph. The critical phrase is: "if you are successful in getting widespread adoption by your faculty... Let's say you got total buy-in..." This assumption is the logical equivalent of: "Let's say you win the lottery..." [and then going on to describe how you will spend the prize-money]! There is also an element of embalming Peter in order to preserve Paul! (1) Today, as we speak, the canonical digital texts of the articles we are talking here about preserving are being sold by publishers and bought by libraries and inaccessible to most because of the access-toll-barriers. (2) The *contents* of these texts are the ones to which we seek to provide free access for those researchers whose institutions cannot afford the access-tolls. (3) So we (the authors and their institutions) provide a *supplementary* text, a home-brewed version of the canonical one that is still being bought and sold by the publishers and libraries, and we self-archive it in our institutional archives. (4) Or rather, we *could* self-archive it, and we *should* self-archive it, but alas most of us still do not self-archive it. (5) In other words, we are still far from having met the "widespread adoption/total buy-in" precondition that is blithely being assumed in the above passage! (6) More important, one of the reasons we have not met those preconditions is that faculty think they have enough burdens already; and libraries certainly have enough burdens too. (7) So it looks quite unlikely that what will get faculty to just go ahead and do it will be to add or even mention any further burdens (viz. the putative "preservation" burden). (8) What we need to do is lighten up and focus on the task. (9) And that task is getting more faculty (*all* faculty) to provide open-access *now* (by self-archiving a supplementary version of each of their peer-reviewed publications in their institutional archives). (10) Are we sloughing off a substantive responsibility in focusing solely on immediate open-access provision? Is the long-term fate of these (mostly non-existent) supplementary versions a real issue? (11) No, the real issue is not the long-term fate of non-existent supplements to the canonical versions (the real ones with the real preservation burden); the real issue is the non-existence of the immediate open access to all peer-reviewed publications that those supplements would have provided. (12) if they were not being held back by (among other things) spurious preservation worries! http://www.eprints.org/self-faq/#1.Preservation (13) Spurious not just because self-archived supplements are merely the copies and not the originals -- those self-same originals that would have their (real) preservation burdens regardless of whether or not the non-existent supplements about whose preservation we are worrying, existed. (14) But spurious also because what little supplementary self-archiving has been done across the past 12 years (e.g., the 250,000 papers growing in the Physics ArXiv since 1991) is all alive and well and fully as openly-accessible today as it was when it was first self-archived 12 years ago, thank you very much! (15) So it does not look as if even the immediate open-access windfall, supplementing the toll-access canon (with its preservation burden) is at any imminent risk of being snatched back from us, in those few cases where we have actually troubled to provide the open access. (16) What will follow from successfully winning the lottery is a matter for pure speculation. (17) But should it turn out that once the supplementary corpus -- and hence open access to the entire refereed literature -- is complete, it forces the providers of the toll-access corpus to cut costs and downsize in such a way that they are no longer providing the digital texts of the primary corpus (but only the peer-review and certification), offloading it instead, from that day onward, onto the network of institutional open-access archives. (18) Starting then, and only then, on that happy day, do we need to begin worrying about the long-term preservation of what until then was merely a supplementary corpus, but, from that day forward, also takes over the burden of being the primary, canonical corpus. (19) Before that, though, we need to win the lottery. (20) And the lottery will not be one by fretting or fantasizing about how you will will either preserve or spend your non-existent winnings. Of course, the library community is in the profession of assuming responsibility for the preservation of contents, whether analog or digital. And their perennity horizons are far, far vaster than just the annual 2.5 million articles that appear in the planet's 24,000 journals. But it is important that they not let their ex officio responsibility for preservation Writ Large get in the way of the winning of the lottery here: that they not subsume the non-existent preservation burden for this non-existent supplementary open-access corpus under their preservation efforts on behalf of many other kinds of contents, including: > [The] natural extension... to collect[ing] supporting materials > for... preprints [such as] multi-TB dataset[s] in some fields such > as astronomy or biology. It only takes one such large dataset to > completely blow away any space calculations based only on collecting > the paper-publishable text. May I make a suggestion? Reckon the space separately, and don't burden the empty open-access-article shelves with the altogether distinct preservation and capacity demands of supporting datasets: "Refereed Research Archiving and Data Archiving" http://www.ecs.soton.ac.uk/~harnad/Hypermail/Amsci/1582.html http://www.ecs.soton.ac.uk/~harnad/Temp/data-archiving.htm Or, to put it another way, don't make the purchase of an open-access lottery ticket contingent on buying into a data-archiving lottery ticket too! > Even if you are collecting just > preprints and theses, the size estimates depend on how you are handling > acquisition of multimedia materials; if you collect theses in dance you > might have videos of performances, each of which is several GB. Preprints and theses are extras, freebies. Our primary, secondary, and tertiary target here is the peer-reviewed journal literature, 24,000 journals-full, 2,500,000 articles annually. A few new journals may be multimedia. Don't worry about them. Keep the goal in focus: It's those 24,000 journals, almost all of which have both a paper edition and an online version of it, identical except for the medium. Don't handicap the self-archiving of the 2,499,000 yearly non-multimedia articles that are also non-open-access with the newfound extras of the few yearly multimedia articles in peer-reviewed journals. > [aside: we believe that if we DON'T > collect such unprintable items we'll never get faculty buy-in for > Stevan's laudable goal of collecting the printable peer-reviewed works] But *why* do you feel that? Is there any evidence for a correlation between making an archive capable of storing uprintable items and successfully opening the sluice-gates of self-archiving? I can only echo the sentiments of: "Re: EPrints, DSpace or ESpace?" http://www.ecs.soton.ac.uk/~harnad/Hypermail/Amsci/2837.html As long as our institutional archiving efforts keep running off in all directions, they will get nowhere. A fence should be built around our focussed open-access provision efforts for our refereed article output, separating them for all spurious distractions and burdens. http://www.ecs.soton.ac.uk/~harnad/Temp/archpolnew.html Stevan Harnad NOTE: A complete archive of the ongoing discussion of providing open access to the peer-reviewed research literature online is available at the American Scientist Open Access Forum (98 & 99 & 00 & 01 & 02 & 03): http://amsci-forum.amsci.org/archives/september98-forum.html http://www.cogsci.soton.ac.uk/~harnad/Hypermail/Amsci/index.html Post discussion to: september98-forum@amsci-forum.amsci.org Dual Open-Access-Provision Policy: BOAI-2 ("gold"): Publish your article in a suitable open-access journal whenever one exists. BOAI-1 ("green"): Otherwise, publish your article in a suitable toll-access journal and also self-archive it. http://www.soros.org/openaccess/read.shtml http://www.ecs.soton.ac.uk/~harnad/Temp/berlin.htm http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving_files/Slide0026.gif http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving_files/Slide0021.gif http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving_files/Slide0024.gif http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving_files/Slide0028.gif From harnad@ecs.soton.ac.uk Mon Dec 8 17:48:51 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hB8Mmoqb014097 for ; Mon, 8 Dec 2003 17:48:50 -0500 (EST) Received: from raven.ecs.soton.ac.uk (raven.ecs.soton.ac.uk [152.78.70.1]) hB8Mmnkl018992 for ; Mon, 8 Dec 2003 17:48:50 -0500 (EST) Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1]) by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id WAA01638; Mon, 8 Dec 2003 22:48:45 GMT Received: from pandora (pandora [152.78.68.157]) by pigeon.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id WAA18924; Mon, 8 Dec 2003 22:48:43 GMT Newsgroups: bionet.journals.note Date: Mon, 8 Dec 2003 22:48:41 +0000 (GMT) From: Stevan Harnad X-Sender: harnad@pandora To: American Scientist Open Access Forum In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information X-ECS-MailScanner: Found to be clean cc: dspace-general@mit.edu Subject: [Dspace-general] Re: Estimates on data and cost per department for institutional archives? X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 08 Dec 2003 22:48:51 -0000 JQ Johnson wrote: > please note that I have replied only to one of the lists > you CCed. Subscribers to the other lists may like me get multiple > copies of your posts. If not, they don't have the context of Kan's > original question. This entire thread is archived and accessible at: "Estimates on data and cost per department for institutional archives?" http://www.ecs.soton.ac.uk/~harnad/Hypermail/Amsci/3247.html > The "total buyin" scenario puts an upper bound on the size of > the archive. That upper bound is quite small, so the reductio > argument leads one to conclude that disk space is not an issue for > [p]reprints. I think that's a conclusion you would agree with. Agreed. But I am talking about eprints, which means (optionally) unrefereed preprints and (essentially) refereed postprints. http://www.eprints.org/self-faq/#What-is-Eprint The 1st, 2nd, and 3rd purpose of the open access movement is to provide free, full-text online access to all of the articles (2.5 million annually) published in the planet's 24,000 refereed journals. That means the refereed version of the article is the essential target; providing access to that is the essential function of the archive; and the rest are just bonuses, which must not be allowed to get in the way of the essentials. > You also seem to miss the point that many of us disagree > with you about the goals/conceptualizaion of an institutional > repository. Slightly different conceptualizations from yours, for > instance the decision that the repository should hold, in addition > to surrogates for published papers, the canonical copies of working > papers or supplementary materials, can lead to very big differences > in one's sizing expectations and budget for the repository. No, I think I fully understand that point. But it is in the interests of at last providing access to the essentials -- the peer-reviewed research literature, which is what the open-access movement is about -- that I strongly urge those who have other objectives for their institutional archives to pursue them separately. The point is that these other agendas should not be allowed to get in the way of the essentials (for the open access movement), which consists of the "surrogates for published papers" (as you aptly put it) and not other things. It is not that other things should not be archived! Nor even that they should not be archived in the same archive, if that is possible. But the constraints on the archiving of the other things should not be allowed to hamper the archiving of the essentials in any way. That includes capacity and preservation burdens. If the other things have those burdens, they should be carried separately not imposed needlessly on the essentials. > Re preservation: I also disagree with your claim that having a > library mention preservation is likely to dissuade faculty from > contributing their work. Quite the contrary, a committment to a > reasonable degree of preservation is one way to sell the service, > and in fact is a piece that we've found to be fairly appealing > to faculty, even if it does have institutional costs that need to > be considered. Anything that actually generates the self-archiving of the essentials -- reminder: refereed articles! -- is welcome. But the fact is that there is not yet faintly enough self-archiving of refereed articles. So if the preservation promises have served as an inducement, they haven't yet helped much! http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving_files/Slide0024.gif http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving_files/Slide0043.gif Far, far more likely is that preservation promises have simply compounded the still prevalent misunderstanding about what is to be self-archived, how, and why. The author of an article in Nature, for example, has no worries about preservation. If you want to induce him to self-archive, you have to demonstrate to him the advantages -- in terms of research impact -- of providing open access to his Nature article. You will not induce him to self-archive by telling him that if he does, you promise to provide long-term preservation for that surrogate of the article! He is not concerned about long-term preservation. (Why should he be any more concerned about the long-term preservation of his Nature articles today than 10, 20, or 30 years ago?) But I am always open to new inducements for open-access provision. If -- mirabile dictu -- preservation promises start to serve as the successful inducement (instead of the red herring they have been till now), I will immediately stop preaching impact and start preaching preservation! (But I would only keep preaching at all because in reality open-access *is* for the sake of impact, even if, for some reason, preservation should prove to be the only language researchers understand.) I profoundly doubt, however, that the promise of preservation will do the trick. It's more likely to distract from the real goal, as it has done so often in the past: http://www.eprints.org/self-faq/#1.Preservation > Similarly, we find that there is demand for a convenient way to make > supplmentary materials available to colleagues. Many journals these > days realize there is demand for this and are offering this service > themselves (so it's ALREADY part of the publication process), but > not all. Again, offering support for the deposit of these materials > is something a library can do to make it MORE likely that faculty > will contribute the paper itself to an institutional repository, > and hence provide the open access we both agree is important. I agree that if an author troubles to self-archive the supplementary materials for his article, he is more likely to self-archive the article too. But (1) the vast majority of the yearly 2,500,000 articles do not have any supplementary materials and (2) chances are that for the minority of articles that do have supplementary materials that the author wants to self-archive (*and* the journal cannot archive them) the authors are already self-archiving their articles too. So I don't think this tail can or should wag the dog. >JQJ> The key issue here may be: > >JQJ> [aside: we believe that if we DON'T collect such unprintable >JQJ> items we'll never get faculty buy-in for Stevan's laudable >JQJ> goal of collecting the printable peer-reviewed works] > >SH> But *why* do you feel that? > > We need more data, but anecdotally, our experience has been that > those faculty who are hot to self-archive their preprints are > already doing so, and that arXiv and RePEc are meeting most of the > demand. That's probably true, though it leaves out an anarchic multi-disciplinary body of articles self-archived by authors on their own websites (as discovered by harvesters such as citeseer in computer science, already twice as big as the Physics ArXiv several years ago). http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving_files/Slide0038.gif But I agree that it is those who are *not* yet self-archiving (i.e., nearly 90%) who are the targets. I just doubt that the lure of either preservation or data-archiving is going to draw that 90% on board! (Whereas I do think that powerful objective demonstrations of the impact-enhancing power of open-access provision will: for the researchers, and, even more important, for their institutions and funders, who wield the publish-or-perish carrot and stick that already protects researchers from any natural tendency to just put their papers into a desk-drawer rather than maximizing their impact by publishing them: http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving.htm .) > There are very few examples of institutional repositories > that are proving successful in collecting the types of items you > insist on focusing on. That is true. But there are some. And more than there used to be recently. And we are still working on formulating that offer that researchers won't be able to refuse! http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving_files/Slide0006.gif http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving_files/Slide0025.gif "Measuring cumulating research impact loss across fields and time" http://www.ecs.soton.ac.uk/~harnad/Hypermail/Amsci/3212.html > Even MIT's DSpace is getting very little > true faculty self-archiving, with most of its growth seeming to > come from departmental grey literature (and soon from OCI course > materials). I can only re-echo the sentiments of: "EPrints, DSpace or ESpace?" http://www.ecs.soton.ac.uk/~harnad/Hypermail/Amsci/2670.html http://www.ecs.soton.ac.uk/~harnad/Hypermail/Amsci/2837.html The reason institutional archives are not getting filled is because they are heading off in all directions: 1. (MAN) digital collection management (all kinds of digital content) 2. (PRES) digital preservation (all kinds of digital content) 3. (TEACH) online teaching materials 4. (EPUB) electronic publication (journals and books) 5. (RES) self-archiving institutional research output (preprints, postprints and theses) Instead of focussing on 5 (RES). http://www.ecs.soton.ac.uk/~harnad/Hypermail/Amsci/3210.html > Meanwhile, though, many faculty express the desire > to have better tools for managing large data sets as part of the > publication process. Meanwhile, while the archives are *not* filling, and open access is *not* being provided, and cumulating research impact loss continues to grow, there are many other desires being expressed (and perhaps even being fulfilled). But they have nothing to do with open access (to the refereed journal literature)! And those sectors of the archives continue to yawn empty. > We had a dean's retreat last month, and our > deanlet for the social sciences made the point that her new hires > in the social sciences are starting to imitate their physical > science colleagues and demand more startup money; when asked what > they say they need the money for, she reported that it is mostly > for management and archival of their data sets. Well, that is certainly interesting, and good news for data-archiving in the social sciences. But what further conclusion is to be drawn from it? > Similarly, there > is pressure in the U.S. from the granting agencies to make the > data that accompanies a submitted paper publicly accessible. That pressure is very welcome, but it seems absurd for the granting agencies to pressure for archiving the data without also pressuring for archiving the data! (And are you sure this is all for *open-access* data-archiving, rather than merely data-archiving?) http://www.ariadne.ac.uk/issue35/harnad > And I frequently hear from faculty that they want to increase the > impact of their work by making available supplmentary materials > that go along with the peer reviewed paper -- data sets, survey > instruments, supplementary statistical analyses, maps and images, > etc. There's real unmet demand here. A useful thing to say to faculty who have expressed the desire to increase the impact of their peer-reviewed papers by providing open access to supplementary materials is: Wouldn't it be a good idea to increase the impact of your peer-reviewed papers by providing open access to your peer-reviewed papers? But I am not disagreeing that data-archiving is a splendid idea and will help hasten article-archiving too! http://www.ecs.soton.ac.uk/~harnad/Temp/data-archiving.htm I'm just suggesting that we shouldn't focus on trying to make the tail wag the dog. > I think you make a very good point that it is a large problem that > institutional archiving efforts keep running off in all directions. > However, although I think there is definitely room for institutional > strategies that are monomaniacal in their focus, there's also room > for strategies that take a very different direction. For instance, > consider MIT's DSpace, or Ohio State's KnowledgeBank. The important > thing is that any given institution be clear in its goals, and that > we recognize that the precise statement of those goals will imply > particular implementation strategies and hardware/technology/budget > requirements (the question that Min-Yen Kan originally raised). There are many digital things institutions can and should archive. One particularly important thing is their refereed research output. The self-archiving of that particularly important thing is going particularly slowly (relative to its importance), mainly (I believe) because the research community has not yet grasped what a strong direct causal connection there is between research access and research impact. Their grasp of that connection will not be hastened by mixing it up with the archiving of all kinds of other digital things -- and especially if the archiving of those other digital things has further constraints and liabilities (such as preservation, large-scale data-archiving, and multimedia) that spill over onto the archiving of refereed research output, which does not have those further constraints and liabilities, and needs more momentum rather than dead weight. Stevan Harnad From harnad@ecs.soton.ac.uk Mon Dec 8 06:37:14 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hB8BbDqb002139 for ; Mon, 8 Dec 2003 06:37:14 -0500 (EST) Received: from raven.ecs.soton.ac.uk (raven.ecs.soton.ac.uk [152.78.70.1]) hB8BbCXE026285 for ; Mon, 8 Dec 2003 06:37:13 -0500 (EST) Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1]) by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id LAA14324; Mon, 8 Dec 2003 11:37:11 GMT Received: from pandora (pandora [152.78.68.157]) by pigeon.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id LAA24657; Mon, 8 Dec 2003 11:36:58 GMT Newsgroups: bionet.journals.note Date: Mon, 8 Dec 2003 11:36:56 +0000 (GMT) From: Stevan Harnad X-Sender: harnad@pandora To: SPARC Open Access Forum Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information X-ECS-MailScanner: Found to be clean X-Mailman-Approved-At: Tue, 09 Dec 2003 10:06:12 -0500 Subject: [Dspace-general] Estimates on data and cost per department for institutionalarchives? (fwd) X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 08 Dec 2003 11:37:14 -0000 ---------- Forwarded message ---------- Date: Sun, 7 Dec 2003 23:10:10 -0500 From: Min-Yen Kan To: SEPTEMBER98-FORUM@LISTSERVER.SIGMAXI.ORG Subject: Estimates on data and cost per department for institutional archives? Hello all: At the National University of Singapore, a task force has assembled to examine the possibility of setting up an open-access institutional repository to address some of the goals brought up by Stevan Harnad, but most importantly: > 5. (RES) self-archiving institutional research output (preprints, > postprints and theses) > > "Re: Central versus institutional self-archiving" > http://www.ecs.soton.ac.uk/~harnad/Hypermail/Amsci/3210.html > > "Re: EPrints, DSpace or ESpace?" > http://www.ecs.soton.ac.uk/~harnad/Hypermail/Amsci/2837.html The reason why I'm writing the list is because we are currently trying to estimate the amount of data that will eventually flow into the institutional archive. It's hoped that it will give us a way to estimate the cost of the budget for the project. Many of the parameters in the project are under discussion, so I can't give many informative details, but I'm interested in finding out whether any studies tabulating the size (and/or cost) of data going into institutional repositories have been done. I know this query is a bit underspecified, but I'm hoping that any leads that readers of this list might be able to offer will be able to help our group come up with an approximate figure. We feel it is good to consult expertise earlier rather than later. Of course, there are numerous other issues that need to be examined (e.g., copyright policy), and our group is checking these out in parallel. I've done some searching on the list archives, D-Ligband Ariadne, and as of now, I'm only aware of Theo Andrew's recent Ariadne article on repository postings at the Univ. of Edinburgh (http://www.ariadne.ac.uk/issue37/andrew/) and Michael Day's article on ePrints UK (http://www.rdn.ac.uk/projects/eprints-uk/docs/studies/impact/). I would be very happy to hear from you if you have any past or present lessons to share. I would be happy to post a summary of responses if there's interest. Regards, Min-Yen KAN Assistant Professor Department of Computer Science, School of Computing National University of Singapore, Singapore 117543 http://www.comp.nus.edu.sg/~kanmy From harnad@ecs.soton.ac.uk Mon Dec 8 07:05:19 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hB8C5Jqb002531 for ; Mon, 8 Dec 2003 07:05:19 -0500 (EST) Received: from raven.ecs.soton.ac.uk (raven.ecs.soton.ac.uk [152.78.70.1]) hB8C5IXE006242 for ; Mon, 8 Dec 2003 07:05:18 -0500 (EST) Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1]) by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id MAA15942; Mon, 8 Dec 2003 12:05:13 GMT Received: from pandora (pandora [152.78.68.157]) by pigeon.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id MAA28507; Mon, 8 Dec 2003 12:05:08 GMT Newsgroups: bionet.journals.note Date: Mon, 8 Dec 2003 12:05:06 +0000 (GMT) From: Stevan Harnad X-Sender: harnad@pandora To: American Scientist Open Access Forum In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information X-ECS-MailScanner: Found to be clean X-Mailman-Approved-At: Tue, 09 Dec 2003 10:06:12 -0500 Subject: [Dspace-general] Re: Estimates on data and cost per department for institutional archives? X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 08 Dec 2003 12:05:20 -0000 On Mon, 8 Dec 2003, Min-Yen Kan wrote: > At the National University of Singapore, a task force has assembled > to examine the possibility of setting up an open-access institutional > repository [for] > > 5. (RES) self-archiving institutional research output (preprints, > > postprints and theses) > > http://www.ecs.soton.ac.uk/~harnad/Hypermail/Amsci/3210.html > > http://www.ecs.soton.ac.uk/~harnad/Hypermail/Amsci/2837.html > > we are currently trying to estimate the amount of data that will > eventually flow into the institutional archive. It's hoped that it will > give us a way to estimate the cost of the budget for the project. I leave it to the administrators of the existing institutional archives for RES (e.g., the larger ones among the 113 in http://software.eprints.org/archives.php or the 243 in http://oaister.umdl.umich.edu/o/oaister/ ) to reply about costs. I just wish to point out one crucial omission in the question: Cost is very low, and the cost per-paper will obviously be lower the more papers are archived. But how many papers are archived in turn depends on something completely different from the question of archive cost, namely, whether or not the institution has a successful and effective policy for ensuring that the RES archive is filled! http://www.ecs.soton.ac.uk/~harnad/Temp/archpolnew.html http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving_files/Slide0022.gif There are many institutional archives intended for RES that are sitting out there still near-empty for lack of an institutional archive-filling policy. There is not much to be learned from finding out what that costs to do! If I were planning to set up institutional archives for RES I would devote far more effort to finding out how to fill them (and then to filling them). If nothing else, that would give a far better idea of the per-paper cost to expect. The cost-data from some of the larger existing archives will help estimate this figure. Reckon into it also the cost per-paper of implementing an effective institutional archive-filling policy! http://eprints.st-andrews.ac.uk/proxy_archive.html Stevan Harnad NOTE: A complete archive of the ongoing discussion of providing open access to the peer-reviewed research literature online is available at the American Scientist Open Access Forum (98 & 99 & 00 & 01 & 02 & 03): http://amsci-forum.amsci.org/archives/september98-forum.html http://www.cogsci.soton.ac.uk/~harnad/Hypermail/Amsci/index.html Post discussion to: september98-forum@amsci-forum.amsci.org Dual Open-Access-Provision Policy: BOAI-2 ("gold"): Publish your article in a suitable open-access journal whenever one exists. BOAI-1 ("green"): Otherwise, publish your article in a suitable toll-access journal and also self-archive it. http://www.soros.org/openaccess/read.shtml http://www.ecs.soton.ac.uk/~harnad/Temp/berlin.htm http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving_files/Slide0026.gif http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving_files/Slide0021.gif http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving_files/Slide0024.gif http://www.ecs.soton.ac.uk/~harnad/Temp/self-archiving_files/Slide0028.gif From r.d.jones@ed.ac.uk Thu Dec 11 12:01:42 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hBBH1fqb007927 for ; Thu, 11 Dec 2003 12:01:41 -0500 (EST) Received: from lawnmarket.ucs.ed.ac.uk (lawnmarket.ucs.ed.ac.uk [129.215.166.63])hBBH1ea7013820 for ; Thu, 11 Dec 2003 12:01:40 -0500 (EST) Received: from LIBPC1118 (library-mg-01.net.ed.ac.uk [129.215.146.81]) hBBH1bft017670; Thu, 11 Dec 2003 17:01:37 GMT Message-ID: <004e01c3c008$2afe8320$5192d781@lib.ed.ac.uk> From: "Richard Jones" To: , Date: Thu, 11 Dec 2003 16:59:40 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [Dspace-general] EUL-DSpace Add-On v0.2 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list Reply-To: Richard Jones List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Thu, 11 Dec 2003 17:01:42 -0000 Hi All, Quick Xmas prezzie for anyone that wants it: EUL-DSpace v0.2 is now available for download from http://www.thesesalive.ac.uk/dsp_download.shtml. I am now away on holiday for the whole of the xmas period but will be available to answer questions as of the beginning of next year. Have a good holiday everyone. Cheers Richard ============================== Richard Jones Systems Developer Theses Alive! - www.thesesalive.ac.uk Edinburgh University Library r.d.jones@ed.ac.uk 0131 651 1611 From sbell@library.rochester.edu Mon Dec 15 10:40:23 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hBFFeMqb015183 for ; Mon, 15 Dec 2003 10:40:22 -0500 (EST) Received: from library.rochester.edu (mail.lib.rochester.edu [128.151.244.122])hBFFeMpF016047 for ; Mon, 15 Dec 2003 10:40:22 -0500 (EST) Received: from RCL-MTA by library.rochester.edu with Novell_GroupWise; Mon, 15 Dec 2003 10:46:13 -0500 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.3 Date: Mon, 15 Dec 2003 10:45:27 -0500 From: "Suzanne Bell" To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: [Dspace-general] Experiences with policy making, quotas? X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 15 Dec 2003 15:40:23 -0000 Hello folks - A couple questions for those with more material up and more experience generally: - has anyone been in on their departments/communities' establishment of policies for DSpace? e.g., what have depts at other places done - given everyone rights to deposit, and trust they will "self-filter"? given everyone rights, but then used the workflow capability to have someone check all the deposits? what kind of "someone" - a faculty person? a dept. administrator? - have any of you established storage quotas for your communities? can you say anything about that - how much, how you decided? Thanks for any experiences you want to share! cheers from the snowy northeast... :) -Suzanne ******************************************* Suzanne Bell, Economics/Data Librarian DSpace Projects Coordinator University of Rochester 585/275-9317 sbell@library.rochester.edu From mcneillh@MIT.EDU Mon Dec 15 11:14:38 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hBFGEbqb015723 for ; Mon, 15 Dec 2003 11:14:37 -0500 (EST) Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72])hBFGEbpF006913; Mon, 15 Dec 2003 11:14:37 -0500 (EST) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])hBFGDlH7007795; Mon, 15 Dec 2003 11:14:36 -0500 (EST) Received: from dewey-12.mit.edu (DEWEY-12.MIT.EDU [18.171.0.103]) ) hBFGBBRk027233; Mon, 15 Dec 2003 11:11:11 -0500 (EST) Message-Id: <5.2.1.1.2.20031215105753.02003338@po11.mit.edu> X-Sender: mcneillh@po11.mit.edu (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 15 Dec 2003 11:10:33 -0500 To: "Suzanne Bell" , From: Katherine McNeill-Harman Subject: Re: [Dspace-general] Experiences with policy making, quotas? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 15 Dec 2003 16:14:38 -0000 Suzanne, Hi there and good to hear from you Others from MIT can weigh in with more details, but here's a starting answer for us. Regarding the first question, we've worked with our communities to set their own policies in these areas, so that they can determine a workflow that works best in their department. From my understanding, communities therefore have set up a variety of arrangements, giving different levels of permission for submission and involving different kinds of personnel. This flexibility is illustrated in our community start-up procedures http://libraries.mit.edu/dspace-mit/mit/policies/startup.html. Regarding storage quotas, we do have some, based on the size of the community, but I'm not sure where they're written. Communities might have the option to pay a fee for more storage space, however. Good luck, Kate McNeill-Harman At 10:45 AM 12/15/2003 -0500, Suzanne Bell wrote: >Hello folks - > > A couple questions for those with more material up and more experience >generally: > > - has anyone been in on their departments/communities' establishment >of policies for DSpace? e.g., what have depts at other places done - >given everyone rights to deposit, and trust they will "self-filter"? >given everyone rights, but then used the workflow capability to have >someone check all the deposits? what kind of "someone" - a faculty >person? a dept. administrator? > > - have any of you established storage quotas for your communities? can >you say anything about that - how much, how you decided? > > Thanks for any experiences you want to share! > > cheers from the snowy northeast... :) > > -Suzanne > >******************************************* >Suzanne Bell, Economics/Data Librarian >DSpace Projects Coordinator >University of Rochester >585/275-9317 >sbell@library.rochester.edu >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general ___________________________________________ Katherine McNeill-Harman Data Services Reference Librarian Dewey Library for Management and Social Sciences Massachusetts Institute of Technology 77 Massachusetts Avenue, E53-100 Cambridge, MA 02139 mcneillh@mit.edu 617-253-0787 From gabriela.mircea@utoronto.ca Mon Dec 15 15:03:20 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hBFK3Kqb020289 for ; Mon, 15 Dec 2003 15:03:20 -0500 (EST) Received: from bureau8.utcc.utoronto.ca (bureau8.utcc.utoronto.ca [128.100.132.18])hBFK3JZ1028784 for ; Mon, 15 Dec 2003 15:03:19 -0500 (EST) Received: from utl-194-187.library.utoronto.ca ([142.150.194.187] EHLO utoronto.ca ident: IDENT-NOT-QUERIED [port 1181]) by bureau8.utcc.utoronto.ca with ESMTP id <24943-18500>; Mon, 15 Dec 2003 15:03:12 -0500 Message-ID: <3FDE137A.1030001@utoronto.ca> Date: Mon, 15 Dec 2003 15:03:06 -0500 From: Gabriela Mircea User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.01 MIME-Version: 1.0 To: Suzanne Bell , dspace-general@mit.edu Subject: Re: [Dspace-general] Experiences with policy making, quotas? References: Content-Type: multipart/alternative; boundary="------------010905050006090406040903" X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 15 Dec 2003 20:03:21 -0000 --------------010905050006090406040903 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hello Suzanne, Below is what we have posted on our website in regards to storage space, but it doesn't apply to early adopters. For early adopters we have a special treatment, since space is not an issue yet, we give them unlimited storage space until we officially launch our service. "Storage Space: The quotas listed below are proposed levels that will be reviewed and set prior to the full T-Space release. Thereafter, the quotas for new input will be reviewed on an annual basis at which time UofT Libraries reserve the right to alter the quotas as dictated by demand and resource availability. Communities with greater storage needs will be dealt with on a case by case basis. Annual Quotas for New Input (Guideline only) Community Size Small Medium Large Number of items per year 300 600 1000 Number of submitters < 50 51 - 149 150 Average file size 1 MB 1 MB 1 MB Annual storage limit approx. 3 GB 6 GB 10 GB " About policies .. We let the users decide the policies. We just explain them their choices, and they decide. Most of our communities do not use the workflow, and each community has just a few people allowed to submit. I hope this helps. Gabriela Suzanne Bell wrote: >Hello folks - > > A couple questions for those with more material up and more experience >generally: > > - has anyone been in on their departments/communities' establishment >of policies for DSpace? e.g., what have depts at other places done - >given everyone rights to deposit, and trust they will "self-filter"? >given everyone rights, but then used the workflow capability to have >someone check all the deposits? what kind of "someone" - a faculty >person? a dept. administrator? > > - have any of you established storage quotas for your communities? can >you say anything about that - how much, how you decided? > > Thanks for any experiences you want to share! > > cheers from the snowy northeast... :) > > -Suzanne > >******************************************* >Suzanne Bell, Economics/Data Librarian >DSpace Projects Coordinator >University of Rochester >585/275-9317 >sbell@library.rochester.edu >_______________________________________________ >Dspace-general mailing list >Dspace-general@mit.edu >http://mailman.mit.edu/mailman/listinfo/dspace-general > > -- Gabriela Mircea Information Technology Services Robarts Library, 130 St. George St. Toronto, ON, Canada, M5S 1A5 416 946 0114 --------------010905050006090406040903 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Suzanne,


Below is what we have posted on our website in regards to storage space, but it doesn't apply to early adopters. For early adopters we have a special treatment, since space is not an issue yet, we give them unlimited storage space until we officially  launch  our service.

"Storage Space:
The quotas listed below are proposed levels that will be reviewed and set prior to the full T-Space release. Thereafter, the quotas for new input will be reviewed on an annual basis at which time UofT Libraries reserve the right to alter the quotas as dictated by demand and resource availability. Communities with greater storage needs will be dealt with on a case by case basis.
Annual Quotas for New Input (Guideline only)
Community Size
Small
Medium
Large
Number of items per year 300 600 1000
Number of submitters < 50 51 - 149 150
Average file size 1 MB 1 MB 1 MB
Annual storage limit approx. 3 GB 6 GB 10 GB
"


About policies .. We let the users decide the policies. We just explain them their choices, and they decide. Most of our communities do not use the workflow, and each community has just a few people allowed to submit.

I hope this helps.

Gabriela

Suzanne Bell wrote:
Hello folks -

 A couple questions for those with more material up and more experience
generally:

 - has anyone been in on their departments/communities' establishment
of policies for DSpace? e.g., what have depts at other places done -
given everyone rights to deposit, and trust they will "self-filter"?
given everyone rights, but then used the workflow capability to have
someone check all the deposits? what kind of "someone" - a faculty
person? a dept. administrator?

 - have any of you established storage quotas for your communities? can
you say anything about that - how much, how you decided?

 Thanks for any experiences you want to share!

 cheers from the snowy northeast... :)

 -Suzanne

*******************************************
Suzanne Bell, Economics/Data Librarian
DSpace Projects Coordinator
University of Rochester
585/275-9317
sbell@library.rochester.edu
_______________________________________________
Dspace-general mailing list
Dspace-general@mit.edu
http://mailman.mit.edu/mailman/listinfo/dspace-general
  

-- 
Gabriela Mircea
Information Technology Services
Robarts Library, 130 St. George St.
Toronto, ON, Canada, M5S 1A5
416 946 0114

--------------010905050006090406040903-- From rrodgers@MIT.EDU Tue Dec 23 16:18:33 2003 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hBNLIXqb012086 for ; Tue, 23 Dec 2003 16:18:33 -0500 (EST) Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82])hBNLIWN9026329 for ; Tue, 23 Dec 2003 16:18:32 -0500 (EST) Received: from manawatu-mail-centre.mit.edu (MANAWATU-MAIL-CENTRE.MIT.EDU [18.7.7.71])hBNLIVHA027509 for ; Tue, 23 Dec 2003 16:18:32 -0500 (EST) Received: from dspace-03.mit.edu (DSPACE-03.MIT.EDU [18.51.2.148]) ) hBNLIVQ7016614 for ; Tue, 23 Dec 2003 16:18:31 -0500 (EST) Received: (from rrodgers@localhost) by dspace-03.mit.edu (8.12.9) id hBNLIVU4025969; Tue, 23 Dec 2003 16:18:31 -0500 From: Richard Rodgers To: dspace-general@MIT.EDU Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1072214310.18829.20.camel@dspace-03.mit.edu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Tue, 23 Dec 2003 16:18:31 -0500 Subject: [Dspace-general] DSpace 1.2 Release Schedule X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 23 Dec 2003 21:18:34 -0000 A Word on DSpace 1.2 I wanted to bring the community up to date on the 1.2 release schedule. Although work on feature definition and implementation is proceeding, the target date has receded from our optimistic early projections of the end of this year. We want this release to be worth the wait, and also understand the increased importance of thorough testing, since a larger group of adopters is depending upon a smooth upgrade experience. With these issues in mind, we are looking at an early March 2004 'preview' release, to be demonstrated at the DSpace user group meeting, which will then be subjected to intensive evaluation and testing. DSpace adopter community participation in this process will be vital, and can assume several forms. First, we will set up a server at MIT with 1.2 code and solicit testers to exercise it. This was done for the 1.1.1 release, but we hope both to expand the number of participants and improve its effectiveness by documenting the changes more fully. Second, we would like volunteers to test the installation process, to catch unforeseen dependencies. I strongly recommend installers use a separate server on which to perform the test upgrade, but one that shares the characteristics of their production server(s) (such as customized UI, etc). Third, we will also try to make documentation (including install docs) available in preview, to expose any deficiencies before they are officially published. If you are willing to act in any of these capacities, let me know after the new year, and as the release nears completion, we will contact you with further details. Have a happy holiday season, Richard Rodgers DSpace Federation Systems Manager From jonesa01@newschool.edu Wed Dec 24 16:07:41 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hBOL7fqb027843; Wed, 24 Dec 2003 16:07:41 -0500 (EST) Received: from igate.newschool.edu (igate.newschool.edu [149.31.5.20]) hBOL7SOX014713; Wed, 24 Dec 2003 16:07:28 -0500 (EST) Received: from NGWGATE-MTA by igate.newschool.edu with Novell_GroupWise; Wed, 24 Dec 2003 16:07:28 -0500 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.5 Beta Date: Wed, 24 Dec 2003 16:07:25 -0500 From: "Allen Jones" To: , Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=_BDE36500.91F09649" Subject: [Dspace-general] Re: Dspace-general Digest, Vol 5, Issue 9 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 24 Dec 2003 21:07:42 -0000 This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=_BDE36500.91F09649 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I would be happy to run a test server of 1.2 code as it becomes available. Allen Jones Director Center for Education and Technology University Library/New School University 55 W.13th Street, New York, NY 10011 (voice)212.229.5188 (fax)212.647.8202 >>> dspace-general-request@mit.edu 12/24/03 12:02PM >>> Send Dspace-general mailing list submissions to dspace-general@mit.edu=20 To subscribe or unsubscribe via the World Wide Web, visit http://mailman.mit.edu/mailman/listinfo/dspace-general=20 or, via email, send a message with subject or body 'help' to dspace-general-request@mit.edu=20 You can reach the person managing the list at dspace-general-owner@mit.edu=20 When replying, please edit your Subject line so it is more specific than "Re: Contents of Dspace-general digest..." Today's Topics: 1. DSpace 1.2 Release Schedule (Richard Rodgers) ---------------------------------------------------------------------- Date: Tue, 23 Dec 2003 16:18:31 -0500 From: Richard Rodgers To: dspace-general@MIT.EDU=20 Subject: [Dspace-general] DSpace 1.2 Release Schedule Message-ID: <1072214310.18829.20.camel@dspace-03.mit.edu> Content-Type: text/plain MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: list Message: 1 A Word on DSpace 1.2 I wanted to bring the community up to date on the 1.2 release schedule. Although work on feature definition and implementation is proceeding, the target date has receded from our optimistic early projections of the end of this year. We want this release to be worth the wait, and also understand the increased importance of thorough testing, since a larger group of adopters is depending upon a smooth upgrade experience. With these issues in mind, we are looking at an early March 2004 'preview' release, to be demonstrated at the DSpace user group meeting, which will then be subjected to intensive evaluation and testing. DSpace adopter community participation in this process will be vital, and can assume several forms. First, we will set up a server at MIT with 1.2 code and solicit testers to exercise it. This was done for the 1.1.1 release, but we hope both to expand the number of participants and improve its effectiveness by documenting the changes more fully. Second, we would like volunteers to test the installation process, to catch unforeseen dependencies. I strongly recommend installers use a separate server on which to perform the test upgrade, but one that shares the characteristics of their production server(s) (such as customized UI, etc). Third, we will also try to make documentation (including install docs) available in preview, to expose any deficiencies before they are officially published. If you are willing to act in any of these capacities, let me know after the new year, and as the release nears completion, we will contact you with further details. Have a happy holiday season, Richard Rodgers DSpace Federation Systems Manager =20 ------------------------------ _______________________________________________ Dspace-general mailing list Dspace-general@mit.edu=20 http://mailman.mit.edu/mailman/listinfo/dspace-general=20 End of Dspace-general Digest, Vol 5, Issue 9 ******************************************** --=_BDE36500.91F09649 Content-Type: text/plain; name="Allen Jones.vcf" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="Allen Jones.vcf" BEGIN:VCARD VERSION:2.1 X-GWTYPE:USER FN:internet:jonesa01@newschool.edu TEL;WORK:5667 X-367 ORG:;Center for Education and Technology TEL;PREF;FAX: EMAIL;WORK;PREF:JonesA01@newschool.edu N:Jones;Allen TITLE:Director END:VCARD BEGIN:VCARD VERSION:2.1 X-GWTYPE:USER FN:internet:jonesa01@newschool.edu TEL;WORK:5667 X-367 ORG:;Center for Education and Technology TEL;PREF;FAX: EMAIL;WORK;PREF:JonesA01@newschool.edu N:Jones;Allen TITLE:Director END:VCARD BEGIN:VCARD VERSION:2.1 X-GWTYPE:USER FN:Jones, Allen TEL;WORK:5667 X-367 ORG:;Center for Education and Technology TEL;PREF;FAX: EMAIL;WORK;PREF;NGW:JonesA01@newschool.edu N:Jones;Allen TITLE:Director END:VCARD --=_BDE36500.91F09649-- From vsaxena@MIT.EDU Fri Dec 26 17:28:28 2003 Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hBQMSSqb008548 for ; Fri, 26 Dec 2003 17:28:28 -0500 (EST) Received: from websnail.mit.edu (WEBSNAIL.MIT.EDU [18.7.22.71]) hBQMSSu3007494 for ; Fri, 26 Dec 2003 17:28:28 -0500 (EST) Received: (from www@localhost) by websnail.mit.edu (8.9.3) id RAA15050; Fri, 26 Dec 2003 17:28:28 -0500 (EST) From: vsaxena@MIT.EDU Received: from 18.202.0.157 ( [18.202.0.157]) as user vsaxena@MIT.EDU by webmail.mit.edu with HTTPS; Fri, 26 Dec 2003 17:28:28 -0500 Message-ID: <1072477708.3fecb60c6b50e@webmail.mit.edu> Date: Fri, 26 Dec 2003 17:28:28 -0500 To: dspace-general@MIT.EDU MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1-cvs X-Originating-IP: 18.202.0.157 X-Originating-Host: X-MIT-WebMail-Sender: X-MIT-WebMail-User-Browser: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322) Subject: [Dspace-general] Problem with DSpace | while using ant fresh_install | Linux Env | MIT Student X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Fri, 26 Dec 2003 22:28:29 -0000 Hi, I am a MIT Graduate Student, working on J2EE application (dSpace) in linux environment. I am trying to solve this problem since last 4 weeks. I have arrived at the conclusion that there is some problem with gcc or may be with gij in the context of its compatability with linux. I am compliling dspace (a J2EE based MIT owned product) using ant at Linux system. I am getting following errors................ -------------------------------------------------------------------- [dspace@sloandb dspace]$ ant fresh_install Buildfile: build.xml update: [jar] Building jar: /home/dspace/lib/dspace.jar install_code: setup_database: [java] gij: unrecognized option -- `-classpath' [java] Try `gij --help' for more information. BUILD FAILED file:/home/dspace/dspace/build.xml:220: Java returned: 1 Total time: 2 seconds -------------------------------------------------------------------- I will appreciate if you can suggest me some wokaround, may be some patch or can let me know what should be a better way for me to approach. Thanks and Regards ~Vishal Saxena VISHAL SAXENA -Student, M.I.T. Cambridge -Graduate Research Assistant, Sloan Business School, MIT -CELL:1-617-308-1003 "In a race, it does not matter where you are, what matters is how much distance you have covered" From tsf@cogeco.ca Sat Dec 27 11:47:48 2003 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hBRGlmqb005335 for ; Sat, 27 Dec 2003 11:47:48 -0500 (EST) Received: from fep4.cogeco.net (smtp.cogeco.net [216.221.81.25]) hBRGllYU028863 for ; Sat, 27 Dec 2003 11:47:47 -0500 (EST) Received: from customer (unknown [24.235.152.216]) by fep4.cogeco.net (Postfix) with SMTP id 16429C68 for ; Sat, 27 Dec 2003 11:47:47 -0500 (EST) Message-ID: <000901c3cc99$720ca600$d898eb18@pego2.on.cogeco.ca> From: "M. Dale Rodger" To: Date: Sat, 27 Dec 2003 11:48:32 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Subject: [Dspace-general] unsuscribe X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Sat, 27 Dec 2003 16:47:48 -0000 please unsubscribe From kenzie@MIT.EDU Tue Dec 30 18:32:06 2003 Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id hBUNW5qb027801 for ; Tue, 30 Dec 2003 18:32:05 -0500 (EST) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])hBUNVmHx016201; Tue, 30 Dec 2003 18:31:48 -0500 (EST) Received: from ADTPA.mit.edu (macknz.ne.client2.attbi.com [24.61.43.45]) (authenticated bits=0) (User authenticated as kenzie@ATHENA.MIT.EDU)hBUNVkRw001326 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT); Tue, 30 Dec 2003 18:31:47 -0500 (EST) Message-Id: <5.2.1.1.2.20031230175751.01c6afb8@hesiod> X-Sender: kenzie@hesiod X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Tue, 30 Dec 2003 18:27:48 -0500 To: dspace-tech@lists.sourceforge.net From: MacKenzie Smith In-Reply-To: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_24621023==_" cc: dspace-general@MIT.EDU Subject: [Dspace-general] [Dspace-tech] License agreement for each item X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 30 Dec 2003 23:32:06 -0000 --=====================_24621023==_ Content-Type: text/plain; charset="us-ascii"; format=flowed Hi Mao, MIT is about to implement something like this for our own use. We will split the current submission license into two parts: a "DSpace license" that governs what we (the Libraries managing DSpace) can do with the item as its steward, and a separate "use license" to govern what the author/submitter wants to allow the public (or whoever can access the item) to do with it. For the former we'll use a fixed license that looks pretty much like the one in DSpace now, and for the latter we'll offer some of the Creative Commons licenses. I've attached a draft of what our UI screen might look like, and we're hoping to do the necessary programming in the next two months. If this is something of general interest we'd be happy to think about adding it to the open source system later on... just let us know. And on a related note, a Creative Commons representative will be coming to the DSpace user group meeting on March 10-11 to answer questions about their status and plans for the coming year -- for example, I know they've been tweaking their base license to address institutional concerns about liability and so on. Should be interesting! As for enforcement by DSpace -- the system administrator can set access control for items as necessary (at the bitstream, item, or collection level) and these are enforced using whatever authentication/authorization method you've implemented (logon/password, digital certificates, LDAP, etc.). But *use* licenses -- those that govern what a particular user is allowed to do with an item once they have it -- aren't really enforceable without implementing nasty encryption techniques which get in the way of fair use. At MIT we've decided to rely on copyright law and licenses like the Creative Commons for use of our material, and to let the courts enforce them if that ever proves necessary. I hope this answers your question! MacKenzie >Date: Thu, 18 Dec 2003 16:00:48 -0500 >From: mao ni >To: DSpace >Subject: [Dspace-tech] License agreement for each item > >Dear All, > >Happy Holidays! > >Our E-thesis collection wants to apply flexible rights administration for >each item, that is, every submitter could choose one from a set of license >agreements like Creative Commons. For example, an author might limit his >item to non-commercial use only. >In this case, it is convenient for authors to pick up the license they >want instead of the same license agreement for the whole collection. >I have done this by storing the DC copyrights metadata with each item. >My question is that if DSpace has implemented the rights limitation or not >when the bitstream of the item is going to be viewed? For example, if the >license of the item is not allowed to be viewed yet, will DSpace disallow >the bitstream to be accessed? > >Thanks, > >Mao > >School of Information and Library Science >University of North Carolina at Chapel Hill >Email: maoni@ils.unc.edu >Tel: (919) 962 - 0184 MacKenzie Smith Associate Director for Technology MIT Libraries Building 14S-208 77 Massachusetts Avenue Cambridge, MA 02139 (617)253-8184 kenzie@mit.edu --=====================_24621023==_ Content-Type: text/html; charset="us-ascii" Content-Disposition: attachment; filename="CCForm.htm" Untitled Document

DSpace Distribution License

If you own the copyright to this item, DSpace offers you several ways to protect your work as it is distributed to the world at large. All published work is automatically protected by copyright law in the United States (link to copyright law). However, if you would like to make your work more accessible, you may choose another option below to release some of the restrictions of the copyright law.

Modify Copyright Protection by using one or more of the following Creative Commons choices:

(more info - link to CC)

Allow Commercial Use? (more info - link to CC)
yes no

Allow (more info - link to CC)
 yes no

Allow others to distribute derivative works only under a license identical to the license that governs your work? no

Put my work in the Public Domain (more info - link to CC)

Retain Full Copyright Protection (more info - MIT info. & U.S. copyright law)

Other terms of distribution (more info- link to MIT counsel)

 



--=====================_24621023==_-- From maoni@email.unc.edu Fri Jan 2 14:39:10 2004 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id i02Jd9qb020564 for ; Fri, 2 Jan 2004 14:39:09 -0500 (EST) Received: from smtp.unc.edu (smtpsrv10.isis.unc.edu [152.2.1.241]) i02Jcxmi007057; Fri, 2 Jan 2004 14:38:59 -0500 (EST) Received: from scooby.ils.unc.edu (scooby.ils.unc.edu [152.2.81.24]) by smtp.unc.edu (8.12.9/8.12.9) with ESMTP id i02Jc96l001669; Fri, 2 Jan 2004 14:38:09 -0500 (EST) Date: Fri, 02 Jan 2004 14:38:10 -0500 From: mao ni To: MacKenzie Smith , dspace-tech@lists.sourceforge.net Message-ID: <1808156.1073054289@scooby.ils.unc.edu> In-Reply-To: <5.2.1.1.2.20031230175751.01c6afb8@hesiod> References: <5.2.1.1.2.20031230175751.01c6afb8@hesiod> X-Mailer: Mulberry/3.0.3 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mailman-Approved-At: Fri, 02 Jan 2004 16:21:25 -0500 cc: dspace-general@MIT.EDU Subject: [Dspace-general] Re: [Dspace-tech] License agreement for each item X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Fri, 02 Jan 2004 19:39:10 -0000 Thanks for your detailed reply, MacKenzie. It will be great if DSpace will implement the Creative Commons. We could customize the DSpace retrieving procedure if it doesn't have bitstream control based on license. Happy New Year! Mao --On Tuesday, December 30, 2003 6:27 PM -0500 MacKenzie Smith wrote: > Hi Mao, > > MIT is about to implement something like this for our own use. We will > split the current submission license into two parts: a "DSpace license" > that governs what we (the Libraries managing DSpace) can do with the item > as its steward, and a separate "use license" to govern what the > author/submitter wants to allow the public (or whoever can access the > item) to do with it. For the former we'll use a fixed license that looks > pretty much like the one in DSpace now, and for the latter we'll offer > some of the Creative Commons licenses. I've attached a draft of what our > UI screen might look like, and we're hoping to do the necessary > programming in the next two months. > > If this is something of general interest we'd be happy to think about > adding it to the open source system later on... just let us know. And on > a related note, a Creative Commons representative will be coming to the > DSpace user group meeting on March 10-11 to answer questions about their > status and plans for the coming year -- for example, I know they've been > tweaking their base license to address institutional concerns about > liability and so on. Should be interesting! > > As for enforcement by DSpace -- the system administrator can set access > control for items as necessary (at the bitstream, item, or collection > level) and these are enforced using whatever authentication/authorization > method you've implemented (logon/password, digital certificates, LDAP, > etc.). But *use* licenses -- those that govern what a particular user is > allowed to do with an item once they have it -- aren't really enforceable > without implementing nasty encryption techniques which get in the way of > fair use. At MIT we've decided to rely on copyright law and licenses like > the Creative Commons for use of our material, and to let the courts > enforce them if that ever proves necessary. > > I hope this answers your question! > > MacKenzie > >> Date: Thu, 18 Dec 2003 16:00:48 -0500 >> From: mao ni >> To: DSpace >> Subject: [Dspace-tech] License agreement for each item >> >> Dear All, >> >> Happy Holidays! >> >> Our E-thesis collection wants to apply flexible rights administration >> for each item, that is, every submitter could choose one from a set of >> license agreements like Creative Commons. For example, an author might >> limit his item to non-commercial use only. >> In this case, it is convenient for authors to pick up the license they >> want instead of the same license agreement for the whole collection. >> I have done this by storing the DC copyrights metadata with each item. >> My question is that if DSpace has implemented the rights limitation or >> not when the bitstream of the item is going to be viewed? For example, >> if the license of the item is not allowed to be viewed yet, will DSpace >> disallow the bitstream to be accessed? >> >> Thanks, >> >> Mao >> >> School of Information and Library Science >> University of North Carolina at Chapel Hill >> Email: maoni@ils.unc.edu >> Tel: (919) 962 - 0184 > > > MacKenzie Smith > Associate Director for Technology > MIT Libraries > Building 14S-208 > 77 Massachusetts Avenue > Cambridge, MA 02139 > (617)253-8184 > kenzie@mit.edu From scott.yeadon@anu.edu.au Sun Jan 4 21:56:05 2004 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id i052u4qb029899 for ; Sun, 4 Jan 2004 21:56:05 -0500 (EST) Received: from anu.edu.au (anumail5.anu.edu.au [150.203.2.45]) i052tw7X022498; Sun, 4 Jan 2004 21:55:59 -0500 (EST) Received: from anumail.anu.edu.au (anumail.anu.edu.au [150.203.2.90]) by anu.edu.au (8.12.10/8.12.10) with ESMTP id i052tuB2007152; Mon, 5 Jan 2004 13:55:56 +1100 (EST) Received: from sts59101.anu.edu.au (sts59101.anu.edu.au [150.203.59.101]) by anumail.anu.edu.au (8.12.10/8.12.10) with ESMTP id i052tuZQ011228; Mon, 5 Jan 2004 13:55:56 +1100 (EST) Content-Type: text/plain; charset="iso-8859-1" From: Scott Yeadon To: rrodgers@mit.edu Date: Mon, 5 Jan 2004 13:50:47 +1100 User-Agent: KMail/1.4.1 References: <200312241701.hBOH1Kqb025799@pch.mit.edu> In-Reply-To: <200312241701.hBOH1Kqb025799@pch.mit.edu> MIME-Version: 1.0 Message-Id: <200401051350.47885.scott.yeadon@anu.edu.au> X-Sender: scott.yeadon@anu.edu.au X-Sender-Domain: anu.edu.au X-Spam-Status: Scanned X-Spam-Score: (-2.9) X-Spam-Tests: EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.36 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id i052u4qb029899 cc: dspace-general@mit.edu Subject: [Dspace-general] Re: Dspace-general Digest, Vol 5, Issue 9 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list Reply-To: scott.yeadon@anu.edu.au List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 05 Jan 2004 02:56:05 -0000 Hi Richard, We at ANU would be very keen to partcipate in testing DSpace 1.2 functionality, testing the installation process, and reviewing the documentation. If there are any details you need from us prior to release of the review version, please let me know. Thanks. Scott. On Thu, 25 Dec 2003 04:01, dspace-general-request@mit.edu wrote: > Date: Tue, 23 Dec 2003 16:18:31 -0500 > From: Richard Rodgers > To: dspace-general@MIT.EDU > Subject: [Dspace-general] DSpace 1.2 Release Schedule > Message-ID: <1072214310.18829.20.camel@dspace-03.mit.edu> > Content-Type: text/plain > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Precedence: list > Message: 1 > > > A Word on DSpace 1.2 > > > I wanted to bring the community up to date on the 1.2 release schedule. > Although work on feature definition and implementation is proceeding, > the target date has receded from our optimistic early projections of the > end of this year. We want this release to be worth the wait, and also > understand the increased importance of thorough testing, since a larger > group of adopters is depending upon a smooth upgrade experience. > > > With these issues in mind, we are looking at an early March 2004 > 'preview' release, to be demonstrated at the DSpace user group meeting, > which will then be subjected to intensive evaluation and testing. > > > DSpace adopter community participation in this process will be vital, > and can assume several forms. First, we will set up a server at MIT with > 1.2 code and solicit testers to exercise it. This was done for the 1.1.1 > release, but we hope both to expand the number of participants and > improve its effectiveness by documenting the changes more fully. Second, > we would like volunteers to test the installation process, to catch > unforeseen dependencies. > I strongly recommend installers use a separate server on which to > perform the test upgrade, but one that shares the characteristics of > their production server(s) (such as customized UI, etc). Third, we will > also try to make documentation (including install docs) available in > preview, to expose any deficiencies before they are officially > published. > > > If you are willing to act in any of these capacities, let me know after > the new year, and as the release nears completion, we will contact you > with further details. > > > Have a happy holiday season, > > > Richard Rodgers > DSpace Federation Systems Manager > > > > > > ------------------------------ > > > _______________________________________________ > Dspace-general mailing list > Dspace-general@mit.edu > http://mailman.mit.edu/mailman/listinfo/dspace-general > > > > End of Dspace-general Digest, Vol 5, Issue 9 > ******************************************** From Michele.Huston@anu.edu.au Tue Jan 6 00:43:33 2004 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id i065hWqb028836 for ; Tue, 6 Jan 2004 00:43:33 -0500 (EST) Received: from CASEVS02.cas.anu.edu.au (casexg02.anu.edu.au [130.56.11.72]) i065hUqj003132 for ; Tue, 6 Jan 2004 00:43:31 -0500 (EST) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Tue, 6 Jan 2004 16:43:29 +1100 Message-ID: <6C5D773DDBA3BE42A19C738100E44528021BAD11@CASEVS02.cas.anu.edu.au> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Preservation and presentation formats Thread-Index: AcPUGAMeCzRj9DqrR0al3BvejBXoJA== From: "Michele Huston" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id i065hWqb028836 Subject: [Dspace-general] Preservation and presentation formats X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 06 Jan 2004 05:43:34 -0000 Hi all, At ANU we are looking at placing collections of images, audio and XML docs into DSpace. These files raise the issue of different formats for preservation and access. e.g. 1 Our images are in tiff format and we have generated jpeg derivatives (e.g. thumbnail and a larger web view) for display. Our thinking is that it would be better to store the derivatives in a structured files space elsewhere rather than bundled with the tiffs as they are not archive quality and we may want to regenerated them or serve them on the fly in the future. We have made some minor changes to the DSpace user interface to allow the thumbnails and the enlarged view to display. e.g. 2 Our audio files are in wav format and the access format we are using is real audio (streaming). Again our plan is to store the real audio files separate from the wav files. We don't want to archive the access formats as it is very likely that we will want to change this format in the future. e.g. 3 In the case of the XML docs we'd like to allow the user to choose between HTML and PDF and to generate these derivatives on the fly. We were wondering if anyone else has been exploring the issue of separation of the preservation and display functions in DSpace. Regards Michele Michele Huston Digital Resource Services The Australian National University Ph 02 6125 6659 michele.huston@anu.edu.au From bialangiano@yahoo.com.br Tue Jan 6 08:31:59 2004 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id i06DVxqb005319 for ; Tue, 6 Jan 2004 08:31:59 -0500 (EST) Received: from web60901.mail.yahoo.com (web60901.mail.yahoo.com [216.155.196.77])i06DVwth003486 for ; Tue, 6 Jan 2004 08:31:59 -0500 (EST) Message-ID: <20040106133158.44780.qmail@web60901.mail.yahoo.com> Received: from [200.17.212.1] by web60901.mail.yahoo.com via HTTP; Tue, 06 Jan 2004 10:31:58 ART Date: Tue, 6 Jan 2004 10:31:58 -0300 (ART) From: =?iso-8859-1?q?Beatriz=20Langiano?= To: DSpace tech list , Duvidas DSpace , Lista Dspace MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: [Dspace-general] Submitted items X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 06 Jan 2004 13:32:00 -0000 Hi, We have a problem with our submitted items. We created a community and not changed the policy of anonymous (READ). After we created a collection and not changed the policy of anonymous (READ and DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ for submitted items). The problem is the users don't have access to the submitted items of this collection (note: this users were entered in DSpace through the E-people tool), only the admin have access them. Why this occurs? Thanks, Beatriz ______________________________________________________________________ Conheça a nova central de informações anti-spam do Yahoo! Mail: http://www.yahoo.com.br/antispam From Francis.Brouns@ou.nl Tue Jan 6 10:12:05 2004 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id i06FC5qb007011 for ; Tue, 6 Jan 2004 10:12:05 -0500 (EST) Received: from aix-4.ouh.nl (mailserv2.ouh.nl [145.20.126.12]) i06FC3Za023823 for ; Tue, 6 Jan 2004 10:12:04 -0500 (EST) Received: (from root@localhost) by aix-4.ouh.nl (8.12.10.Beta2/8.12.10.Beta2) id i06FC0Jr357806 for dspace-general@mit.edu; Tue, 6 Jan 2004 16:12:00 +0100 Received: from srv-hrl-18.pwo.ou.nl (exchange-1.pwo.ou.nl [145.20.33.20]) i06FBtgD357800 for ; Tue, 6 Jan 2004 16:11:55 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 6 Jan 2004 16:11:54 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: remove policy Thread-Index: AcPUZ2shTZHR737/S6i9L6YvL4A0Zg== From: "Brouns, Francis" To: X-Virus-Scanned: by amavisd-new Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id i06FC5qb007011 Subject: [Dspace-general] remove policy X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 06 Jan 2004 15:12:05 -0000 Hello, the documentation states that policies are assigned to epeople. One of the possible actions is REMOVE. According to the documentation only administrators can remove items. Am I correct in assuming that it is not possible for an non-admin person who has been assigned REMOVE rights, to remove items? In order to remove items, a eperson needs to be an administrator. If this is case, why should I assign REMOVE rights? An adminstrator can do everything, including items. Kind regards, Francis Brouns From robert.tansley@hp.com Tue Jan 6 13:23:00 2004 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id i06IN0qb011205 for ; Tue, 6 Jan 2004 13:23:00 -0500 (EST) Received: from palrel10.hp.com (palrel10.hp.com [156.153.255.245]) i06IMthf003807 for ; Tue, 6 Jan 2004 13:22:55 -0500 (EST) Received: from hplms2.hpl.hp.com (hplms2.hpl.hp.com [15.0.152.33]) by palrel10.hp.com (Postfix) with ESMTP id 131451C01DA1; Tue, 6 Jan 2004 10:22:54 -0800 (PST) Received: from hplex1.hpl.hp.com (hplex1.hpl.hp.com [15.0.152.182]) i06IMqIp002446; Tue, 6 Jan 2004 10:22:52 -0800 (PST) Received: from 15.0.152.182 by hplex1.hpl.hp.com (InterScan E-Mail VirusWall NT); Tue, 06 Jan 2004 10:22:51 -0800 Received: by hplex1.hpl.hp.com with Internet Mail Service (5.5.2653.19) id ; Tue, 6 Jan 2004 10:22:51 -0800 Message-ID: <40700B4C02ABD5119F00009027876644084DF37B@hplex1.hpl.hp.com> From: "Tansley, Robert" To: "Brouns, Francis" , dspace-general@mit.edu Subject: RE: [Dspace-general] remove policy Date: Tue, 6 Jan 2004 10:22:43 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 06 Jan 2004 18:23:01 -0000 Hello Francis, The limitation you refer to is really just a limitation of the current Web user interface. You could give someone REMOVE rights, but currently, there is no user interface page that would let that person actually remove anything. The reason only administrators can access the relevant function right now is that the administrator UI is not yet very robust and really needs to be used by someone who knows what they are doing, as opposed to (say) a department administrator. This is likely to change over time as the user interface matures. Robert Tansley / Hewlett-Packard Laboratories / (+1) 617 551 7624 > -----Original Message----- > From: dspace-general-bounces@mit.edu > [mailto:dspace-general-bounces@mit.edu] On Behalf Of Brouns, Francis > Sent: 06 January 2004 10:12 > To: dspace-general@mit.edu > Subject: [Dspace-general] remove policy > > > Hello, > > the documentation states that policies are assigned to > epeople. One of the possible actions is REMOVE. According to > the documentation only administrators can remove items. > > Am I correct in assuming that it is not possible for an > non-admin person who has been assigned REMOVE rights, to > remove items? In order to remove items, a eperson needs to be > an administrator. > > If this is case, why should I assign REMOVE rights? An > adminstrator can do everything, including items. > > Kind regards, > > Francis Brouns > > > _______________________________________________ > Dspace-general mailing list > Dspace-general@mit.edu > http://mailman.mit.edu/mailman/listinfo/dspace> -general > From sbell@library.rochester.edu Tue Jan 6 15:20:19 2004 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id i06KKJqb015928 for ; Tue, 6 Jan 2004 15:20:19 -0500 (EST) Received: from mail.lib.rochester.edu (mail.lib.rochester.edu [128.151.244.122])i06KKImt027781 for ; Tue, 6 Jan 2004 15:20:18 -0500 (EST) Received: from RCL-MTA by mail.lib.rochester.edu with Novell_GroupWise; Tue, 06 Jan 2004 15:26:43 -0500 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.1 Date: Tue, 06 Jan 2004 15:26:32 -0500 From: "Suzanne Bell" To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline cc: acarli@esm.rochester.edu Subject: [Dspace-general] Wash., DC-area person to talk to Music Librarians about DSpace? X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 06 Jan 2004 20:20:19 -0000 Hi Folks- I am posting this message on behalf of Alice Carli, the Conservator at our Sibley Music Library. Please respond directly to her at acarli@esm.rochester.edu . Thanks from both of us! :) The Music Library Association Preservation Committee is looking for someone involved with DSpace to participate in a panel discussion at their annual meeting, which will be in: Washington D.C. on: February 11-15, the Preservation Committee presentation being 12:30-2:00 pm on Saturday 2/14. (Apologies for the short notice!) More detail as supplied by Alice: The topic of this year's public presentation will be Preservation and Copyright, and is a joint project of the Preservation and Legislative Committees. It is intended to be a minimally moderated discussion among the librarians in attendance, with input and elucidations sought from a panel which so far includes Sam Brylawski from the Library of Congress, whose expertise is in copyright, David Buecher, a preservation librarian from Berkeley, and Esther Gillie, who did sound preservation here at Eastman before going on to become Music Digital Services Coordinator at Urbana. It occurred to me somewhat belatedly that it would be good to include a representative of Dspace, who could supply information about managing copyright issues, as well as other Dspace strong points such as "format conservation" (or whatever the term is for the commitment to migration as necessary) at a consortium level. I think it would be a good opportunity to introduce music librarians to the organization, since the audience will certainly include both people like me, from universities that are already members but who nonetheless have yet to begin thinking creatively about how to use Dspace, and many people who will be hearing about the organization for the first time. I could also check with members of the Preservation Committee to see if they would be interested in inviting that person (assuming they come from the DC area) to attend the Preservation Committee business meeting, 3:00-4:30 on Thursday 2/12. We have no budget for an honorarium, but it would be a good opportunity for further networking. ******************************************* Suzanne Bell, Economics/Data Librarian DSpace Projects Coordinator University of Rochester 585/275-9317 sbell@library.rochester.edu From Francis.Brouns@ou.nl Wed Jan 7 03:23:03 2004 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id i078N2qb027178 for ; Wed, 7 Jan 2004 03:23:03 -0500 (EST) Received: from aix-4.ouh.nl (ns.ouh.nl [145.20.126.12])i078N1KI001317 for ; Wed, 7 Jan 2004 03:23:01 -0500 (EST) Received: (from root@localhost) by aix-4.ouh.nl (8.12.10.Beta2/8.12.10.Beta2) id i078N0ci201380 for dspace-general@mit.edu; Wed, 7 Jan 2004 09:23:00 +0100 Received: from srv-hrl-18.pwo.ou.nl (exchange-1.pwo.ou.nl [145.20.33.20]) i078M8gD182744 for ; Wed, 7 Jan 2004 09:22:09 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: [Dspace-general] remove policy Date: Wed, 7 Jan 2004 09:22:07 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Dspace-general] remove policy Thread-Index: AcPUgh1UT2W9gNokQAeVpN2EvGcvSQAdQ4RQ From: "Brouns, Francis" To: X-Virus-Scanned: by amavisd-new Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id i078N2qb027178 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Wed, 07 Jan 2004 08:23:03 -0000 Hello Robert, thank for your reply and confirmation. We gathered as much. It is no problem for now, and we will wait for the new user interface. Regards, Francis > -----Original Message----- > From: Tansley, Robert [mailto:robert.tansley@hp.com] > Sent: 06 January 2004 19:23 > To: Brouns, Francis; dspace-general@mit.edu > Subject: RE: [Dspace-general] remove policy > > > Hello Francis, > > The limitation you refer to is really just a limitation of > the current Web user interface. You could give someone > REMOVE rights, but currently, there is no user interface page > that would let that person actually remove anything. The > reason only administrators can access the relevant function > right now is that the administrator UI is not yet very robust > and really needs to be used by someone who knows what they > are doing, as opposed to (say) a department administrator. > This is likely to change over time as the user interface matures. > > Robert Tansley / Hewlett-Packard Laboratories / (+1) 617 551 7624 > > > -----Original Message----- > > From: dspace-general-bounces@mit.edu > > [mailto:dspace-general-bounces@mit.edu] On Behalf Of Brouns, Francis > > Sent: 06 January 2004 10:12 > > To: dspace-general@mit.edu > > Subject: [Dspace-general] remove policy > > > > > > Hello, > > > > the documentation states that policies are assigned to > > epeople. One of the possible actions is REMOVE. According to > > the documentation only administrators can remove items. > > > > Am I correct in assuming that it is not possible for an > > non-admin person who has been assigned REMOVE rights, to > > remove items? In order to remove items, a eperson needs to be > > an administrator. > > > > If this is case, why should I assign REMOVE rights? An > > adminstrator can do everything, including items. > > > > Kind regards, > > > > Francis Brouns > > > > > > _______________________________________________ > > Dspace-general mailing list > > Dspace-general@mit.edu > > http://mailman.mit.edu/mailman/listinfo/dspace> -general > > > From kenzie@MIT.EDU Fri Jan 9 10:49:44 2004 Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id i09Fniqb016977 for ; Fri, 9 Jan 2004 10:49:44 -0500 (EST) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])i09FmXFC018704; Fri, 9 Jan 2004 10:48:33 -0500 (EST) Received: from ADTPA.mit.edu (ADTPA.MIT.EDU [18.51.1.92]) (authenticated bits=0) (User authenticated as kenzie@ATHENA.MIT.EDU)i09FmVRw000663 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT); Fri, 9 Jan 2004 10:48:32 -0500 (EST) Message-Id: <5.2.1.1.2.20040108215130.01ed9780@hesiod> X-Sender: kenzie@hesiod X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Fri, 09 Jan 2004 10:43:38 -0500 To: dspace-general@MIT.EDU From: MacKenzie Smith Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Dspace-general] DSpace Federation User Group Meeting, March 10-11, 2004 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Fri, 09 Jan 2004 15:49:44 -0000 =============================================================== DSpace Federation User Group Meeting Announcement and Call for Presentations Cambridge, Massachusetts 10-11 March 2004 =============================================================== Over the past year the DSpace digital repository system, the open source software system originally developed by Hewlett-Packard and MIT, has been adopted for use by many organizations world wide. As this group of research institutions and other organizations has grown, the need for a forum to come together and share experiences, ideas, and concerns has become highly desirable. To initiate this, MIT will host a first-ever user group meeting of the DSpace Federation in March to help build connections among the adopter community and to discuss the future of the group. The DSpace Federation user group meeting will be held at MIT, in Cambridge, Massachusetts, on Wednesday March 10 and Thursday March 11, 2004. The meeting website includes additional information and will be updated frequently in the coming months: Registration will be open to all, with a registration fee of $185 per person. Online registration at the meeting website will be available by February 1, 2004. The objective of the DSpace Federation meeting is to bring together the research and other communities to share experiences and discuss the future developments of the DSpace platform and Federation of adopters. There will be presentations on current and future work being done on the DSpace platform by a variety of organizations, applications of the technology in specific organizational contexts, and discussion of future governance and maintenance options to ensure the platform's timeliness, usability, openness, and future success. In addition to presentations by the HP and MIT DSpace teams about upcoming releases and future plans, there will be keynote presentations from Google and Open Source Software experts. We are issuing a Call for Presentations by organizations using DSpace who have innovative or educational uses of the platform to share with the community, or others who have proposals for how to leverage the DSpace platform for its main preservation and access goals. Presentation proposals should be sent via email to the meeting organizers (email address below) and should take the form of brief (1 page) descriptions of the topic for presentation. All presentations will be approximately 30 minutes. Submissions are requested by January 31, 2004 and will be reviewed by members of the DSpace Federation project (http://dspace.org/federation/project.html) for acceptance notification by February 13, 2004. Further information can be obtained from the MIT organizers: MacKenzie Smith, Associate Director for Technology Julie Walker, Senior Business Strategist Richard Rodgers, DSpace Federation Systems Manager Email: dspace-meeting@mit.edu Many thanks, MacKenzie Smith Associate Director for Technology MIT Libraries 77 Massachusetts Avenue Cambridge, MA From rea.devakos@utoronto.ca Mon Jan 12 10:54:52 2004 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id i0CFspqb028645 for ; Mon, 12 Jan 2004 10:54:52 -0500 (EST) Received: from bureau8.utcc.utoronto.ca (bureau8.utcc.utoronto.ca [128.100.132.18])i0CFsoHt027080 for ; Mon, 12 Jan 2004 10:54:51 -0500 (EST) Received: from utl-194-184.library.utoronto.ca ([142.150.194.184] EHLO utoronto.ca ident: IDENT-NOT-QUERIED [port 1946]) by bureau8.utcc.utoronto.ca with ESMTP id <25094-28151>; Mon, 12 Jan 2004 10:54:03 -0500 Message-ID: <4002C317.60708@utoronto.ca> Date: Mon, 12 Jan 2004 10:53:59 -0500 From: Rea Devakos Organization: Gerstein Science Information Centre, University of Toronto Library User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.01 X-Accept-Language: en MIME-Version: 1.0 To: dspace Content-Type: multipart/alternative; boundary="------------000302090906010400030503" Subject: [Dspace-general] fundraising, costing and launch X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 12 Jan 2004 15:54:52 -0000 --------------000302090906010400030503 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi everyone We're looking for the experience of others re: 1. fundraising 2. costing 3. planing a service launch. for local DSpace installations. MIT has kindly made some information available, but I was hoping to gather some information from other institutions as well. many thanks Rea -- Rea Devakos Gerstein Science Information Centre University of Toronto 7 King's College Circle Toronto, ON Canada M5S 1A5 E: rea.devakos@utoronto.ca V: 416-978-0533 F: 416-971-2848 http://www.library.utoronto.ca/gerstein --------------000302090906010400030503 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi everyone

We're looking for the experience of others re:
1. fundraising
2. costing
3. planing a service launch.
for local DSpace installations.

MIT has kindly made some information available, but I was hoping to gather some information from other institutions as well.

many thanks

Rea
-- 
Rea Devakos
Gerstein Science Information Centre
University of Toronto
7 King's College Circle
Toronto, ON
Canada M5S 1A5
E: rea.devakos@utoronto.ca
V: 416-978-0533
F: 416-971-2848
http://www.library.utoronto.ca/gerstein
--------------000302090906010400030503-- From Michele.Huston@anu.edu.au Mon Jan 12 18:04:16 2004 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id i0CN4Gqb007091 for ; Mon, 12 Jan 2004 18:04:16 -0500 (EST) Received: from CASEVS02.cas.anu.edu.au (casexg02.anu.edu.au [130.56.11.72]) i0CN4EMp006574 for ; Mon, 12 Jan 2004 18:04:15 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Subject: Re: [Dspace-general] fundraising, costing and launch Date: Tue, 13 Jan 2004 10:04:12 +1100 Message-ID: <6C5D773DDBA3BE42A19C738100E4452801E323AD@CASEVS02.cas.anu.edu.au> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: [Dspace-general] fundraising, costing and launch Thread-Index: AcPZYGTXUcICwwQXTJS/H7H9ETKUiQ== From: "Michele Huston" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by pch.mit.edu id i0CN4Gqb007091 X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Mon, 12 Jan 2004 23:04:17 -0000 Dear Rea, I too am interested in gathering ideas for launching the DSpace service at ANU, although we are some months away. Our current thinking is not a simgle central launch but a campus roadshow based on a set of exemplars. We are preparing a number of demonstrators using the file formats tiff, wav, pdf and XML and perhaps video as well. We will then develop a presentation based on these exemplars and deliver it at Faculty and departmental meetings. We will prepare a print handout of some kind as well, perhaps a bookmark, to remind them of the URL. We have three year funding for our DSpace implementation and have no plans to charge for the service at this stage. We will need to prepare a business plan for sustainability of the service as part of the project but it is early days for us. Interest to hear what others are planning. Cheers Michele Hi everyone We're looking for the experience of others re: 1. fundraising 2. costing 3. planing a service launch. for local DSpace installations. MIT has kindly made some information available, but I was hoping to gather some information from other institutions as well. many thanks Rea -- Rea Devakos Gerstein Science Information Centre University of Toronto 7 King's College Circle Toronto, ON Canada M5S 1A5 E: rea.devakos@utoronto.ca V: 416-978-0533 F: 416-971-2848 http://www.library.utoronto.ca/gerstein From harnad@ecs.soton.ac.uk Mon Jan 12 20:54:36 2004 Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.7.21.83]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id i0D1saqb010268 for ; Mon, 12 Jan 2004 20:54:36 -0500 (EST) Received: from raven.ecs.soton.ac.uk (raven.ecs.soton.ac.uk [152.78.70.1]) i0D1sYG8003166 for ; Mon, 12 Jan 2004 20:54:34 -0500 (EST) Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1]) by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id BAA18515; Tue, 13 Jan 2004 01:52:33 GMT Received: from pandora (pandora [152.78.68.157]) by pigeon.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id BAA22323; Tue, 13 Jan 2004 01:52:12 GMT Newsgroups: bionet.journals.note Date: Tue, 13 Jan 2004 01:52:08 +0000 (GMT) From: Stevan Harnad X-Sender: harnad@pandora To: September 1998 American Scientist Forum In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information X-ECS-MailScanner: Found to be clean cc: dspace-general@mit.edu cc: OAI-general@oaisrv.nsdl.cornell.edu cc: eprints-underground@ecs.soton.ac.uk Subject: [Dspace-general] Re: EPrints, DSpace or ESpace? X-BeenThere: dspace-general@mit.edu X-Mailman-Version: 2.1 Precedence: list List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , X-List-Received-Date: Tue, 13 Jan 2004 01:54:36 -0000 Peter Suber reported the following in Open Access News http://www.earlham.edu/~peters/fos/2004_01_11_fosblogarchive.html#a107394650955511367 "Outsell http://www.outsellinc.com/index.html has released 13 predictions for the information content industry in 2004. http://home.businesswire.com/portal/site/google/index.jsp?ndmViewId=news_view&newsId=20040112005739&newsLang=en "Here's prediction #6: "The Open Access movement in scholarly and scientific publications will gain legitimacy." "In a separate, downloadable report to accompany the predictions, http://www.outsellinc.com/subscribe/freebriefsOutlook.htm Outsell says this about open access (p. 9): "The Open Access movement in scholarly and scientific publications will gain legitimacy as it transforms from a loose collection of disjointed initiatives into a new model backed by major universities and institutions worldwide....Academic institutions and the scholarly publishing world have been at loggerheads for years over the increasing cost of journal subscriptions. The irony is that most scholarly content is created by individuals employed by universities, who are then required to pay for it again in the form of published works. The new Public Library of Science is only the most prominent in a series of open-access challenges to the scholarly publishing industry, which finds itself in a real crisis situation as users and the organizations they work for start to revolt. As steam gathers under institutional archiving initiatives like DSpace, the infrastructure will be in place to support peer-to-peer from the get-go. Where there is a will, there is a way, and technology is providing the 'way' to enable creative new solutions for distribution, access, and sharing of scholarly content. Watch for even more radical and flexible knowledge-sharing initiatives in this space that will increasingly call into question the structure of an entire publishing sector." I only want to add that if steam is to gather under institutional archiving initiatives "like DSpace" then they need to get their act together and focus it specifically on the institutional self-archiving of peer-reviewed research output. Right now, DSpace, like EPrints, offers software, but unlike EPrints, DSpace offers absolutely no guidance or focus on what the software should be used for (i.e., how it is that institutions should go about designing and implementing a self-archiving policy). http://www.eprints.org/self-faq/ "Archiving" is a big word, and means (far too) many things to (too) many people. Having MIT behind the self-archiving movement looked promising initially, but until and unless they get it into focus, DSpace will just continue to be a magnet for software downloads that generate everything except open-access peer-reviewed research output! (Having said that, I have to add that the EPrints archives so far are mostly nea