Dear
It really depends on the type of file to edit where you edit it. I prefer to edit all files at level 1. Though I admit that, some quick n' dirty, (css) testing can, indeed, be done at level 4. Even then, it good to, afterwards, copy the code from the tomcat level to level 1 again. In a previous version I didn't always see the changes I made because the tomcat kept somehow an older version runnning which was very confusing. Because of that, I, now, always, delete, before building, the sources at sources/target level and the tomcat level (both webapps & work/). Ok building takes some time but the code remaines consistent. Yours Sincerely Christof Στις 04-05-2010, ημέρα Τρι, και ώρα 12:36 +0000, ο/η [email protected] έγραψε: > 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. ETD Submission Workflow (Lewatle Phaladi) > 2. Re: ETD Submission Workflow (Bram Luyten) > 3. A general question about editing a file from a newcomer (Shaw Yu) > 4. Re: ETD Submission Workflow (Gavin Henrick) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 4 May 2010 11:53:14 +0200 > From: "Lewatle Phaladi" <[email protected]> > Subject: [Dspace-tech] ETD Submission Workflow > To: <[email protected]> > Cc: Mark Diggory <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > Hi DSpace Team > > > > Here in my University we need a Module that we can use in Dspace to > manage the ETD collection during submission of theses and that will also > allows different users to participate during that submission process, > the Dspace programme should allows students to submit their scanned > theses and put their metadata and submit but the item should not be > published before the examiner ratifies it and the supervisor also views > it. > > > > Even if the solution is proprietary one you may suggest it, I Cc you > Mark as you are with @mire and I am aware that you guys are doing more > or less on Dspace Modules. > > > > Regards, > > Lewatle > > > <html><p><font face = "verdana" size = "0.8" color = "navy">This > communication is intended for the addressee only. It is confidential. If you > have received this communication in error, please notify us immediately and > destroy the original message. You may not copy or disseminate this > communication without the permission of the University. Only authorized > signatories are competent to enter into agreements on behalf of the > University and recipients are thus advised that the content of this message > may not be legally binding on the University and may contain the personal > views and opinions of the author, which are not necessarily the views and > opinions of The University of the Witwatersrand, Johannesburg. All agreements > between the University and outsiders are subject to South African Law unless > the University agrees in writing to the contrary.</font></p></html> > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > Message: 2 > Date: Tue, 4 May 2010 13:45:58 +0200 > From: Bram Luyten <[email protected]> > Subject: Re: [Dspace-tech] ETD Submission Workflow > To: Lewatle Phaladi <[email protected]> > Cc: [email protected], Mark Diggory > <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Lewatle, > > although we don't offer a module that fulfills your requirements, this is > the type of workflow customization we could do for you in a customization > project. > > I've seen quite a few different, and interesting approaches towards ETD's in > DSpace. One of them is Munin ( http://www.ub.uit.no/munin/ ). If I remember > correctly, they use 2 instances of DSpace: an internal one where ALL ETD's > are submitted and archived. A selection of quality ETD's is then exported to > the second instance of DSpace, a public one, that publishes these ETD's > online. > > This work was presented at the DSpace user group in 2007 ( > http://demo-eprints.cilea.it/conf/viewabstract.php?id=258&cf=11 ). > > To which extent is the current workflow system insufficient for your usecase > ? I would assume that the existing roles of metadata edtors or reviewers > could get you already quite far. > > This is also something we could examine for you, in order to dermine which > customizations e.g. are necessary. > > best regards, > > Bram Luyten > > @mire - http://www.atmire.com > > Technologielaan 9 - 3001 Heverlee - Belgium > 533 2nd Street - Encinitas, CA 92024 - USA > > http://www.togather.eu - Before getting together, get t...@ther > > > On Tue, May 4, 2010 at 11:53 AM, Lewatle Phaladi <[email protected] > > wrote: > > > Hi DSpace Team > > > > > > > > Here in my University we need a Module that we can use in Dspace to manage > > the ETD collection during submission of theses and that will also allows > > different users to participate during that submission process, the Dspace > > programme should allows students to submit their scanned theses and put > > their metadata and submit but the item should not be published before the > > examiner ratifies it and the supervisor also views it. > > > > > > > > Even if the solution is proprietary one you may suggest it, I Cc you Mark > > as you are with @mire and I am aware that you guys are doing more or less on > > Dspace Modules. > > > > > > > > Regards, > > > > Lewatle > > > > This communication is intended for the addressee only. It is confidential. > > If you have received this communication in error, please notify us > > immediately and destroy the original message. You may not copy or > > disseminate this communication without the permission of the University. > > Only authorized signatories are competent to enter into agreements on > > behalf of the University and recipients are thus advised that the content > > of this message may not be legally binding on the University and may > > contain the personal views and opinions of the author, which are not > > necessarily the views and opinions of The University of the Witwatersrand, > > Johannesburg. All agreements between the University and outsiders are > > subject to South African Law unless the University agrees in writing to the > > contrary. > > > > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > > DSpace-tech mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/dspace-tech > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > Message: 3 > Date: Tue, 04 May 2010 08:26:33 -0400 > From: Shaw Yu <[email protected]> > Subject: [Dspace-tech] A general question about editing a file from a > newcomer > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi there, > > I found that a file (e.g., style.css) can be edited at least at 4 levels > (any system is more complicated than this?): > > 1. at the source/modules level > 2. at the source/target level > 3. at dspace level > 4. at tomcat level > > Are there general rules about at which level that a file should be > edited? It looks like to edit a file at (4) is easiest (no rebuild is > needed) but is also easiest to be overwritten late. To edit a file at > (1) is just the opposite. > > Is it true that we should do most of our editing at '2. the > source/target level' and than issue an ANT command? > > Thank you. > > Shaw > VCU Libraries > > > > ------------------------------ > > Message: 4 > Date: Tue, 4 May 2010 13:35:39 +0100 > From: Gavin Henrick <[email protected]> > Subject: Re: [Dspace-tech] ETD Submission Workflow > To: Lewatle Phaladi <[email protected]> > Cc: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Lewatle, > > We implemented a customisation similar to this for Trinity College Dublin > (originally for 1.3x but now migrated to 1.6) > > I attach a PDF of the workflow slide that we implemented for their DSpace. > > *This slide is taken from the presentation at the Edinburgh Repository > Fringe 2008 by Niamh Brennan, TCD - > http://www.era.lib.ed.ac.uk/handle/1842/2420 * > > This doesn't cover a lot of the details implemented like licences and > restrictions, but is a general feel for what was done. > > Is that something along the lines you were thinking about? > > Regards > > Gavin Henrick > > FYI: Just for clarity, the "we" I mentioned is Enovation Solutions in > Dublin, an open source consultancy - who work on DSpace, Fedora, and > eprints. www.enovation.ie > > > On Tue, May 4, 2010 at 10:53 AM, Lewatle Phaladi <[email protected] > > wrote: > > > Hi DSpace Team > > > > > > > > Here in my University we need a Module that we can use in Dspace to manage > > the ETD collection during submission of theses and that will also allows > > different users to participate during that submission process, the Dspace > > programme should allows students to submit their scanned theses and put > > their metadata and submit but the item should not be published before the > > examiner ratifies it and the supervisor also views it. > > > > > > > > Even if the solution is proprietary one you may suggest it, I Cc you Mark > > as you are with @mire and I am aware that you guys are doing more or less on > > Dspace Modules. > > > > > > > > Regards, > > > > Lewatle > > > > This communication is intended for the addressee only. It is confidential. > > If you have received this communication in error, please notify us > > immediately and destroy the original message. You may not copy or > > disseminate this communication without the permission of the University. > > Only authorized signatories are competent to enter into agreements on > > behalf of the University and recipients are thus advised that the content > > of this message may not be legally binding on the University and may > > contain the personal views and opinions of the author, which are not > > necessarily the views and opinions of The University of the Witwatersrand, > > Johannesburg. All agreements between the University and outsiders are > > subject to South African Law unless the University agrees in writing to the > > contrary. > > > > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > > DSpace-tech mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/dspace-tech > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: tcd-workflow.pdf > Type: application/pdf > Size: 143575 bytes > Desc: not available > > ------------------------------ > > ------------------------------------------------------------------------------ > > > ------------------------------ > > _______________________________________________ > DSpace-tech mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-tech > > > End of DSpace-tech Digest, Vol 49, Issue 10 > ******************************************* ------------------------------------------------------------------------------ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
