Hi Pennington
Usually when I get error 500 like yours I immediately export java_home
variable like :
Put the path of your jdk and the version of that jdk as well
# export JAVA_HOME=/usr/jdk/jdk1.5.0_12
And lastly restart your tomcat
Hope that help
Regards,
Lewatle
-Original
On 31 March 2010 06:14, MOHIT SHARMA mohit7...@gmail.com wrote:
After doing this command :sudo ant fresh_install
i have used these commands
1:) /dspace/bin/create-administrator
2)sudo gedit /etc/default/tomcat6
--TOMCAT6_USER=dspace
--TOMCAT6_SECURITY=no
3) sudo gedit
On 31 March 2010 10:18, Sean Carte sean.ca...@gmail.com wrote:
On 31 March 2010 06:14, MOHIT SHARMA mohit7...@gmail.com wrote:
After doing this command :sudo ant fresh_install
i have used these commands
1:) /dspace/bin/create-administrator
2)sudo gedit /etc/default/tomcat6
On 30.03.10 18:55, Peter Dietz wrote:
I encounter this problem as well. On my development desktop Ubuntu
9.10 spikes for seemingly indefinite periods of time. I tolerate the
100% spikes because since I'm at the machine, its quick enough to kill
process and restart, and all I want to do is
On 31 March 2010 10:30, Hilton Gibson hilton.gib...@gmail.com wrote:
You never customise the maintainers version.
I am duly chastised!
You make very good points, thanks Hilton.
Sean
--
Sean Carte
esAL Library Systems Manager
+27 72 898 8775
+27 31 373 2490
fax: 0866741254
Hi folks,
I am from Ghana and i have a problem of which i need some help. I´ve
installed DSpace on Fedora on a test machine. Everything works fine. I can
access port 80 of the DSPACE computer on other clients on the LAN but i
can´t access port 8080 let alone the Dspace application. PLease i need
Hi all,
I am testing DSpace 1.6 before we migrate to it. I believe I have the
dspace.cfg set up correctly, and I have added dc.embargo.terms and
dc.embargo.liftdate to my metadata registry.
However, nothing shows up in the submission workflow in any of my xmlui themes,
or in jspui. Are there
Hi Jason:
One thought: have you added those fields to your input-forms.xml? In other
respects, the embargo fields behave just like any other metadata, and can be
added to the default set - or any collection-specifc set - of metadata fields
used in web submission. The tech doc has instructions
Richard,
That's helpful. So just to verify, it is necessary to add those items to the
input-forms.xml in order to get them to show up in the submission process?
Embargoes don't just work (ie. show up in the submission process) out of the
box? I am fine with making the changes, but I just want
Hello Jason,
the embargo only works during the submission process not if you edit add
the metadata to an already archived item.
It will not make the item invisible but restrict the access to the
bitstreams belonging to an item, set a lift date and change the date
available. When the
Thanks for the advice, but those steps didn't make any difference in the
outcome.
It is just really odd. This request fails with a 500 error:
http://dlynx.rhodes.edu/oai/request?verb=ListIdentifiersmetadataPrefix=oai_dc
But this request gives a response, which is the correct Bad Argument
Jason:
Yes, that's right - input-forms must be updated. But I regard it on balance
an advantage that the embargo system 'inherits' all the configurability of
standard DSpace metadata -
not just in submission, but indexing, display and more (so you could, e.g. do
fielded search on embargo
Hi
I think your must check if your have firewall running and if the port 8080
is blocked,
another point to check is the configuration of your tomcat?? o resin? what
server are you using??
Im using tomcat, under directory conf exists server.xml file on this file
exist a block like this:
!--
Hi Kumara,
There should be nothing to do with proxy.
The setting of firewall in OSX is in
System Preferences - sharing
There you are going to add a new exception to the firewall. The effect
is to open a new hole in your wall, allowing others to connect to your
tomcat at port 8080.
Hope that
Hi All
With respect to older items already submitted, can one impose an embargo on
them without a migration and re-submission ?
Cheers
hg.
On 31 March 2010 16:21, Richard Rodgers rrodg...@mit.edu wrote:
Hi Jason:
One thought: have you added those fields to your input-forms.xml? In other
That makes sense. The only thing I don't understand is how exactly the liftdate
is computed. Is that something that happens automatically, or do I need to
configure that?
Jason Fowler, CA, MSLS
From: Claudia Juergen [claudia.juer...@ub.tu-dortmund.de]
I'm wondering if someone could contact me off-list to discuss getting my DSpace
repository off the ground. Here is what I am dealing with, in the hopes that
someone out there has some experience with this set of circumstances and can
give me a few pointers here and there.
I have a Windows
Hi Hilton:
Not really - the assumption of the embargo system is that once content has been
made generally available, it no longer makes sense to embargo it (since
embargo traditionally means withholding exposure until some future time, then
exposing it). So it really isn't the same as access
On 31 March 2010 20:35, Richard Rodgers rrodg...@mit.edu wrote:
Hi Hilton:
Not really - the assumption of the embargo system is that once content has
been made generally available, it no longer makes sense to embargo it
(since embargo traditionally means withholding exposure until some
Hi Jason:
I can see that this might be confusing, so let me try to explain a little more
clearly.
At the most basic level, the field containing the 'terms' is where a submitter
specifies how the embargo should work for that item.
At the time of installation into the archive (i.e. when it
Hello Peter and Mark,
I'm not quite convinced yet that this consolidation of API's was the
best / final destination for the Syndication work in DSpace.
Consolidation sometimes just creates bottlenecks and forces an api
in a situation that may still be evolving.
This is a bit more forward
Hi Hilton:
I'm not sure I precisely follow option b (especially step 9 - not sure what
'read access permission problems' are), but something along these lines ought
to work.
Specifically, if by some means you remove read policies on the bitstreams, and
make sure there is a valid date in the
Hi Stacy,
You might be suffering from this issue:
- http://jira.dspace.org/jira/browse/DS-212
You could test this theory by seeing if you've got
'harvest.includerestricted.oai' set to 'false'. If so, set it to 'true' and try
again. If this fixes the problem, you could try enabling it again,
Hi all,
DSpace 1.6.1 development has started!
With the release of DSpace 1.6, the DSpace developer community is now focusing
attention on the next major release, DSpace 1.7, and on DSpace 1.6.1, which
will be a minor release to fix any bugs found in DSpace 1.6.0.
I've volunteered to
Hello everbody,
every now and then somebody rises questions regarding clock speed and disk
space and the kind on this list during planning for a new project or when going
from development to production. I just skimmed through the archived messages of
the last year and found several requests
Hi member
I'm using DSpace 1.3.2 which is not yet supported the script
/update-handle-prefix/ on production. So I copied and pasted the script from
1.4.1. The script can be executed. But it is stopped after it has updated
12,004 records from more than hundred thousands records. It
26 matches
Mail list logo
