[Dspace-tech] millions of records in solr dspace statistics
Hi, recently we've migrated our ETD repository to DSpace which was created in 2001. We've also migrated the apache_logs to solr, but althought we've refused a lot of logs which were detected as robots, there are still a lot of records: 514millions! ...the solr index is about 50Gb Tomcat couldn't open and read this huge index because the Java heap space, so we resized the ram of the host to 8gb and finally it could open it...but now the statistics are so slow. I've been searching through solr and lucene posts to optimize all of this without success. Someone has got a huge solr index or has some idea to improve this behaviour? Thanks in advance, Regards, Jesús -- ... __ / / Jesús Martín García C E / S / C A Tècnic de Projectes /__ / Centre de Serveis Científics i Acadèmics de Catalunya Gran Capità, 2-4 (Edifici Nexus) · 08034 Barcelona T. 93 551 6213 · F. 93 205 6979 · jmar...@cesca.cat ... -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Setting string-length for collection choosing in the submission process (xmlui)
Hi,
thanks Josefina for helping out fixing this problem instantly; it now
works well, as well as to Peter for noticing it as something to bring
forth through JIRA. I added some more input on the CSS part
(https://jira.duraspace.org/browse/DS-1044).
Regards
Jessica
--
Jessica Lindholm
Malmö högskola
Bibliotek och IT
Orkanenbiblioteket
205 06 Malmö
Malmö University
Library and IT Service
Orkanen Library
205 06 Malmö
Sweden
jessica.lindh...@mah.se
+46 (0)40 665 71 39
http://www.mah.se/bit
http://homeweb.mah.se/~bijeli/
http://www.linkedin.com/in/jessical
2011-09-30 kl. 00:25, skrev Peter Dietz pdiet...@gmail.com :
Hi Jessica,
I just noticed that our site has that issue as well. So.. I filed a
DSpace
bug, fixed it, and added a patch to Jira, complete with screenshots
of
before-and-after.
https://jira.duraspace.org/browse/DS-1044
I'll probably need some feedback from people on whether we should be
truncating the length to 50 characters or not. Either way, it
shouldn't be
Java limiting this information. XSL is capable of truncating at a
given
length. I've chosen not to limit at all, just have CSS keep things
looking
normal though. For the patch, cheers to Josi for pulling out the 50
char
limit. And thanks to Jessica for finding the bug/annoyance.
Hej hej,
Peter Dietz
On Thu, Sep 29, 2011 at 3:16 PM, Josefina Perez Alvarez
josi@gmail.comwrote:
*Hi *Jessica Lindholm,
We needed to do this change in our installation:
Edit
[dspace-src]/dspace-xmlui/dspace-xmlui-api/src/main/java/org/dspace/
app/xmlui/aspect/submission/submit/SelectCollectionStep.java
In public void addBody(Body body)
In
select.addOption(,T_collection_default);
for (Collection collection : collections)
{
String name = collection.getMetadata(name);
if (name.length() 50)
/** changed from 50 to 100 */
{
name = name.substring(0, 47) + ...;
/**
changed from 47 to 97 (minus 3 to include ...)*/
}
select.addOption(collection.getHandle(),name);
}
Button submit = list.addItem().addButton(submit);
submit.setValue(T_submit_next);
maven
ant
restart tomcat
Hope this help,
Josi Perez
2011/9/29 Jessica Lindholm jessica.lindh...@mah.se
Hello all,
this is a very specific question which answer I believe hide in one
of
the xsl:s.
When a user picks a collection in the submission process from the
dropdown list of all collections a string-length of max 50 is set
somewhere. I cannot find its whereabouts. Users end up trying to
distuingish their collection to submit to from drop down option
values
looking like this
div xmlns=http://di.tamu.edu/DRI/1.0/; class=ds-form-content
select
id=aspect_submission_submit_SelectCollectionStep_field_handle
class=ds-select-field name=handle title=Select the collection
you
wish to submit an item to.
option value=Select a collection.../option
option value=2043/6050Student Essays / Utbildningsvetenskap
med
inrik.../option
option value=2043/4488Student Essays / Utbildningsvetenskap
med
inrik.../option
option value=2043/7087Student Essays / Utbildningsvetenskap
med
inrik.../option
which is far from optimal.
I have looked in structural.xsl, [localtheme].xsl, dri2xhtml/*.xsl
without success. We have made adjustments of various max chars of
titles, filenames etc in the local theme, but not on collection
names in
drop-downs at submission.The width of the dropdown list have been
adjusted in the css to see if that would help, but it is quite
obvious a
string-length setting hiding somewhere. The collection names seem
to be
shortened only in this particular display.
We use DSpace 1.7.2 XMLUI and have built our own theme based on
Kubrick.xsl.
Anyone with ideas how to solve this, rather than shortening names
of
collections?
Kind regards
Jessica Lindholm
--
Jessica Lindholm
Malmö högskola
Bibliotek och IT
Orkanenbiblioteket
205 06 Malmö
Malmö University
Library and IT Service
Orkanen Library
205 06 Malmö
Sweden
jessica.lindh...@mah.se
+46 (0)40 665 71 39
http://www.mah.se/bit
http://homeweb.mah.se/~bijeli/
http://www.linkedin.com/in/jessical
-
-
All the data continuously generated in your IT infrastructure
contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and
makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Stats on 1.5.1, ERROR: invalid input syntax for type timestamp: 2007
Jose, Perfect, that was a big help. I'm not very familiar with DSpace's schema, but I was able to hack together some SQL to find all of our offending items: select text_value from metadatavalue where metadata_field_id=25 and item_id in (select item_id from metadatavalue where metadata_field_id=11 and text_value = '25/07/2005' or text_value= '13/02/2008'); Where 25/07/2005 and 13/02/2008 were commonly-occurring, incorrect values for the dc.date.accessioned field. I saw them frequently in the postgresql logs as causing the dspace-stat scripts to fail. The above SQL spits out a list of handle URLs, where our editors will be able to correct the data. For anyone who's also having this problem and trying to follow my SQL, 25 is the metadata_field_id for URI, and 11 is for the date.accessioned. Adios! Alan On Fri, Oct 7, 2011 at 6:40 PM, Blanco, Jose blan...@umich.edu wrote: Alan, I’d query metadtafieldregistry to find out the metadata_field_id for date.accissioned: dspace-prod= select metadata_field_id from metadatafieldregistry where element='date' and qualifier='accessioned'; metadata_field_id --- 11 ( so for us it happens to by 11 ) Then, once you have that number, do this query without specifying the datestyle. You might have to play around a bit with the query, maybe not include the text_value and see all the values to see if any one looks suspicious, or use the wild card %. dspace-prod= select text_value from metadatavalue where metadata_field_id =11 and text_value '2011-10-01' AND text_value '2011-10-31'; Hope this helps, Jose From: Alan Orth [mailto:alan.o...@gmail.com] Sent: Friday, October 07, 2011 11:16 AM To: dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Stats on 1.5.1, ERROR: invalid input syntax for type timestamp: 2007 Hi, We just noticed that our stats haven't run for the past month, so I went to run `/home/dspace/bin/dspace stat-monthly` manually. I'm getting a similar problem (but on DSpace 1.7.2 with Postgres 8.3): 2011-10-07 03:08:22 PDT ERROR: date/time field value out of range: 25/07/2005 2011-10-07 03:08:22 PDT HINT: Perhaps you need a different datestyle setting. 2011-10-07 03:08:22 PDT STATEMENT: SELECT COUNT(*) AS num FROM item WHERE in_archive = true AND withdrawn = false AND item_id IN ( SELECT item_id FROM metadatavalue WHERE metadata_field_id = ( SELECT metadata_field_id FROM metadatafieldregistry WHERE element = 'date' AND qualifier = 'accessioned') AND text_value::timestamp '2011-10-01'::timestamp AND text_value::timestamp '2011-10-31'::timestamp ) It's quite possible that a recent batch import of several thousand items had an incorrect date format... I'm not sure how to go about finding the offending item via SQL. Thanks, Alan On 09/15/2011 02:23 AM, Andrea Schweer wrote: Hi Evelio, On 15/09/11 01:23, Evelio Martínez wrote: When we invoke the following scripts [bin]# ./stat-initial [bin]# ./stat-monthly We have the same result Exception in thread main org.postgresql.util.PSQLException: ERROR: invalid input syntax for type timestamp: 2007 This is caused by an item for which date.accessioned is just 2007. You should be able to get the item id with something like the following query (just a slight modification of the one you posted): SELECT item_id FROM item WHERE in_archive = true AND withdrawn = false AND item_id IN (SELECT item_id FROM metadatavalue WHERE text_value = 2007 AND metadata_field_id = (SELECT metadata_field_id FROM metadatafieldregistry WHERE element = 'date' AND qualifier = 'accessioned')); DSpace expects the value of this field to be in the same format you got in your query for last_modified (eg 2008-12-15 09:08:10.66+01). Once you have fixed the date.accessioned value for this item, your statistics script should go through fine. cheers, Andrea -- Alan Orth alan.o...@gmail.com http://alaninkenya.org I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone. -Bjarne Stroustrup, inventor of C++ -- Alan Orth alan.o...@gmail.com http://alaninkenya.org http://mjanja.co.ke In heaven all the interesting people are missing. -Friedrich Nietzsche -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] CCCLicense Issue with german Localization
Hello, I have switched to Sun Java 1.6_26 now (which is essentially the same as the thing now called Oracle java) and nothing has changed. I think the workaround should be checked in to the main repository as long as the bug preventing properly localized messages to be used without compromising functionally is not found. My suggestion for a changed message text is as follows: message key=xmlui.Submission.submit.CCLicenseStep.submit_to_creative_commonsWeiter zur Auswahl der Lizenz auf der Website von Creative Commons./message Bye, Christian Am 03.10.2011 um 00:48 schrieb Christian Voelker: (…) The button label contains an Umlaut in the german version. This Umlaut is properly stored as UTF-8 in the messages_de.xml. Changing the Umlaut in the last Word auszuwählen to auszuwaehlen resolves the issue. Here comes the offending line without the change: message key=xmlui.Submission.submit.CCLicenseStep.submit_to_creative_commonsWeiter zur Creative Commons Seite, um eine Lizenz auszuwählen./message I guess it should work with the localized string as Claudia has entered it. Changing the label is only a workaround. This is the java version on my Debian server: $java -version java version 1.6.0_18 OpenJDK Runtime Environment (IcedTea6 1.8.7) (6b18-1.8.7-2~squeeze1) OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode) -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] XMLUI Mirage Theme Search Box Context not properly detected
Hello, in Mirage theme, the search box on the upper right hand contains a context radio button and is defined in lib/xsl/core/navigation.xsl. The correspoding code snippet follows below. It should make a difference whether you are in a Community or in a Collection and expose different labels on the radio button. The corresponding messages are as follows: message key=xmlui.dri2xhtml.structural.searchSearch DSpace/message message key=xmlui.dri2xhtml.structural.search-advancedAdvanced Search/message message key=xmlui.dri2xhtml.structural.search-in-communityThis Community/message message key=xmlui.dri2xhtml.structural.search-in-collectionThis Collection/message However, it does not work. You can verify the effect by looking at demo.dspace.org. I have the same here in my local 1.7.2, in either english oder localized version: http://demo.dspace.org/xmlui/handle/10673/6648 I dont really understand what is going wrong. I was just searching for an example to decide on the status of being logged in from within a .xsl file when I came across this. I was not able to fix it myself and cant provide a patch. The XSL looks fine for me, but I am a total beginner at XSL, started to modify a theme for the first time only yesterday. While reporting this issue I want to mention a whish. Splitting up the xmlui.dri2xhtml.structural.search in two separate messages could help to improve the interface. The current message should stay the same as now and be used only for the search box headline. The button label for sitewide search should use a new message which is more destinctive and read something like this I guess: message key=xmlui.dri2xhtml.structural.search-in-whole-siteComplete Repository/message Bye, Christian h1 id=ds-search-option-head class=ds-option-set-head i18n:textxmlui.dri2xhtml.structural.search/i18n:text /h1 (…) xsl:if test=/dri:document/dri:meta/dri:pageMeta/dri:metadata[@element='focus'][@qualifier='container'] label input id=ds-search-form-scope-all type=radio name=scope value= checked=checked/ i18n:textxmlui.dri2xhtml.structural.search/i18n:text /label br/ label input id=ds-search-form-scope-container type=radio name=scope xsl:attribute name=value xsl:value-of select=substring-after(/dri:document/dri:meta/dri:pageMeta/dri:metadata[@element='focus'][@qualifier='container'],':')/ /xsl:attribute /input xsl:choose xsl:when test=/dri:document/dri:meta/dri:pageMeta/dri:metadata[@element='focus'][@qualifier='containerType']/text() = 'type:community' i18n:textxmlui.dri2xhtml.structural.search-in-community/i18n:text /xsl:when xsl:otherwise i18n:textxmlui.dri2xhtml.structural.search-in-collection/i18n:text /xsl:otherwise /xsl:choose /label /xsl:if -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] XMLUI Mirage Theme Search Box Context not properly detected
Hello Christian, seems as if no element 'focus' with the qualifier 'containerType' is added to the pageMeta, so the check in navigation.xsl will result in collection. Hope that helps Claudia Jürgen Am 10.10.2011 14:58, schrieb Christian Voelker: Hello, in Mirage theme, the search box on the upper right hand contains a context radio button and is defined in lib/xsl/core/navigation.xsl. The correspoding code snippet follows below. It should make a difference whether you are in a Community or in a Collection and expose different labels on the radio button. The corresponding messages are as follows: message key=xmlui.dri2xhtml.structural.searchSearch DSpace/message message key=xmlui.dri2xhtml.structural.search-advancedAdvanced Search/message message key=xmlui.dri2xhtml.structural.search-in-communityThis Community/message message key=xmlui.dri2xhtml.structural.search-in-collectionThis Collection/message However, it does not work. You can verify the effect by looking at demo.dspace.org. I have the same here in my local 1.7.2, in either english oder localized version: http://demo.dspace.org/xmlui/handle/10673/6648 I dont really understand what is going wrong. I was just searching for an example to decide on the status of being logged in from within a .xsl file when I came across this. I was not able to fix it myself and cant provide a patch. The XSL looks fine for me, but I am a total beginner at XSL, started to modify a theme for the first time only yesterday. While reporting this issue I want to mention a whish. Splitting up the xmlui.dri2xhtml.structural.search in two separate messages could help to improve the interface. The current message should stay the same as now and be used only for the search box headline. The button label for sitewide search should use a new message which is more destinctive and read something like this I guess: message key=xmlui.dri2xhtml.structural.search-in-whole-siteComplete Repository/message Bye, Christian h1 id=ds-search-option-head class=ds-option-set-head i18n:textxmlui.dri2xhtml.structural.search/i18n:text /h1 (…) xsl:if test=/dri:document/dri:meta/dri:pageMeta/dri:metadata[@element='focus'][@qualifier='container'] label input id=ds-search-form-scope-all type=radio name=scope value= checked=checked/ i18n:textxmlui.dri2xhtml.structural.search/i18n:text /label br/ label input id=ds-search-form-scope-container type=radio name=scope xsl:attribute name=value xsl:value-of select=substring-after(/dri:document/dri:meta/dri:pageMeta/dri:metadata[@element='focus'][@qualifier='container'],':')/ /xsl:attribute /input xsl:choose xsl:when test=/dri:document/dri:meta/dri:pageMeta/dri:metadata[@element='focus'][@qualifier='containerType']/text() = 'type:community' i18n:textxmlui.dri2xhtml.structural.search-in-community/i18n:text /xsl:when xsl:otherwise i18n:textxmlui.dri2xhtml.structural.search-in-collection/i18n:text /xsl:otherwise /xsl:choose /label /xsl:if -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Claudia Juergen Universitaetsbibliothek Dortmund Eldorado 0231/755-4043 https://eldorado.tu-dortmund.de/ -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more.
Re: [Dspace-tech] Dspace 1.7.2 Indexing problem
After I upgrade, I always roun index-init ./dspace index-init Have you tried this? -Jose From: Bodnar Robert [mailto:bodnar_rob...@yahoo.com] Sent: Monday, October 10, 2011 2:11 AM To: dspace-tech@lists.sourceforge.net Subject: [Dspace-tech] Dspace 1.7.2 Indexing problem Hello! We still have the following problem with our DSpace 1.7.2 installation, does anyone have any clue what could the problem be: Hi All! I have an indexing problem, a different one then I have read on the list since now. We have recently upgraded our DSpace software from version 1.6.0 to 1.7.2. Everything seemed fine, until I tried to update the index. When I try running the index: ./dspace index-update I see the following: Started: 1314339018968 Ended: 1314339064644 Elapsed time: 45 secs (45676 msecs) The numers are changeing but the 45 secs are constant. Then it simply stops but I do not get back the bash (no command line). I can see nothing more. When I had run the index on 1.6.0, I saw the lines running. In the logs I found the following error: Error Null metadata value for item 13000, field: dc.subject Unfortunately in the beginning a lots of items were uploaded with metadatas missing. Thank you for any advice! B. Robert -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] dspace 1.7 webui.browse.index
hello, i have problems to configure the webui.browse.index in dspace-1.7 using xmlui. in special setting up the index display. the following browsindex should print out a full list. webui.browse.index.7 = identifierother:metadata:dc.identifier.other:date:full in the manual for version 1.7 in chapter 6.2.26.1. Defining the Indexes: Choose full or single. This refers to the way that the index will be displayed in the browse list- ing. Full will be the full item list as specified by webui.itemlist.columns ; single will be a single list of only the indexed term. the webui.itemlist.columns is set up also (but i believe this has no effect for the xmlui part). but i can see only the single column dc.identifier.other not the defined columns in the xmlui theme. the webui.browse.index.3 = title:item:title brings out a complete list of title, date, creator, etc. index has been new created with ./dspace index-init (tomcat restarted). has somebody an idea, hint ... best lars moeller -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] dspace 1.7 webui.browse.index
Hello Lars, you created a metadata index with webui.browse.index.7 = identifierother:metadata:... try to create an item index webui.browse.index.7 = identifierother:item:... Hope this helps Claudia Jürgen Am 10.10.2011 16:25, schrieb Lars Möller: hello, i have problems to configure the webui.browse.index in dspace-1.7 using xmlui. in special setting up theindex display. the following browsindex should print out a full list. webui.browse.index.7 = identifierother:metadata:dc.identifier.other:date:full in the manual for version 1.7 in chapter 6.2.26.1. Defining the Indexes: Choose full or single. This refers to the way that the index will be displayed in the browse list- ing. Full will be the full item list as specified by webui.itemlist.columns ; single will be a single list of only the indexed term. the webui.itemlist.columns is set up also (but i believe this has no effect for the xmlui part). but i can see only the single column dc.identifier.other not the defined columns in the xmlui theme. the webui.browse.index.3 = title:item:title brings out a complete list of title, date, creator, etc. index has been new created with ./dspace index-init (tomcat restarted). has somebody an idea, hint ... best lars moeller -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Claudia Juergen Universitaetsbibliothek Dortmund Eldorado 0231/755-4043 https://eldorado.tu-dortmund.de/ -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] dspace 1.7 webui.browse.index
hello claudia, thanks for the quick answer. but i get this error: Exception: Browse Index configuration is not valid: webui.browse.index.7 = identifierother:item:dc.identifier.other:date:full org.dspace.browse.BrowseException: Browse Index configuration is not valid: webui.browse.index.7 = identifierother:item:dc.identifier.other:date:full at org.dspace.browse.BrowseIndex.init(BrowseIndex.java:202) at org.dspace.browse.BrowseIndex.getBrowseIndices(BrowseIndex.java:682) at org.dspace.browse.IndexBrowse.init(IndexBrowse.java:123) at org.dspace.browse.IndexBrowse.main(IndexBrowse.java:626) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:183) best lars Am 10.10.11 17:06, schrieb Claudia Jürgen: Hello Lars, you created a metadata index with webui.browse.index.7 = identifierother:metadata:... try to create an item index webui.browse.index.7 = identifierother:item:... Hope this helps Claudia Jürgen Am 10.10.2011 16:25, schrieb Lars Möller: hello, i have problems to configure the webui.browse.index in dspace-1.7 using xmlui. in special setting up theindex display. the following browsindex should print out a full list. webui.browse.index.7 = identifierother:metadata:dc.identifier.other:date:full in the manual for version 1.7 in chapter 6.2.26.1. Defining the Indexes: Choose full or single. This refers to the way that the index will be displayed in the browse list- ing. Full will be the full item list as specified by webui.itemlist.columns ; single will be a single list of only the indexed term. the webui.itemlist.columns is set up also (but i believe this has no effect for the xmlui part). but i can see only the single column dc.identifier.other not the defined columns in the xmlui theme. the webui.browse.index.3 = title:item:title brings out a complete list of title, date, creator, etc. index has been new created with ./dspace index-init (tomcat restarted). has somebody an idea, hint ... best lars moeller -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] dspace 1.7 webui.browse.index
On Mon, Oct 10, 2011 at 17:23, Lars Möller moel...@basis5.de wrote: but i get this error: Exception: Browse Index configuration is not valid: webui.browse.index.7 = identifierother:item:dc.identifier.other:date:full Hi Lars, I would check 2 things first: 1) after you changed indexes in dspace.cfg, did you run index-init? 2) in dspace.cfg, did you happen to leave out a number? e.g. if you want only 2 indexes, you cannot number them this way: webui.browse.index.1 webui.browse.index.3 you have to number them sequentioally, i.e.: webui.browse.index.1 webui.browse.index.2 Hope that helps. Regards, ~~helix84 -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] dspace 1.7 webui.browse.index
hello helix, 1) in my first post, i wrote, index has been new created with ./dspace index-init (tomcat restarted). 2) no numbers leaved out. 1 to 7 exists. it isn't the problem, that the index doesn't work. only the index display-option full doesn't work. best lars Am 10.10.11 17:39, schrieb helix84: On Mon, Oct 10, 2011 at 17:23, Lars Möllermoel...@basis5.de wrote: but i get this error: Exception: Browse Index configuration is not valid: webui.browse.index.7 = identifierother:item:dc.identifier.other:date:full Hi Lars, I would check 2 things first: 1) after you changed indexes in dspace.cfg, did you run index-init? 2) in dspace.cfg, did you happen to leave out a number? e.g. if you want only 2 indexes, you cannot number them this way: webui.browse.index.1 webui.browse.index.3 you have to number them sequentioally, i.e.: webui.browse.index.1 webui.browse.index.2 Hope that helps. Regards, ~~helix84 -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] dspace 1.7 webui.browse.index
Hello Lars, for an item index it is just: webui.browse.index.n = index name : item : sort option name : (asc | desc) with the correpsonding sort option in the form webui.itemlist.sort-option.n = option name :schema prefix.element[.qualifier|.*] : (date | text | ...) : (show | hide) An item index is a full index. So with your example it would be webui.browse.index.7 =identifierother:item:identifierother webui.itemlist.sort-option.4 = identifierother:dc.identifier.other:date Hope this helps Claudia Jürgen hello claudia, thanks for the quick answer. but i get this error: Exception: Browse Index configuration is not valid: webui.browse.index.7 = identifierother:item:dc.identifier.other:date:full org.dspace.browse.BrowseException: Browse Index configuration is not valid: webui.browse.index.7 = identifierother:item:dc.identifier.other:date:full at org.dspace.browse.BrowseIndex.init(BrowseIndex.java:202) at org.dspace.browse.BrowseIndex.getBrowseIndices(BrowseIndex.java:682) at org.dspace.browse.IndexBrowse.init(IndexBrowse.java:123) at org.dspace.browse.IndexBrowse.main(IndexBrowse.java:626) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:183) best lars Am 10.10.11 17:06, schrieb Claudia Jürgen: Hello Lars, you created a metadata index with webui.browse.index.7 = identifierother:metadata:... try to create an item index webui.browse.index.7 = identifierother:item:... Hope this helps Claudia Jürgen Am 10.10.2011 16:25, schrieb Lars Möller: hello, i have problems to configure the webui.browse.index in dspace-1.7 using xmlui. in special setting up theindex display. the following browsindex should print out a full list. webui.browse.index.7 = identifierother:metadata:dc.identifier.other:date:full in the manual for version 1.7 in chapter 6.2.26.1. Defining the Indexes: Choose full or single. This refers to the way that the index will be displayed in the browse list- ing. Full will be the full item list as specified by webui.itemlist.columns ; single will be a single list of only the indexed term. the webui.itemlist.columns is set up also (but i believe this has no effect for the xmlui part). but i can see only the single column dc.identifier.other not the defined columns in the xmlui theme. the webui.browse.index.3 = title:item:title brings out a complete list of title, date, creator, etc. index has been new created with ./dspace index-init (tomcat restarted). has somebody an idea, hint ... best lars moeller -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech Mit freundlichen Gruessen Claudia Juergen Universitaetsbibliothek Dortmund Eldorado 0231/755-4043 https://eldorado.tu-dortmund.de/ Tel.: 0049-231-755-4043 -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Dspace 1.7.2 Indexing problem
Thank you for your answer Jose! Yes, I tried that, but the result is the same: Started: Ended: Elapsed time: 70 secs (see attachment) But nothing is done... Thank you! B. Robert Subject: RE: [Dspace-tech] Dspace 1.7.2 Indexing problem After I upgrade, I always roun index-init ./dspace index-init Have you tried this? -Joseattachment: dspace-index.JPG-- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
