Re: [Dspace-tech] Adding description to a file through bulk

2009-03-26 Thread Surinder Kumar Gaba
We are using Dspace 1.4.2 for our application. After putting tab
between files and description, it was giving file not found. Even
putting tab with the help of programming langauage, it was still
giving error.  After checking the programme import.java, we didnot
find the code of putting file description with the contents file. When
we checked the DSpace 1.5 code, it was implemented. We just copy the
code from DSpace 1.5 and update the DSpace 1.4. It is working and
showing the file description.

Thanks for providing timely help.

regards

Surinder Kumar

Claudia J?rgen responds:

Hi Surinder,

in the contens file of the item to be imported, just add
\tdescription:YourDescription

e.g.
foo.pdf description:SomeText

Note that the whitespace between filename and description got to be a
tabulator.

Hope that helps

Claudia J?rgen


Surinder Kumar Gaba schrieb:
 We are uploading data through bulk load programme to DSpace. We would
 like to add description to each file. For example iqrs.pdf image pdf,
 pqrs.pdf text pdf.  In a single record submission, Dspace respond with
 file description. How Can I achieve this with bulk load programme.

 regards

-- 
Surinder Kumar Gaba
Technical Director
Bibliographic Informatics Division
National Informatics Centre
A-Block, CGO Complex, Lodhi Road
New Delhi-110 003
Tel : 011-24362359 (o)
  : 011-27865224 (r)

--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


[Dspace-tech] 1.5.2 Testhaton Roadmap

2009-03-26 Thread Andrea Bollini
Dear DSpace users and developers (please excuse the cross-post),
thanks to all for the efforts done in the Testhaton.
Some bugs have been reported and we are already at work to solve them!

You can find the progress status on the 1.5.2 JIRA page:
http://jira.dspace.org/jira/browse/DS/fixforversion/10012

The official release is expected on April 6th.

Anyone who would be interested in helping with the last patches can go
on using the testhaton
instance at CILEA
http://dspace-testhaton.cilea.it/jspui/

we will apply the patches when available on JIRA also before to commit
them to the main SVN repo to allow early reviews to all the community.
Best regards,
Andrea

-- 
Dott. Andrea Bollini
Project Manager, IT Architect  Systems Integrator
Sezione Servizi per le Biblioteche e l'Editoria Elettronica
CILEA, http://www.cilea.it
tel. +39 06-59292853
cel. +39 348-8277525

---

Disclaimer: the content of this email is confidential and may be privileged, 
and it must not be disclosed or copied without the sender's consent. If you 
have received this message in error, please notify the sender and remove it 
from your system. The content of this email does not constitute legal advice, 
nor any responsibility is accepted for loss or damage incurred as a result of 
acting upon its contents or attachments. 
The statements and opinions expressed in this email are those of the author and 
do not necessarily reflect those of the employer.


--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] Changes to Messages.properties not being recognized

2009-03-26 Thread Kurzenberger, Eric
Hi Gary,

I am indeed using 1.5.1.  Sorry about the confusion, but I confirmed that 
Messages.properties is indeed in

/[my dspace-source]/dspace/modules/jspui/src/main/resources

I made sure the dspace user was the owner of both the dspace source and tomcat 
directories, then followed the four steps you outlined successfully.  But when 
I attempted to define a context path in Tomcat for JSPUI and restarted Tomcat, 
I got a 404 error when loading the dspace webpage with the message The 
requested resource () is not available.  Undoing the change I made to the 
tomcat server.xml file and copying the JSPUI webapp to Tomcat's webapps 
directory worked, but my changes to Messages.properties still aren't reflected.

When changing the tomcat server.xml file, I also made sure to specify my dspace 
install directory and that the changes were made within the host element.

FYI, changing the owner to the dspace user did indeed take care of those 
failure to delete build errors I was getting.

You also mentioned trying the source release rather than the default release.  
Would I be able to change my install to the source release without overwriting 
my current configuration and data?

I appreciate all the help.

Cheers,

Eric


On 3/25/09 6:23 PM, Gary Browne g.bro...@library.usyd.edu.au wrote:

Hello again Eric,

This is a little puzzling, but I know I've been more than puzzled by
Messages.properties in the past. I don't like to be defeated by one
little flat file, so I'm going to ask a few more questions...

Firstly, it looks like and I'm assuming you are on 1.5.1. Correct?

The reason I asked if you had your Messages.properties in the
[dspace-source]/dspace/modules/jspui/src/main/resources/ directory was
that in your original email it was listed as
[Dspace-source]/modules/jspui/main/resources. So I'll just get you to
double check that directory for me.

Also, I haven't tried the default release but I couldn't find any
mention of .war files in the install instructions. Maybe you could try
one of the alternative deployment methods (see below). But first, can I
get you to confirm that you have followed each of these steps:

i) cd [dspace-source]/dspace
ii) mvn package
iii) cd target/dspace-[version].dir
iv) ant init_configs

Having followed these procedures, can you then either:

A) DEFINE A CONTEXT PATH IN TOMCAT FOR THE JSPUI

Add the following to your [tomcat-home]/conf/server.xml, within the
Host element:


!-- DEFINE A CONTEXT PATH FOR DSpace JSP User Interface  --
Context path=/jspui
docBase=[dspace-install-directory]\webapps\jspui debug=0
reloadable=true cachingAllowed=false
allowLinking=true/

OR:

B) COPY YOUR JSPUI WEBAPP TO TOMCAT'S WEBAPPS DIRECTORY

cp -r  [dspace-install-directory]/webapps/jspui [tomcat-home]/webapps/


AFAIK the default and source releases should behave the same in terms of
building and deployment, but someone else could confirm or deny this?

I look forward to your reply (or indeed anyone else's thoughts on this
issue).

Gary

P.S. Has the failure to delete error been resolved as a result of
permissions changes?


Gary Browne
Development Programmer
Library IT Services
University of Sydney
ph: 9351-5946


 -Original Message-
 From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu]
 Sent: Thursday, 26 March 2009 6:53 AM
 To: Gary Browne; DSpace-tech@lists.sourceforge.net
 Subject: Re: [Dspace-tech] Changes to Messages.properties not
 being recognized

 Hi Gary,

 I already had the Messages.properties file in
 [dspace-source]/dspace/modules/jspui/src/main/resources/
 prior to building and deploying, following the instructions
 in the Dspace wiki (which Van Ly also sent in response to
 this thread).  No luck.  Could this be because I'm using the
 default release and not the source release?  I can't for the
 life of me figure out why the dspace install would be
 ignoring the Messages.properties file.

 Cheers,

 Eric

 On 3/24/09 11:08 PM, Gary Browne
 g.bro...@library.usyd.edu.au wrote:

 Hi Eric,

 Upon further investigation, the path to your source
 Messages.properties appears to be incorrect. I have:

 [dspace-source]/dspace/modules/jspui/src/main/resources/Messag
 es.propert
 ies

 Try sticking your Messages.properties file in that location
 and going through the build and deploy steps again.

 The 'failure to delete' error looks like a permissions
 problem. Make sure all your source files are owned by the
 'dspace' user (or whatever you choose to call the user which
 runs tomcat).

 Good luck.
 Cheers
 Gary


 Gary Browne
 Development Programmer
 Library IT Services
 University of Sydney
 ph: 9351-5946


  -Original Message-
  From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu]
  Sent: Wednesday, 25 March 2009 2:00 PM
  To: Gary Browne; DSpace-tech@lists.sourceforge.net
  Subject: Re: [Dspace-tech] Changes to Messages.properties not being
  recognized
 
  Thanks for the response, Gary.  I followed the steps you
 outlined, but
  still am 

Re: [Dspace-tech] Incorrect DSpace subscription links

2009-03-26 Thread Brett, Hamish
Hi Claudia

I went to do as you instructed; however it appears I do not have the *.java 
files on my instance. Are they meant to be downloaded through Maven?

It looks to me I just get the required *.jar files during installation and 
redeployment.

Can you please clarify what is required here

Thanks

Hamish

-Original Message-
From: Claudia Jürgen [mailto:claudia.juer...@ub.uni-dortmund.de] 
Sent: Tuesday, 24 March 2009 5:42 PM
To: Brett, Hamish
Subject: Re: [Dspace-tech] Incorrect DSpace subscription links

P. S. then you got to rebuild and redeploy your application

Brett, Hamish schrieb:
 Thanks Claudia I will give that a go
 
 Hamish
 
 -Original Message-
 From: Claudia Jürgen [mailto:claudia.juer...@ub.uni-dortmund.de]
 Sent: Monday, 23 March 2009 5:21 PM
 To: Brett, Hamish
 Subject: Re: [Dspace-tech] Incorrect DSpace subscription links
 
 Hi Brett,
 
 you apply a patch by using the patch command patch -p0  
 /path/to/the/patch
 
 Claudia
 
 
 Brett, Hamish schrieb:
 Thanks Claudia,

 This might be a silly question but how do I apply the pathc.

 Thanks

 hamish

 -Original Message-
 From: Claudia Jürgen [mailto:claudia.juer...@ub.uni-dortmund.de]
 Sent: Friday, 20 March 2009 8:14 PM
 To: Brett, Hamish
 Cc: DSpace Tech
 Subject: Re: [Dspace-tech] Incorrect DSpace subscription links

 Hi Hamish,

 blanks have been added between label and text in subscription email in 
 1.5.x. Attached is a patch which you can use on your 1.5.1 instance.

 Hope that helps

 Claudia Jürgen


 Brett, Hamish schrieb:
 Hi

 we are using version 1.5.1 and since using this version we have had 
 issues with the subscription emails.

 The embedded links are not clickable as they have the prefix ID: 
 (see example below)

 
 ID:http://dspace-dsto.dsto.defence.gov.au/dspace/handle/dsto/6711

 this does not occur in other emails like registration and password 
 changes

  

 any ideas

 thanks

 hamish


 IMPORTANT: This email remains the property of the Australian Defence 
 Organisation and is subject to the jurisdiction of section 70 of the CRIMES 
 ACT 1914.  If you have received this email in error, you are requested to 
 contact the sender and delete the email.





 
 -
 -
 --

 
 -
 -
  Apps built with the Adobe(R) Flex(R) framework and Flex
 Builder(TM) are powering Web 2.0 with engaging, cross-platform 
 capabilities. Quickly and easily build your RIAs with Flex Builder, 
 the Eclipse(TM)based development software that enables intelligent 
 coding and step-through debugging.
 Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com


 
 -
 -
 --

 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech

IMPORTANT: This email remains the property of the Australian Defence 
Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 
1914.  If you have received this email in error, you are requested to contact 
the sender and delete the email.




--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] Changes to Messages.properties not being recognized

2009-03-26 Thread Gary Browne
Hi Eric,

Just starting to think about the weekend here...so maybe not in the
right brainspace to answer this well.

It might be helpful if you posted the relevant parts of your tomcat
server.xml file (ie: your Host element and the contained Context element
- are there only one of each, or do you have multiple hosts in tomcat?).

To try out the source release, firstly backup your database and
assetstore (if possible). It might be worth replicating the db and using
this replicated db to try out the source release. Just set the relevant
(replicated) db parameters, and (different from existing) dspace.dir and
assetstore.dir in [dspace-source]/dspace/config/dspace.cfg, then follow
the previous steps that I've outlined. Alternatively, you could just try
a fresh_install with different db parameters, since it's not really
changes in the db that you're interested in testing.

Can anyone think of anything else that needs to be done to avoid
overwriting the existing setup? If possible try the whole setup on a
different machine so you're guaranteed of no cross-contamination. If the
fresh_install works, you can then copy your existing db and assetstore
to the new setup (along with any code changes you've made, if any),
rebuild and deploy (mvn package, ant update, ant init_configs). You also
might want to keep your old logs if you have people viewing the stats
regularly.

I'd be interested to see if this works, 'cause I'm stumped as to why
it's not with your current setup.

I'll think about it over the weekend... ;)

Cheers
Gary


Gary Browne
Development Programmer
Library IT Services
University of Sydney
ph: 9351-5946
 

 -Original Message-
 From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu] 
 Sent: Friday, 27 March 2009 3:09 AM
 To: Gary Browne; DSpace-tech@lists.sourceforge.net
 Subject: Re: [Dspace-tech] Changes to Messages.properties not 
 being recognized
 
 Hi Gary,
 
 I am indeed using 1.5.1.  Sorry about the confusion, but I 
 confirmed that Messages.properties is indeed in
 
 /[my dspace-source]/dspace/modules/jspui/src/main/resources
 
 I made sure the dspace user was the owner of both the dspace 
 source and tomcat directories, then followed the four steps 
 you outlined successfully.  But when I attempted to define a 
 context path in Tomcat for JSPUI and restarted Tomcat, I got 
 a 404 error when loading the dspace webpage with the message 
 The requested resource () is not available.  Undoing the 
 change I made to the tomcat server.xml file and copying the 
 JSPUI webapp to Tomcat's webapps directory worked, but my 
 changes to Messages.properties still aren't reflected.
 
 When changing the tomcat server.xml file, I also made sure to 
 specify my dspace install directory and that the changes were 
 made within the host element.
 
 FYI, changing the owner to the dspace user did indeed take 
 care of those failure to delete build errors I was getting.
 
 You also mentioned trying the source release rather than the 
 default release.  Would I be able to change my install to the 
 source release without overwriting my current configuration and data?
 
 I appreciate all the help.
 
 Cheers,
 
 Eric
 
 
 On 3/25/09 6:23 PM, Gary Browne 
 g.bro...@library.usyd.edu.au wrote:
 
 Hello again Eric,
 
 This is a little puzzling, but I know I've been more than 
 puzzled by Messages.properties in the past. I don't like to 
 be defeated by one little flat file, so I'm going to ask a 
 few more questions...
 
 Firstly, it looks like and I'm assuming you are on 1.5.1. Correct?
 
 The reason I asked if you had your Messages.properties in the 
 [dspace-source]/dspace/modules/jspui/src/main/resources/ 
 directory was that in your original email it was listed as 
 [Dspace-source]/modules/jspui/main/resources. So I'll just 
 get you to double check that directory for me.
 
 Also, I haven't tried the default release but I couldn't find 
 any mention of .war files in the install instructions. Maybe 
 you could try one of the alternative deployment methods (see 
 below). But first, can I get you to confirm that you have 
 followed each of these steps:
 
 i) cd [dspace-source]/dspace
 ii) mvn package
 iii) cd target/dspace-[version].dir
 iv) ant init_configs
 
 Having followed these procedures, can you then either:
 
 A) DEFINE A CONTEXT PATH IN TOMCAT FOR THE JSPUI
 
 Add the following to your [tomcat-home]/conf/server.xml, 
 within the Host element:
 
 
 !-- DEFINE A CONTEXT PATH FOR DSpace JSP User Interface  -- 
 Context path=/jspui
 docBase=[dspace-install-directory]\webapps\jspui debug=0
 reloadable=true cachingAllowed=false
 allowLinking=true/
 
 OR:
 
 B) COPY YOUR JSPUI WEBAPP TO TOMCAT'S WEBAPPS DIRECTORY
 
 cp -r  [dspace-install-directory]/webapps/jspui [tomcat-home]/webapps/
 
 
 AFAIK the default and source releases should behave the same 
 in terms of building and deployment, but someone else could 
 confirm or deny this?
 
 I look forward to your reply (or indeed anyone else's 

[Dspace-tech] [SPAM] Vacation reply

2009-03-26 Thread matthewjbills
Hi Friend,
How are you doing recently? I would like to introduce you a very good company which I know. Their website is www.myewell.com. They can offer you all kinds of
Electronic products like laptops, gps,TV LCD,cell phones,ps3,MP3/4, etcPlease take some time to have a check, There must have something you'd like to buy.Their contact email: myew...@vip.188.com 
Hope you have a good mood in shopping from their company!
Best Regards
Matthew!
--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech