As its not in the maven central repository. We would need to release
it ourselves under org.dspace.dependencies or see if someone else can
push out a new version of tm-extractors for maven central.
To release into our repository, we just need to author a pom.xml file
for the tm-extractors and
DSpace scalability issues report, per wiki template:
1. dsp...@cambridge, The University of Cambridge, UK.
Technical contacts: Tom De Mulder, td...@cam.ac.uk (systems manager)
Simon Brown st...@cam.ac.uk (DSpace developer)
2. a. DSpace version 1.6.2 with extensive local patches, using
(Apologies for replying to my own email.)
One metric the template didn't ask for, I just noticed, is the number of hits
per second.
We average about 2 hits per second, which is very low, even if most of these
hits are actual page views, not just layout elements. However, both our webapp
and
I'm really having a hard time with this. In order to understand the code a bit
more, I'm trying to find the line in the themes dir that would put the message
Find Itme in the url:
http://dspace-test-area/admin/item
So I looked at
http://dspace-test-area/DRI/admin/item
which contains:
The recordings of 2 recent webinars are now available on the duraspace.org
website: http://duraspace.org/resources.php. Please see the full descriptions
below.
Valorie Hollister
Director of Community Development, DSpace Project
DuraSpace
vhollis...@duraspace.org
DSpace 1.6 Usage
Hi Jose,
Text labels are not set in the XSLT, but rather are defined in the
i18n/messages.xml file.
--Dave
==
David Walker
Library Web Services Manager
California State University
http://xerxes.calstate.edu
From: Blanco, Jose
Hi Dave,
Meant to get back to this discussion -- but, as you can see, it has
taken me a while to do so :)
On 10/1/2010 4:22 PM, Walker, David wrote:
If the goal here is to add an input button to the interface -- on the
'confirm item' page, let's say -- I think it would be *significantly*
But how does it get from that file to the page?
-Original Message-
From: Walker, David [mailto:dwal...@calstate.edu]
Sent: Thursday, October 07, 2010 10:58 AM
To: Blanco, Jose; Tim Donohue
Cc: dspace-tech@lists.sourceforge.net
Subject: RE: [Dspace-tech] manikin question
Hi Jose,
Text
Hi, Jose:
would put the message Find Item in the url
I'm guessing you actually mean in the title of the page?
I believe your answer is somewhere in this file:
dspace-src/dspace-xmlui/dspace-xmlui-api/src/main/java/org/dspace/app/xmlui/aspect/administrative/item/
FindItemForm.java
Two
Hi Tom,
First off, thanks for sharing your details, and some more specifics
about the memory issues you are seeing. Much appreciated.
I've got a few followup questions, if you or Simon don't mind answering
them. Just trying to get a better understanding of where the core
problem(s) reside,
Yes, I see how it gets set here:
findItem.setHead(T_head1);
I think what is causing me so much trouble is my lack of knowledge of DRI and
cocoon.
I was expecting the DRI object to be completely converted to HTML by the
themes, but that is not the case, right? Some tags in the
Hardy,
I cannot recall seeing any diagrams which describe the flow of specific
aspects in Manakin. But, it's possible Scott or others on this list may
know of some?
The best diagrams I know of are those from Scott's slide stack (which
you already linked to). Those are a great overview of
Obviously, as we both know, a button won't do anything
unless there's some server-side code which understands
how to process that request.
Oh, yes, of course.
Obviously, there needs to be Java code that can processes the incoming request
and do something about it: Getting data from the
Well, one thing which occurs to me is that dri:field type='button'/
should instead be something like dri:action/ and let the Theme
figure out whether it wants to lay out a button (or anything else)
which links to the action. These button fields are really just
abstract handles for things the user
The notes from the DGOC October 5 meeting are available at:
https://wiki.duraspace.org/display/DSPACE/DGOC+October+5%2C+2010. The next
meeting will be on November 2. Please see my previous post below for additional
information. Feel free to contact me with any questions or feedback.
Valorie
We still need some way to build a bag of structured,
labeled data and action handles, so that when a
Theme reaches into the bag it can know what to grab
Yes, right. And this is really easy to do:
labeldata/label
It'll probably need to be more complex than that, of course -- but not
Dear all...
I am trying to customize de DSpace 1.6.2. I could change the metadata and
change the input-form to use the new metadata added too.
In the input-form, there are lots of types-input. I´ve used the dropdown as
type-input, but i would like to add a textfield with a button to possibity
I built 1.6.2 with |embargo.field.terms = SCHEMA.ELEMENT.QUALIFIER and
||embargo.field.lift = SCHEMA.ELEMENT.QUALIFIER commented out thinking
that would disable embargo. When I try to enter an item I get |
java.lang.IllegalStateException: Missing one or more of the required
DSpace
Hi Tom,
Thanks for this extra level of information - it will really help.
A few random questions come to mind:
d. Separate servers for webapp, DB, storage and ancillary functions
Webapp/DB servers are HT 8-core Intel servers running Ubuntu Linux
with 16GB of memory and fast local
Hi Gaetano,
Could you check the value of dspace.baseUrl and dspace.url in
[dspace]/config/dspace.cfg?
Going by the information you've given, here are the recommended values for
your DSpace instance:
dspace.hostname = elea.unisa.it
dspace.baseUrl = http://${dspace.hostname}:8080
dspace.url =
David et al.
I have been following this discussion and trying to determine an
appropriate point of entry. So lets dive in...
In @mire, we are highly invested in the DRI solution at this time,
proposing a major change in DRI for DSpace 1.7 is not something that
@mire will support due to the
21 matches
Mail list logo
