Answer on Message 2:
Dear
I believe all ‘Custom’ Codes should be written in
\dspace-1.5.2-src-release\dspace\modules
For JSP : Follow the tree structure under
\dspace-1.5.2-src-release\dspace-jspui\dspace-jspui-webapp\src\main\webapp
An example:
If you want to change the file full.jsp
(\dspace-1.5.2-src-release\dspace-jspui\dspace-jspui-webapp\src\main\webapp\browse\full.jsp)
1. Build, under modules, the same tree structure as in \browse directory
under \dspace-1.5.2-src-release\dspace-jspui\dspace-jspui-webapp\src\main\webapp
• Create the \browse directory under
\dspace-1.5.2-src-release\dspace\modules\jspui\src\main\webapp
• Copy the full.jsp
(\dspace-1.5.2-src-release\dspace\modules\jspui\src\main\webapp\browse\full.jsp)
• Change this file
For Java Classes : Follow the tree structure under
\dspace-1.5.2-src-release\dspace-jspui\dspace-jspui-api\src\main
An example:
If you want to change the file BrowseListTag.java
(\dspace-1.5.2-src-release\dspace-jspui\dspace-jspui-api\src\main\java\org\dspace\app\webui\jsptag\BrowseListTag.java)
2. Build, under modules, the same tree structure as in the directories
under
\dspace-1.5.2-src-release\dspace-jspui\dspace-jspui-api\src\main\java\org\dspace\app\webui\jsptag
[starting from the \java folder]
• Create the \java\org\dspace\app\webui\jsptag directory under
\dspace-1.5.2-src-release\dspace\modules\jspui\src\main\
• Copy the BrowseListTag.java
(dspace-1.5.2-src-release\dspace-jspui\dspace-jspui-api\src\main\java\org\dspace\app\webui\jsptag\BrowseListTag.java)
• Change this file
Yours Sincerely
Christof Verdonck
Email:christof.verdo...@uhasselt.be
-Original Message-
From: dspace-tech-requ...@lists.sourceforge.net
[mailto:dspace-tech-requ...@lists.sourceforge.net]
Sent: woensdag 9 september 2009 1:25
To: dspace-tech@lists.sourceforge.net
Subject: DSpace-tech Digest, Vol 41, Issue 15
Send DSpace-tech mailing list submissions to
dspace-tech@lists.sourceforge.net
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
dspace-tech-requ...@lists.sourceforge.net
You can reach the person managing the list at
dspace-tech-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than Re: Contents of DSpace-tech digest...
Today's Topics:
1. Re: small correction for dspace_migrate (John Davison)
2. Customize Dspace 1.5 using JSP (Khan, Baseer)
3. SWORD and DSpace HowTo Available? (penning...@rhodes.edu)
4. Can Stemming be turned off in DSpace Lucene searches?
(Thornton, Susan M. (LARC-B702)[RAYTHEON TECHNICAL SERVICES COMPANY])
5. Re: Can Stemming be turned off in DSpaceLucenesearches?
(Kim Shepherd)
--
Message: 1
Date: Tue, 08 Sep 2009 14:22:56 -0400
From: John Davison j...@ohiolink.edu
Subject: Re: [Dspace-tech] small correction for dspace_migrate
To: Stuart Lewis s.le...@auckland.ac.nz
Cc: dspace-tech@lists.sourceforge.net
dspace-tech@lists.sourceforge.net
Message-ID: 4aa6a100.3050...@ohiolink.edu
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Collection-based export is working as expected when using the -m
(migrate) flag in DSpace 1.5.2 with one exception.
/bin/export ItemExport --type=COLLECTION --id=collID --dest=dest_dir
--number=seq_num -m
This will correctly remove the handle file, as well as the following
metadata fields from dublin_core.xml:
dcvalue element=date qualifier=accessioned/dcvalue
dcvalue element=date qualifier=available/dcvalue
dcvalue element=date qualifier=issued/dcvalue*
dcvalue element=description qualifier=provenance/dcvalue
dcvalue element=format qualifier=extent/dcvalue
dcvalue element=format qualifier=mimetype/dcvalue
(*Date.issued is retained if the item has been published before.)
It also removes dc.identifier.uri in all cases. The dspace_migrate
script uses a regular expression to only remove identifier.uri fields
that start with http://hdl (retaining non-handle based identifier.uri
elements), while ItemExport.java is eliminating all identifier.uri fields.
Line 474:
if ((!migrate) ||
(migrate !(
(dcv.element.equals(date)
qualifier.equals(issued)) ||
(dcv.element.equals(date)
qualifier.equals(accessioned)) ||
(dcv.element.equals(date)
qualifier.equals(available)) ||
(dcv.element.equals(identifier)
qualifier.equals(uri)) ||
(dcv.element.equals(description)
qualifier.equals(provenance)) ||
(dcv.element.equals(format)
qualifier.equals(extent
