Hi Eric and others re Theses authentication We find DSpace really good for dealing with the minority of work that needs more complex restrictions.
90% or more of our items belong in the first category and we try to encourage this. There is always going to be other work that has complex authentication/access issues so we have put some examples in place see links below. The three levels of access to theses in ResearchSpace are: 1. No restriction. Thesis is freely available for download over the Internet. An example is at http://hdl.handle.net/2292/375 2. Medium restriction. Abstract and front matter (up to Chapter 1) is freely available for download, but the rest of the thesis is restricted to administrator-only access. An example is at http://hdl.handle.net/2292/382 3. High restriction. The full text of the thesis is locked down for administrator-only access. The information available on ResearchSpace is the same access as provided in Voyager, the University of Auckland's online Library Catalogue. An example is at http://hdl.handle.net/2292/403 Cheers Leonie Hayes Project Manager Institutional Repositories Aotearoa University of Auckland Library New Zealand www.ira.auckland.ac.nz -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Saturday, 21 April 2007 7:10 a.m. To: [email protected] Subject: DSpace-tech Digest, Vol 12, Issue 45 Send DSpace-tech mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/dspace-tech or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of DSpace-tech digest..." Today's Topics: 1. Re: DSpace a memory hog? (Brad Teale) 2. Re: Config Submission notes (Tim Donohue) 3. Re: browse index problem (Jeffrey Trimble) 4. Re: granularity of authentication for undergrad theses (Adam Brin) 5. recommendations for a high-performance installation (Deborah Kaplan) ---------------------------------------------------------------------- Message: 1 Date: Fri, 20 Apr 2007 11:28:11 -0500 From: Brad Teale <[EMAIL PROTECTED]> Subject: Re: [Dspace-tech] DSpace a memory hog? To: Cory Snavely <[EMAIL PROTECTED]> Cc: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 Cory, Comments below: On 04/18/2007 01:54 PM, Cory Snavely wrote: > Well, as I said at first, it all depends on your definition of what a > memory hog is. Today's hog fits in tomorrow's pocket. We better all > already be used to that. Thank you for proving my point on memory bloat pervasiveness in the IT industry. This type of thinking allows vendors (whether open source or proprietary) to drive up the "base" systems requirements without greatly improving functionality because it is predestined. > Also, I don't think for a *minute* that the original developers of > DSpace made a casual choice about their development environment--in > fact, I think they made a responsible choice given the alternatives. > Let's give our colleagues credit that's due. Their choice permits > scaling and fits well for an open-source project. Putting the general > problem of memory bloat in their laps seems pretty angsty to me. > > Lastly, dedicating a server to DSpace is a choice, not a necessity. We > as implementors have complete freedom to separate out the database and > storage tiers, and mechanisms exist for scaling Tomcat horizontally as > well. In the other direction, I suspect people are running DSpace on > VMware or xen virtual machines, too. I didn't say they made a casual choice about their development environment. I said the functional requirements of the application didn't justify the memory footprint required to run this application. Whether or not they made a choice that "fits well for an open-source project" depends on your definition of Open Source. However, I don't think that debate is relevant to this discussion. As far as scaling requirements, it depends on where you want scalability. As you pointed out, there is a natural ability with web applications to scale them vertically through hardware or Tomcat's, now native, horizontal approach. Since either approach needs hardware, the memory footprint of an application needs to be taken into account. The higher the "base" system requirements, the likelihood of someone having a scalable system is lowered due to total cost of ownership (TCO). While virtual machine technology can help lower some TCO issues, it brings in a whole new batch of problems which are out of scope for this discussion. The general problem of memory bloat rests in all developers laps (mine included). As an industry, we need to constantly weigh our use of memory against the functionality we are providing. The functionality provided by Dspace isn't rocket science, and shouldn't require memory footprints greater than most of systems that get people into space. -- Brad Teale Web Application Developer Digital Library Development Lab University of Minnesota Libraries [EMAIL PROTECTED] > On Wed, 2007-04-18 at 13:40 -0500, Brad Teale wrote: >> Pan, >> >> Dspace is a memory hog considering the functionality the application >> provides. This is mainly due to the technological choices made by >> the founders of the Dspace project, and not the functional >> requirements the Dspace project fulfills. >> >> Application and memory bloat are pervasive in the IT industry. Each >> individual organization should look at their requirements whether >> they are hardware, software or both. Having to dedicate a machine to >> an application, especially a relatively simple application like >> Dspace, is wasteful for hardware resources and people resources. >> >> Web applications should _not_ need 2G of memory to "run comfortably". >> ------------------------------ Message: 2 Date: Fri, 20 Apr 2007 11:42:38 -0500 From: Tim Donohue <[EMAIL PROTECTED]> Subject: Re: [Dspace-tech] Config Submission notes To: Mark Diggory <[EMAIL PROTECTED]> Cc: "[EMAIL PROTECTED]" <[email protected]>, Dorothea Salo <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Another "heads up" to what Mark has said: It's worth noting there are TWO Configurable Submission patches currently available from SourceForge: 1) Configurable Submission Patch, v. 2.0: http://sourceforge.net/tracker/index.php?func=detail&aid=1532695&group_i d=19984&atid=319984 2) Configurable Submission - JSP UI & Manakin (i.e. v. 3.0): http://sourceforge.net/tracker/index.php?func=detail&aid=1691345&group_i d=19984&atid=319984 The former (#1) is a stable patch for DSpace 1.4 The latter (#2) is an "alpha" release of the patch that will be going into DSpace 1.5 So, if you want to use the Configurable Submission right now, #1 is the best choice (and rightly linked by Dorothea). This is also the patch which is described in detail on the Wiki: http://wiki.dspace.org/ConfigurableSubmissionSystem However, #2 includes some subtle changes that needed to be made to make it work properly with Manakin as well as with the JSP user interface. So, technically #1 is completely stable in DSpace 1.4, but will become obsolete as soon as DSpace 1.5 is released. (However for those using the stable 1.4 version now, I should be able to provide some migration suggestions, especially if you decide to create your own custom steps, etc) I apologize for any confusion this causes, but this is unfortunately what is necessary to bring the Configurable Submission into line with the upcoming DSpace 1.5 release. As always, feel free to contact me for more details, or if you have questions regarding the Configurable Submission. - Tim Mark Diggory wrote: > Just a "heads up", Tim's Configurable Submission patch becomes the > default Submission UI in Manakin in 1.5, so adopting it early should > be a fine solution. > > > On Feb 2, 2007, at 8:31 AM, Dorothea Salo wrote: > >> majx wrote: >>> Hi dsapce-tech, >>> We want to simplefy the submit procedure for the researcher in >>> just 2 or 3 steps. That means integrate the edit metadata >>> steps,upload file and license in one steps,and then verify and >>> complete what a researcher submit. Is there any one carry out >>> similar function? How to do it? Thanks >> You want to look at Tim Donohue's Customizable Item Submission patch: >> >> <http://sourceforge.net/tracker/index.php? >> func=detail&aid=1532695&group_id=19984&atid=319984> >> >> See also the DSpace Wiki: >> >> <http://wiki.dspace.org/index.php//ConfigurableSubmissionSystem> >> >> Dorothea >> >> -- >> Dorothea Salo, Digital Repository Services Librarian >> (703)993-3742 [EMAIL PROTECTED] AIM: gmumars >> MSN 2FL, Fenwick Library >> George Mason University >> 4400 University Drive, Fairfax VA 22031 >> >> >> --------------------------------------------------------------------- >> - >> --- >> Using Tomcat but need to do more? Need to support web services, >> security? >> Get stuff done quickly with pre-integrated technology to make your >> job easier. >> Download IBM WebSphere Application Server v.1.0.1 based on Apache >> Geronimo http://sel.as-us.falkag.net/sel? >> cmd=lnk&kid=120709&bid=263057&dat=121642_____________________________ >> _ >> _________________ >> DSpace-tech mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/dspace-tech > > ~~~~~~~~~~~~~ > Mark R. Diggory - DSpace Systems Manager MIT Libraries, Systems and > Technology Services Massachusetts Institute of Technology > Office: E25-131 > Phone: (617) 253-1096 > > > > ---------------------------------------------------------------------- > --- This SF.net email is sponsored by DB2 Express Download DB2 Express > C - the FREE version of DB2 express and take control of your XML. No > limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > DSpace-tech mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-tech > ------------------------------ Message: 3 Date: Fri, 20 Apr 2007 12:47:34 -0400 From: Jeffrey Trimble <[EMAIL PROTECTED]> Subject: Re: [Dspace-tech] browse index problem To: "Jose Blanco" <[EMAIL PROTECTED]>,<[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii"; format=flowed No..Tomcat was not running at the point of the index all. When I changed my config file back to the original, and index-all, started tomcat, all worked again. Hmmmmm -jat At 11:44 AM 4/20/2007, Jose Blanco wrote: >Did you restart tomcat before running index-all? > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Jeffrey >Trimble >Sent: Friday, April 20, 2007 11:39 AM >To: [email protected] >Subject: [Dspace-tech] browse index problem > >I attempted to limit the browse index for subjects. Originally, I had >webui.browse.index.subject = dc.subject.* > >I changed it to: > >webui.browse.index.subject = dc.subject.lcsh, dc.subject.other > >And now when I run the index-all I get this error: > >Creating browse index >Indexing all Items in DSpace....Exception in thread "main" >java.lang.ArrayIndexO >utOfBoundsException: 3 > at org.dspace.browse.Browse.getMetadataField(Browse.java:665) > at org.dspace.browse.Browse.itemAdded(Browse.java:530) > at org.dspace.browse.Browse.indexAll(Browse.java:606) > at >org.dspace.browse.InitializeBrowse.main(InitializeBrowse.java:74) >Creating search index >Done with indexing > >Is my syntax wrong? > >TIA, > > >Jeffrey A. Trimble >Systems Librarian >Youngstown State University >Youngstown, OH >[EMAIL PROTECTED] >(330) 941-2483 >http://digital.maag.ysu.edu >http://www.maag.ysu.edu >http://jupiter.ysu.edu > > > > >----------------------------------------------------------------------- >-- This SF.net email is sponsored by DB2 Express Download DB2 Express C >- the FREE version of DB2 express and take control of your XML. No >limits. Just data. Click to get it now. >http://sourceforge.net/powerbar/db2/ >_______________________________________________ >DSpace-tech mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/dspace-tech Jeffrey A. Trimble Systems Librarian Youngstown State University Youngstown, OH [EMAIL PROTECTED] (330) 941-2483 http://digital.maag.ysu.edu http://www.maag.ysu.edu http://jupiter.ysu.edu ------------------------------ Message: 4 Date: Fri, 20 Apr 2007 12:09:27 -0400 From: "Adam Brin" <[EMAIL PROTECTED]> Subject: Re: [Dspace-tech] granularity of authentication for undergrad theses To: "'Jose Blanco'" <[EMAIL PROTECTED]>, "'Eric Luhrs'" <[EMAIL PROTECTED]>, <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" We've tried to setup the authentication on the 'part' level but it doesn't really work. Dspace will prompt you for authentication when your PDF reader/viewer is trying to open the file, and Acrobat, at least, gets well, grumpy. - adam _____________________________________ Tri-Colleges Systems Coordinator Bryn Mawr | Haverford | Swarthmore 610.526.5294 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jose Blanco Sent: Friday, April 20, 2007 11:21 AM To: 'Eric Luhrs'; [email protected] Subject: Re: [Dspace-tech] granularity of authentication for undergrad theses As I understand it, authorization is item specific. Now, if you set up a collection and you give say read permissions to bitstreams to a certain group of epeople, then when items are submitted to the collection, the items will inherit these permissions, and if you change the permissions on the collection, the items in the collection retain the permissions they had, but any items deposited from then on will inherit the permissions new permissions. The out of the box DSpace does not allow you to setup permissions based on IP, but there is a patch that can help with this ( I think ). What the patch basically does is determine the ip address of the item and then based on this makes the user a member of a group that you need to have setup to have permissions for the items. This membership is carried on the context and expires when the user ends the session. -Jose -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Luhrs Sent: Friday, April 20, 2007 11:08 AM To: [email protected] Subject: [Dspace-tech] granularity of authentication for undergrad theses Hello all, Lafayette College is in the planning stages for a DSpace repository. While our planning team (which includes a few faculty members) is interested in providing public access to undergraduate honors theses, some other faculty members have expressed concerns. In looking at permission forms used by other institutions, I see that students are often given a choice of the level of access they desire: world, on-campus, or none. This, for me, raises questions about the granularity of authentication. I had thought that authentication was controlled at the collection level, but now I wonder if it can be controlled at the item level. So far, I have only installed an open system with no authentication, so I'm in uncharted water. My questions: Is it possible to have a single collection that provides open access to certain documents, and IP or LDAP restricted access to others? If this level of granularity is possible, is it difficult to implement? Do others have advice for dealing with these issues (either politically, and technically)? Thanks for whatever help you can provide. Eric Luhrs Digital Initiatives Librarian Lafayette College ------------------------------------------------------------------------ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech ------------------------------------------------------------------------ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech ------------------------------ Message: 5 Date: Fri, 20 Apr 2007 14:29:39 -0400 (EDT) From: Deborah Kaplan <[EMAIL PROTECTED]> Subject: [Dspace-tech] recommendations for a high-performance installation To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: TEXT/PLAIN; charset=US-ASCII We're going to be setting up a new DSpace+Manakin installation and I have a few questions about performance tuning. I see looking at the mail archives that there are people using a clustered Tomcat configuration with a single database backend. Are there any tricks to doing so? Any particular problems with hitting the database in this way? Any recommendations for the best filesystem to use for storing the bitstreams in order to optimize performance? Can you use a clustered filesystem? Thanks for any advice, -Deborah -- Deborah Kaplan Digital Initiatives Librarian Brandeis University ------------------------------ ------------------------------------------------------------------------ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ------------------------------ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech End of DSpace-tech Digest, Vol 12, Issue 45 ******************************************* ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
