[Dspace-devel] [DuraSpace JIRA] Created: (DS-892) Performance issues in update enabling the StatisticsLoggingConsumer
Performance issues in update enabling the StatisticsLoggingConsumer --- Key: DS-892 URL: https://jira.duraspace.org/browse/DS-892 Project: DSpace Issue Type: Bug Components: Solr Affects Versions: 1.7.1, 1.7.0, 1.6.2, 1.6.1, 1.6.0 Reporter: Andrea Bollini Priority: Critical We have found that enabling the StatisticsLoggingConsumer to keep statistics data up-to-date after item changes (metadata edit or collection moving/mapping) the item update operations become slowly and the system unusable. NOTE: the StatisticsLoggingConsumer is NOT enabled out-of-box in the dspace.cfg this imply that your statistics data could be incongruous (item access assigned to incorrect communities/collections) We noticed problems when there are large amount of statistics data (> 20M records), for small repository (< 1M statistics record) the overhead is acceptable. Finally, after the introduction of the autocommit patch, the StatisticsLoggingConsumer is not more able to assure the data consistence because the statistics data collected between two auto-commit are not processed by the class. Our current idea is to discard the consumer approach in favour to implement a batch tools to periodically analyze the statistics data and fix it as appropriate. This issue is a placeholder for such feature and discussion around it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1217) DSpace Discovery for JSPUI
Andrea Bollini created DS-1217: -- Summary: DSpace Discovery for JSPUI Key: DS-1217 URL: https://jira.duraspace.org/browse/DS-1217 Project: DSpace Issue Type: New Feature Components: Discovery, JSPUI Reporter: Andrea Bollini Assignee: Andrea Bollini Priority: Major Fix For: 3.0 Porting of the discovery features (SOLR Search) to the JSPUI. This contribution is supported by the University of Hong Kong that has adopted the first version of this code since July 2010 Software development by the CILEA SURplus Team (http://www.cilea.it) Example: http://hub.hku.hk/simple-search?sort_by=1&query=&submit=search -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1218) BrowseDAO based on discovery
Andrea Bollini created DS-1218: -- Summary: BrowseDAO based on discovery Key: DS-1218 URL: https://jira.duraspace.org/browse/DS-1218 Project: DSpace Issue Type: New Feature Components: Discovery Reporter: Andrea Bollini Assignee: Andrea Bollini Priority: Major Fix For: 3.0 Implementation of the BrowseDAO classes to use the data in the SOLR search core (dspace-discovery) instead of Database query. This contribution is supported by the University of Hong Kong that has adopted the first version of this code since July 2010 Software development by the CILEA SURplus Team (http://www.cilea.it) Example: http://hub.hku.hk/browse?type=title -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1223) Display frequencies of items in single browsing for selected indices
[ https://jira.duraspace.org/browse/DS-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25691#comment-25691 ] Andrea Bollini commented on DS-1223: I'm concerned about the performance of this enhancement. The frequencies are calculated with a separate query for any terms and this approach simply not scale. It could be very useful if you can extends the core classes to collect these data directly with the query that retrieve the terms (I know, it is not a trivial task as you need to go deeply in the BrowseDAO classes) > Display frequencies of items in single browsing for selected indices > > > Key: DS-1223 > URL: https://jira.duraspace.org/browse/DS-1223 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Affects Versions: 1.8.2 >Reporter: Christina Paschou > Labels: has-patch, has-pull-request > Attachments: browse_frequencies.diff, README.txt > > > DSpace provides by default two types of browsing, naming them single browsing > and full browsing according to the corresponding names of the .jsp files that > are responsible for handling each request (single.jsp & full.jsp). > Each type of browsing is defined accordingly and configured in different way > in the configuration file dspace.cfg. > The proposed improvement is applied for the case of browsing by a unique > index of metadata values from the item (single browsing). In this case, the > user can define for each metadata browse index whether he wishes to add next > to its various metadata values the frequencies of items that are included. > The configuration takes place in the dspace.cfg. > Examples: > http://phdtheses.ekt.gr/eadd/browse?type=subject > http://phdtheses.ekt.gr/eadd/browse?type=country > http://phdtheses.ekt.gr/eadd/browse?type=language > Attached you can find the patch file and a readme file with details about tha > configuration that is needed to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1217) DSpace Discovery for JSPUI
[ https://jira.duraspace.org/browse/DS-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1217: --- Labels: has-pull-request (was: ) > DSpace Discovery for JSPUI > -- > > Key: DS-1217 > URL: https://jira.duraspace.org/browse/DS-1217 > Project: DSpace > Issue Type: New Feature > Components: Discovery, JSPUI >Reporter: Andrea Bollini >Assignee: Andrea Bollini >Priority: Major > Labels: has-pull-request > Fix For: 3.0 > > > Porting of the discovery features (SOLR Search) to the JSPUI. > This contribution is supported by the University of Hong Kong that has > adopted the first version of this code since July 2010 > Software development by the CILEA SURplus Team (http://www.cilea.it) > Example: http://hub.hku.hk/simple-search?sort_by=1&query=&submit=search -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1217) DSpace Discovery for JSPUI
[ https://jira.duraspace.org/browse/DS-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25732#comment-25732 ] Andrea Bollini commented on DS-1217: Pull request #60 https://github.com/DSpace/DSpace/pull/60 > DSpace Discovery for JSPUI > -- > > Key: DS-1217 > URL: https://jira.duraspace.org/browse/DS-1217 > Project: DSpace > Issue Type: New Feature > Components: Discovery, JSPUI >Reporter: Andrea Bollini >Assignee: Andrea Bollini >Priority: Major > Labels: has-pull-request > Fix For: 3.0 > > > Porting of the discovery features (SOLR Search) to the JSPUI. > This contribution is supported by the University of Hong Kong that has > adopted the first version of this code since July 2010 > Software development by the CILEA SURplus Team (http://www.cilea.it) > Example: http://hub.hku.hk/simple-search?sort_by=1&query=&submit=search -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1218) BrowseDAO based on discovery
[ https://jira.duraspace.org/browse/DS-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1218: --- Status: Open (was: Received) > BrowseDAO based on discovery > > > Key: DS-1218 > URL: https://jira.duraspace.org/browse/DS-1218 > Project: DSpace > Issue Type: New Feature > Components: Discovery >Reporter: Andrea Bollini >Assignee: Andrea Bollini >Priority: Major > Fix For: 3.0 > > > Implementation of the BrowseDAO classes to use the data in the SOLR search > core (dspace-discovery) instead of Database query. > This contribution is supported by the University of Hong Kong that has > adopted the first version of this code since July 2010 > Software development by the CILEA SURplus Team (http://www.cilea.it) > Example: http://hub.hku.hk/browse?type=title -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1218) BrowseDAO based on discovery
[ https://jira.duraspace.org/browse/DS-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1218: --- Labels: has-pull-request (was: ) > BrowseDAO based on discovery > > > Key: DS-1218 > URL: https://jira.duraspace.org/browse/DS-1218 > Project: DSpace > Issue Type: New Feature > Components: Discovery >Reporter: Andrea Bollini >Assignee: Andrea Bollini >Priority: Major > Labels: has-pull-request > Fix For: 3.0 > > > Implementation of the BrowseDAO classes to use the data in the SOLR search > core (dspace-discovery) instead of Database query. > This contribution is supported by the University of Hong Kong that has > adopted the first version of this code since July 2010 > Software development by the CILEA SURplus Team (http://www.cilea.it) > Example: http://hub.hku.hk/browse?type=title -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1218) BrowseDAO based on discovery
[ https://jira.duraspace.org/browse/DS-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25811#comment-25811 ] Andrea Bollini commented on DS-1218: Pull request: https://github.com/DSpace/DSpace/pull/67 > BrowseDAO based on discovery > > > Key: DS-1218 > URL: https://jira.duraspace.org/browse/DS-1218 > Project: DSpace > Issue Type: New Feature > Components: Discovery >Reporter: Andrea Bollini >Assignee: Andrea Bollini >Priority: Major > Labels: has-pull-request > Fix For: 3.0 > > > Implementation of the BrowseDAO classes to use the data in the SOLR search > core (dspace-discovery) instead of Database query. > This contribution is supported by the University of Hong Kong that has > adopted the first version of this code since July 2010 > Software development by the CILEA SURplus Team (http://www.cilea.it) > Example: http://hub.hku.hk/browse?type=title -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1252) (JSP)UI Import from bibliographics database/formats
Andrea Bollini created DS-1252: -- Summary: (JSP)UI Import from bibliographics database/formats Key: DS-1252 URL: https://jira.duraspace.org/browse/DS-1252 Project: DSpace Issue Type: New Feature Components: DSpace API, JSPUI Reporter: Andrea Bollini Priority: Major This contribution add to the DSpace the ability to import from the major bibliographic database both online than local (file based). Out-of-box it provides plugins to import from: - DOI via crossref API - PubMedID via webservices - ArXiv - local BibTeX files Support for additional providers can be easily implemented, the import is done via UI (currently only the JSPUI is supported but extension to XMLUI should be an easy task for any XMLUI experts). The feature can be turned on/off in configuration, the available plugins are also configurated via dspace.cfg. Mapping from the import format (CrossRef, PubMed, etc.) to your local DSpace metadata is done in external properties files in config/crosswalk (standard mapping is provided). In mapping files you can define different mapping rule basing on the destination collection (dspace form name) and origin "type" (for example in bibtex you have: @chapter, @book, etc.) Additional hacks for alter the imported values after the initial import or add other values automatically are provided (see the SanitezeImportedMetadata and the EnhanceImportedMetadata interfaces). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1252) (JSP)UI Import from bibliographics database/formats
[ https://jira.duraspace.org/browse/DS-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1252: --- Labels: has-pull-request (was: ) pull request: https://github.com/DSpace/DSpace/pull/78 > (JSP)UI Import from bibliographics database/formats > --- > > Key: DS-1252 > URL: https://jira.duraspace.org/browse/DS-1252 > Project: DSpace > Issue Type: New Feature > Components: DSpace API, JSPUI >Reporter: Andrea Bollini >Priority: Major > Labels: has-pull-request > > This contribution add to the DSpace the ability to import from the major > bibliographic database both online than local (file based). > Out-of-box it provides plugins to import from: > - DOI via crossref API > - PubMedID via webservices > - ArXiv > - local BibTeX files > Support for additional providers can be easily implemented, the import is > done via UI (currently only the JSPUI is supported but extension to XMLUI > should be an easy task for any XMLUI experts). > The feature can be turned on/off in configuration, the available plugins are > also configurated via dspace.cfg. > Mapping from the import format (CrossRef, PubMed, etc.) to your local DSpace > metadata is done in external properties files in config/crosswalk (standard > mapping is provided). > In mapping files you can define different mapping rule basing on the > destination collection (dspace form name) and origin "type" (for example in > bibtex you have: @chapter, @book, etc.) > Additional hacks for alter the imported values after the initial import or > add other values automatically are provided (see the SanitezeImportedMetadata > and the EnhanceImportedMetadata interfaces). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1226) Batch import from basic bibliographic formats (Endnote, BibTex, RIS, TSV, CSV)
[ https://jira.duraspace.org/browse/DS-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25944#comment-25944 ] Andrea Bollini commented on DS-1226: I have linked this issue to a new one (DS-1252) that I have just created to share a contribution from CILEA that allow import from bibliographic online database (arXiv, Crossref, PubMed) and bibliographic formats (BibTeX, ISI Plain text). As the deadline for 3.0 contribution is expired I don't feel that the new issue could/should be take in consideration but I hope that anyone involved in the review of this contribution can benefit to compare the two different approaches (that could be also merged in some point in future). The main differences are: - the "framework" is part of the code released to DSpace and not an external library (not necessary a good thing ;-) ) - the import is done via UI from the single user in her workspace so that the item could be completed/modified using the submission screens - we are using a different bibtex java parser, I have not a strong opinion about it I can only say that we are using it since 1 year and we haven't find any unparserable valid bibtex file. The bibtex java library as a GPL license and is hosted here: http://code.google.com/p/javabib/source/browse/#svn%2Ftrunk%2Freleases%2F20040801 > Batch import from basic bibliographic formats (Endnote, BibTex, RIS, TSV, CSV) > -- > > Key: DS-1226 > URL: https://jira.duraspace.org/browse/DS-1226 > Project: DSpace > Issue Type: New Feature > Components: DSpace API >Reporter: Kostas Stamatis > Labels: has-patch, has-pull-request, import > Attachments: biblio-transformation-engine-0.8.jar, import-patch.diff, > jbibtex-r45.jar, README.txt > > > This proposed extension (implemented by National Documentation Centre/EKT - > http://www.ekt.gr) allows the batch import of metadata (and/or bitstreams) to > DSpace using the import script and the Biblio-Transformation-Engine tool. The > input format can be any bibliographic format (the specific patch includes > support for Endnote, RIS, BibTex, TSV and CSV formats). > The biblio transformation engine > (http://code.google.com/p/biblio-transformation-engine/) is an open source > java framework developed by the Hellenic National Documentation Centre (EKT, > www.ekt.gr) and consists of programmatic APIs for filtering and modifying > records that are retrieved from various types of data sources (eg. databases, > files, legacy data sources) as well as for outputing them in appropriate > standards formats (eg. database files, txt, xml, Excel). The framework > includes independent abstract modules that are executed seperately, offering > in many cases alternative choices to the user depending of the input data > set, the transformation workflow that needs to be executed and the output > format that needs to be generated. > Thus, the attached patch, adds support for utilizing the > Biblio-Transformation-Engine in the DSpace batch import procedure where the > user only needs to specify the mapping between the input metadata and DSpace > metadata. Default mapping are also provided for the default DSpace Dublin > Core metadata schema. > USEFULNESS > - > Suppose a researcher of your institute provides you with a file with his/her > publications that you need to import in the repository. Supposing that the > format of the file is one the following: CSV, TSV, Endnote, BibTex, RIS > (formats that are commonly used for bibliographic metadata) using only one > command you can import all the records to the DSpace repository while in > parallel, configuration files apply in order to control which metadata is > imported and in which DC (or any other schema of the DSpace repository) field > it maps. > For those who know well the use of the Biblio-Transformation-Engine, this > extension is powerful given that they can write their own DataLoaders in > order to support more input formats. Filtering of records as well as > modifying the metadata is also possible with very little effort (using Biblio > transformation engine's filters and modifiers). The same applies for the > addition of bitstreams in the records. > CONFIGURATION FILES > --- > Since Bibilio-transformation-Engine supports Spring, the only configurations > that the user must work with are the Spring XML files for the Dependency > Injection. These files are located within "config" directory and the user can > specify in them the mapping between input metadata and DSpace Dublin Core > schema (or any other schema users have in their repository) > EXTERNAL LIBRARIES > --- > This extension makes use of t
[Dspace-devel] [DuraSpace JIRA] (DS-1252) (JSP)UI Import from bibliographics database/formats
[ https://jira.duraspace.org/browse/DS-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1252: --- Description: This contribution add to the DSpace the ability to import from the major bibliographic database both online than local (file based). Out-of-box it provides plugins to import from: - DOI via crossref API - PubMedID via webservices - ArXiv - local BibTeX files - local files in ISI Plain text format Support for additional providers can be easily implemented, the import is done via UI (currently only the JSPUI is supported but extension to XMLUI should be an easy task for any XMLUI experts). The feature can be turned on/off in configuration, the available plugins are also configurated via dspace.cfg. Mapping from the import format (CrossRef, PubMed, etc.) to your local DSpace metadata is done in external properties files in config/crosswalk (standard mapping is provided). In mapping files you can define different mapping rule basing on the destination collection (dspace form name) and origin "type" (for example in bibtex you have: @chapter, @book, etc.) Additional hacks for alter the imported values after the initial import or add other values automatically are provided (see the SanitezeImportedMetadata and the EnhanceImportedMetadata interfaces). was: This contribution add to the DSpace the ability to import from the major bibliographic database both online than local (file based). Out-of-box it provides plugins to import from: - DOI via crossref API - PubMedID via webservices - ArXiv - local BibTeX files Support for additional providers can be easily implemented, the import is done via UI (currently only the JSPUI is supported but extension to XMLUI should be an easy task for any XMLUI experts). The feature can be turned on/off in configuration, the available plugins are also configurated via dspace.cfg. Mapping from the import format (CrossRef, PubMed, etc.) to your local DSpace metadata is done in external properties files in config/crosswalk (standard mapping is provided). In mapping files you can define different mapping rule basing on the destination collection (dspace form name) and origin "type" (for example in bibtex you have: @chapter, @book, etc.) Additional hacks for alter the imported values after the initial import or add other values automatically are provided (see the SanitezeImportedMetadata and the EnhanceImportedMetadata interfaces). > (JSP)UI Import from bibliographics database/formats > --- > > Key: DS-1252 > URL: https://jira.duraspace.org/browse/DS-1252 > Project: DSpace > Issue Type: New Feature > Components: DSpace API, JSPUI >Reporter: Andrea Bollini >Priority: Major > Labels: has-pull-request > > This contribution add to the DSpace the ability to import from the major > bibliographic database both online than local (file based). > Out-of-box it provides plugins to import from: > - DOI via crossref API > - PubMedID via webservices > - ArXiv > - local BibTeX files > - local files in ISI Plain text format > Support for additional providers can be easily implemented, the import is > done via UI (currently only the JSPUI is supported but extension to XMLUI > should be an easy task for any XMLUI experts). > The feature can be turned on/off in configuration, the available plugins are > also configurated via dspace.cfg. > Mapping from the import format (CrossRef, PubMed, etc.) to your local DSpace > metadata is done in external properties files in config/crosswalk (standard > mapping is provided). > In mapping files you can define different mapping rule basing on the > destination collection (dspace form name) and origin "type" (for example in > bibtex you have: @chapter, @book, etc.) > Additional hacks for alter the imported values after the initial import or > add other values automatically are provided (see the SanitezeImportedMetadata > and the EnhanceImportedMetadata interfaces). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinf
[Dspace-devel] [DuraSpace JIRA] (DS-1244) OpenSearch not working as expected when Discovery is enabled
[ https://jira.duraspace.org/browse/DS-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1244: --- Component/s: (was: DSpace API) XMLUI > OpenSearch not working as expected when Discovery is enabled > > > Key: DS-1244 > URL: https://jira.duraspace.org/browse/DS-1244 > Project: DSpace > Issue Type: Bug > Components: Discovery, XMLUI >Affects Versions: 1.8.2, 3.0 >Reporter: Nestor Oviedo > Labels: 404, Discovery, OpenSearch, open-search, simple-search > > We enabled the Discovery aspect (and disabled the SearchArtifact > aspect). It seemed there were no problem until we try the OpenSearch > service. > There are two main problems here: > 1) URL "/simple-search" returns a 404 error > 2) URL "/open-search" is not using Solr services > About problem 1, that value is defined in the > "websvc.opensearch.uicontext" property (in dspace.cfg). The DSpace > manual says it is for HTML requests and should be changed only for > non-standard servlet mapping. > As I can see, this property could be changed to "/discover" and the > OpenSearch returning HTML pages with results would be working as > expected. > If this is true, maybe this situation could be added to the DSpace manual. > About problem 2, I've seen the "/open-search" URL is matched in the > main sitemap.xmap (the one located in > /sitemap.xmap), and a special generator is > invoked to make the search and to create the RSS/ATOM with the > results.This special generator is > org.dspace.app.xmlui.cocoon.OpenSearchGenerator . > The problem here is that the search is made using the PostgreSQL index > instead of the Solr services. > I suspect a brand new generator should be created, which would use the > Solr services for searching. > We will be working on this. If anyone has some comment or suggest, it'd be > very welcome. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1244) OpenSearch not working as expected when Discovery is enabled
[ https://jira.duraspace.org/browse/DS-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26053#comment-26053 ] Andrea Bollini commented on DS-1244: the issue is only related to the XMLUI webapp the porting of discovery to JSPUI that should be included in 3.0 manage properly open-search > OpenSearch not working as expected when Discovery is enabled > > > Key: DS-1244 > URL: https://jira.duraspace.org/browse/DS-1244 > Project: DSpace > Issue Type: Bug > Components: Discovery, XMLUI >Affects Versions: 1.8.2, 3.0 >Reporter: Nestor Oviedo > Labels: 404, Discovery, OpenSearch, open-search, simple-search > > We enabled the Discovery aspect (and disabled the SearchArtifact > aspect). It seemed there were no problem until we try the OpenSearch > service. > There are two main problems here: > 1) URL "/simple-search" returns a 404 error > 2) URL "/open-search" is not using Solr services > About problem 1, that value is defined in the > "websvc.opensearch.uicontext" property (in dspace.cfg). The DSpace > manual says it is for HTML requests and should be changed only for > non-standard servlet mapping. > As I can see, this property could be changed to "/discover" and the > OpenSearch returning HTML pages with results would be working as > expected. > If this is true, maybe this situation could be added to the DSpace manual. > About problem 2, I've seen the "/open-search" URL is matched in the > main sitemap.xmap (the one located in > /sitemap.xmap), and a special generator is > invoked to make the search and to create the RSS/ATOM with the > results.This special generator is > org.dspace.app.xmlui.cocoon.OpenSearchGenerator . > The problem here is that the search is made using the PostgreSQL index > instead of the Solr services. > I suspect a brand new generator should be created, which would use the > Solr services for searching. > We will be working on this. If anyone has some comment or suggest, it'd be > very welcome. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1223) Display frequencies of items in single browsing for selected indices
[ https://jira.duraspace.org/browse/DS-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26091#comment-26091 ] Andrea Bollini commented on DS-1223: Hi Kostas, first: sorry for the late reply I was missed your followup. I will try to test your patch directly today. Obvious it is not appropriate use the "second" version of the patch if this is more slow that your first contribution. This is very odd, I'm think (not checked yet) that you are doing join in the wrong order i.e. you are building a full browse list with frequencies and after selecting the porting of browse to show. You should be able to do the join at the end so that the left side is really small (20 terms with the current default pagination configuration). If for some really strange reason also with this strategy the performance will be slower than before, I suggest to try to calculate the frequencies with a single separated query in the browse class just before setting the values for the view: (for example here: https://github.com/DSpace/DSpace/pull/52/files#L2R422 ) Are you able to make these changes shortly? to help me to track down the issue can you attach the resulting query when the frequencies are enabled and disabled? > Display frequencies of items in single browsing for selected indices > > > Key: DS-1223 > URL: https://jira.duraspace.org/browse/DS-1223 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Affects Versions: 1.8.2 >Reporter: Christina Paschou > Labels: has-patch, has-pull-request > Attachments: browse_frequencies.diff, README.txt > > > DSpace provides by default two types of browsing, naming them single browsing > and full browsing according to the corresponding names of the .jsp files that > are responsible for handling each request (single.jsp & full.jsp). > Each type of browsing is defined accordingly and configured in different way > in the configuration file dspace.cfg. > The proposed improvement is applied for the case of browsing by a unique > index of metadata values from the item (single browsing). In this case, the > user can define for each metadata browse index whether he wishes to add next > to its various metadata values the frequencies of items that are included. > The configuration takes place in the dspace.cfg. > Examples: > http://phdtheses.ekt.gr/eadd/browse?type=subject > http://phdtheses.ekt.gr/eadd/browse?type=country > http://phdtheses.ekt.gr/eadd/browse?type=language > Attached you can find the patch file and a readme file with details about tha > configuration that is needed to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1223) Display frequencies of items in single browsing for selected indices
[ https://jira.duraspace.org/browse/DS-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26108#comment-26108 ] Andrea Bollini commented on DS-1223: it looks as the problem was what I suspect, you need to limit the left side before make the join. The final query (in postgres) that you need to run is select browsepag.*, count(item_id) from --- below the "orginal" query as subquery to use in join (SELECT bi_2_dis.* FROM bi_2_dis ORDER BY sort_value ASC NULLS LAST LIMIT 20) as browsepag left join bi_2_dmap as freq on browsepag.distinct_id = freq.distinct_id group by browsepag.id, browsepag.distinct_id, browsepag.authority, browsepag.value, browsepag.sort_value -- it is important to re-order the result ORDER BY sort_value ASC NULLS LAST in my test environments 4000 distinct authors and 8400 items the query with frequencies count require 1ms more (23ms vs 22ms) Can you check this query in your test environment and make the required code modification? > Display frequencies of items in single browsing for selected indices > > > Key: DS-1223 > URL: https://jira.duraspace.org/browse/DS-1223 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Affects Versions: 1.8.2 >Reporter: Christina Paschou > Labels: has-patch, has-pull-request > Attachments: browse_frequencies.diff, README.txt > > > DSpace provides by default two types of browsing, naming them single browsing > and full browsing according to the corresponding names of the .jsp files that > are responsible for handling each request (single.jsp & full.jsp). > Each type of browsing is defined accordingly and configured in different way > in the configuration file dspace.cfg. > The proposed improvement is applied for the case of browsing by a unique > index of metadata values from the item (single browsing). In this case, the > user can define for each metadata browse index whether he wishes to add next > to its various metadata values the frequencies of items that are included. > The configuration takes place in the dspace.cfg. > Examples: > http://phdtheses.ekt.gr/eadd/browse?type=subject > http://phdtheses.ekt.gr/eadd/browse?type=country > http://phdtheses.ekt.gr/eadd/browse?type=language > Attached you can find the patch file and a readme file with details about tha > configuration that is needed to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1260) make host restriction configurable for Solr access
[ https://jira.duraspace.org/browse/DS-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26129#comment-26129 ] Andrea Bollini commented on DS-1260: we do such configuration using the context file in Tomcat (i.e. conf/Catalina/localhost/solr.xml) it looks like: I remember that when we have tried to use the LocalHostRestrictionFilter we have had trouble with IPv6 (on windows local connection was see as coming from :1) > make host restriction configurable for Solr access > -- > > Key: DS-1260 > URL: https://jira.duraspace.org/browse/DS-1260 > Project: DSpace > Issue Type: Improvement > Components: Solr >Reporter: Ivan Masár > Fix For: 4.0 > > > Currently, Solr can be configured to allow only connections from localhost > (default) or by turning off the filter to allow all connections. This is not > granular enough. > Allow access from IPs and IP ranges (preferably in CIDR format) to be > configured as allowed/disallowed. > Case this filter as a template: > https://github.com/DSpace/dspace-solr/blob/master/webapp/src/main/java/org/dspace/solr/filters/LocalHostRestrictionFilter.java > Configuration is currently here: > https://github.com/DSpace/dspace-solr/blob/master/webapp/src/main/webapp/WEB-INF/web.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1223) Display frequencies of items in single browsing for selected indices
[ https://jira.duraspace.org/browse/DS-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26136#comment-26136 ] Andrea Bollini commented on DS-1223: you can do the same trick also when browsing is scoped to a community or a collection the resulting query for a collection should be SELECT COUNT(*) AS num, distable.value, distable.authority FROM (SELECT bi_2_dis.* FROM bi_2_dis, (SELECT DISTINCT bi_2_dmap.distinct_id FROM collection2item, bi_2_dmap WHERE bi_2_dmap.item_id=collection2item.item_id AND collection2item.collection_id=? ) mappings WHERE bi_2_dis.id=mappings.distinct_id ORDER BY sort_value ASC NULLS LAST LIMIT ?) distable, (SELECT bi_2_dmap.distinct_id FROM bi_2_dmap) mappings WHERE distable.id=mappings.distinct_id GROUP BY distable.value, distable.authority, distable.sort_value ORDER BY sort_value ASC NULLS LAST in my environment using a "large collection" that include almost all the content of the repository (4000authors / 8000 items) I see a 25% performance improvement. The main point is that with this query the size of the left side of the join is fixed at the pagination size. Are you checking also the Oracle side? > Display frequencies of items in single browsing for selected indices > > > Key: DS-1223 > URL: https://jira.duraspace.org/browse/DS-1223 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Affects Versions: 1.8.2 >Reporter: Christina Paschou > Labels: has-patch, has-pull-request > Attachments: browse_frequencies.diff, README.txt > > > DSpace provides by default two types of browsing, naming them single browsing > and full browsing according to the corresponding names of the .jsp files that > are responsible for handling each request (single.jsp & full.jsp). > Each type of browsing is defined accordingly and configured in different way > in the configuration file dspace.cfg. > The proposed improvement is applied for the case of browsing by a unique > index of metadata values from the item (single browsing). In this case, the > user can define for each metadata browse index whether he wishes to add next > to its various metadata values the frequencies of items that are included. > The configuration takes place in the dspace.cfg. > Examples: > http://phdtheses.ekt.gr/eadd/browse?type=subject > http://phdtheses.ekt.gr/eadd/browse?type=country > http://phdtheses.ekt.gr/eadd/browse?type=language > Attached you can find the patch file and a readme file with details about tha > configuration that is needed to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1223) Display frequencies of items in single browsing for selected indices
[ https://jira.duraspace.org/browse/DS-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26137#comment-26137 ] Andrea Bollini commented on DS-1223: please comment out the frequencies configuration in dspace.cfg so that default are used out-of-box by fresh dspace installation > Display frequencies of items in single browsing for selected indices > > > Key: DS-1223 > URL: https://jira.duraspace.org/browse/DS-1223 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Affects Versions: 1.8.2 >Reporter: Christina Paschou > Labels: has-patch, has-pull-request > Attachments: browse_frequencies.diff, README.txt > > > DSpace provides by default two types of browsing, naming them single browsing > and full browsing according to the corresponding names of the .jsp files that > are responsible for handling each request (single.jsp & full.jsp). > Each type of browsing is defined accordingly and configured in different way > in the configuration file dspace.cfg. > The proposed improvement is applied for the case of browsing by a unique > index of metadata values from the item (single browsing). In this case, the > user can define for each metadata browse index whether he wishes to add next > to its various metadata values the frequencies of items that are included. > The configuration takes place in the dspace.cfg. > Examples: > http://phdtheses.ekt.gr/eadd/browse?type=subject > http://phdtheses.ekt.gr/eadd/browse?type=country > http://phdtheses.ekt.gr/eadd/browse?type=language > Attached you can find the patch file and a readme file with details about tha > configuration that is needed to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1237) Support date ranges in advance search
[ https://jira.duraspace.org/browse/DS-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26138#comment-26138 ] Andrea Bollini commented on DS-1237: Hi Kostas, imho we need to apply some change before commit this contribution to the master: 1) you are (partially) assuming that the advanced search include only 3 dropdown for index selection but this was configurable in local customization including a num_field hidden field in the form where the actual number was specified. You take care of this in https://github.com/DSpace/DSpace/pull/50/files#L0R407 but not here https://github.com/DSpace/DSpace/pull/50/files#L0R180 where it is assumed that query4 is related to the date range 2) it works with only a range, if the user select the same index there are issues (ok, it is a stupid use case) but there are not possibilities to configure two different data range index (for example one on date.issued and one on date.available) 3) it will be better if you require and work on the date type index (search.index. = dateissued:dc.date.issued:date). With this configuration the lucene index is called dateissued.year see https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/search/DSIndexer.java#L201 https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/search/DSIndexer.java#L1082 4) for the javascript methods you should use the jquery framework as it is supported by all the major browser, getElementById and .innerHTML can produce issues with some (old/bad) IE and others. I also suggest to move (and rename in a more clear way) these methods in a dedicated .js file. You can include this file in the header fragment setting the attribute dspace.layout.head in the request see https://github.com/DSpace/DSpace/blob/master/dspace-jspui/dspace-jspui-webapp/src/main/webapp/layout/header-default.jsp#L38 https://github.com/DSpace/DSpace/blob/master/dspace-jspui/dspace-jspui-webapp/src/main/webapp/layout/header-default.jsp#L73 > Support date ranges in advance search > - > > Key: DS-1237 > URL: https://jira.duraspace.org/browse/DS-1237 > Project: DSpace > Issue Type: New Feature > Components: JSPUI >Reporter: Kostas Stamatis > Labels: has-patch, has-pull-request > Attachments: daterange_patch.diff, README.txt > > > This proposed extension (implemented by National Documentation Centre/EKT - > http://www.ekt.gr) allows date range search in advance search. When a search > index is declared as a "date" search index in configuration file, then, when > selected in advance search drop down lists, a new drop down list appears to > select the range type (equals, before than, after than or between) and the > appropriate fields appear to the user to input the date ranges for the search. > The date range search is based on Lucene's range search mechanism. > The only limitation of this extension is that the companison is String-based > meaning that it works better if the metadata value in the date fields are > saved in the format -mm-dd. > USEFULNESS > - > In case you want to search for records that are dated within a period of > time, you can use this extension to add this functionality in DSpace's > advance search. > CONFIGURATION FILES > --- > In the default configuration file of DSpace (dspace.cfg) just declare the > search indices that you want to be of type date, as follows: > #Declare the indices that are of type date and want to have ranges in > searching > search.index.date.1 = date > EXAMPLES > > Repository: http://phdtheses.ekt.gr/eadd/advanced-search > Note: Select search by date and then a new option drop-down menu appears -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1238) Display advance search form after an advance search
[ https://jira.duraspace.org/browse/DS-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26139#comment-26139 ] Andrea Bollini commented on DS-1238: Hi Kostas, imho this contribution requires some changes before to be ready for commit to the master. 1) we should avoid heavy code duplication, most of this jsp comes from the simple-search result jsp with inclusion of the "form" fragment from the advanced-search. An appropriate use of inclusion should be able to avoid this 2) the user should be able to switch to the old "onebox" where it can do use of the full lucene syntax if she wants. Both form: "advanced-search" and "lucene-syntax" forms should be included in the resulting html page with the lucene-syntax form hided and activable using javascript (users with javascript disabled will be able to see and use both) Andrea PS: you have a misprint here: https://github.com/DSpace/DSpace/pull/51/files#L1R54 > Display advance search form after an advance search > > > Key: DS-1238 > URL: https://jira.duraspace.org/browse/DS-1238 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Affects Versions: 1.8.2 >Reporter: Kostas Stamatis >Assignee: Andrea Bollini > Labels: has-patch, has-pull-request > Attachments: advancedresults_patch.diff, README.txt > > > This proposed extension (implemented by National Documentation Centre/EKT - > http://www.ekt.gr) displays the advance search form after an advance search > in DSpace. The current version of DSpace, returns a simple search form with > the Lucene query that is not starange for the user. In case the user needs to > redifine the query, he must change the Lucene query which is not wise at all. > Given this extension, he can see the advance form filled with the initial > search parameters and make hiw changes and search again. > EXAMPLES > > Repository: http://phdtheses.ekt.gr/eadd/advanced-search > Note: Make an advance search and notice that in the results page, the advance > search form is displayed as well -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1228) Concatenate values of multi-value fields in item display
[ https://jira.duraspace.org/browse/DS-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26140#comment-26140 ] Andrea Bollini commented on DS-1228: Hi Kostas, I suggest to make the following changes: 1) webui.itemdisplay.inclusespace is not necessary, the user can get the same result setting only the webui.itemdisplay.separator (i.e. webui.itemdisplay.separator = ; ). You can add a comment near the configuration to specify this. 2) this line https://github.com/DSpace/DSpace/pull/48/files#L0R484 could produce a NPE if the inclusespace properties is not set. You should use the ConfigurationManager.getBooleanProperty instead to avoid this. Anyway, this will go out if you agree with 1 Andrea > Concatenate values of multi-value fields in item display > > > Key: DS-1228 > URL: https://jira.duraspace.org/browse/DS-1228 > Project: DSpace > Issue Type: Improvement > Components: JSPUI > Environment: DSpace 1.8.2 >Reporter: Kostas Stamatis > Labels: has-patch, has-pull-request, itemtag > Attachments: concatvalues-patch.diff, README.txt > > > This proposed extension (implemented by National Documentation Centre/EKT - > http://www.ekt.gr) permits in JSPUI and item display (item tag) to > concatenate the multiple values of a field to one line instead of displaying > then each one in a seperate line. > The configuration is done within dspace.cfg file and the users can select if > they want the concatenation or the default line break, the separation > character or string and the existence of a non-breaking space before the > separator. > USEFULNESS > - > Sometimens, some fields (usually subject keywords) contain multiple values in > a large number than makes the item display have a huge height that makes the > record unreadable. Using this extension, you can concatenate the values in > one line and thus gain space from the item display screen. > CONFIGURATION FILES > --- > Tag cloud is fully configurable within the default dspace.cfg configuration > file of DSpace. The new configuration options are: > # Customise the DC metadata fields to show in the default simple item view. > # > # The form is prefix>.[.|.*][(date)|(link)|(nobreakline)], ... > # > # For example: > #dc.title = Dublin Core element 'title' (unqualified) > #dc.title.alternative = DC element 'title', qualifier 'alternative' > #dc.title.* = All fields with Dublin Core element 'title' > # (any or no qualifier) > #dc.identifier.uri(link) = DC identifier.uri, render as a link > #dc.date.issued(date) = DC date.issued, render as a date > #dc.subject(nobreakline) = DC subject.keyword, rendered as separated > values > # (see also webui.itemdisplay.inclusespace and > webui.itemdisplay.separator options) > #"link/date" options can be combined with "nobreakline" option using a > space among them i.e "dc.identifier.uri(link nobreakline)" > # > # If an item has no value for a particular field, it won't be displayed. > # The name of the field for display will be drawn from the current UI > # dictionary, using the key: > # > # "metadata.
[Dspace-devel] [DuraSpace JIRA] (DS-1225) Show display values for controlled vocabularies in Item Page
[ https://jira.duraspace.org/browse/DS-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26142#comment-26142 ] Andrea Bollini commented on DS-1225: The current pull request doesn't compile, there is a misprint here: https://github.com/DSpace/DSpace/pull/54/files#L0R I have also found a sysout misprint https://github.com/DSpace/DSpace/pull/54/files#L0R1257 IMHO the support for multilingual is not consistent with the patch approach. When it is configured the "display" style (please rename to inputform) the label is taken from the input-form.xml file when the style is displayMultilanguage the label is taken from the messages.properties files. Please note that you can load a different input-form.xml (_it, _fr, etc.) using the user locale Locale sessionLocale = null; sessionLocale = UIUtil.getSessionLocale(request); String formFileName = I18nUtil.getInputFormsFileName(sessionLocale); DCInputReader inputReader = new DCInputReader(formFileName); I will remove the displayMultilanguage style and use always an "inputform" style that read the display-value from the right (user locale) input-form > Show display values for controlled vocabularies in Item Page > > > Key: DS-1225 > URL: https://jira.duraspace.org/browse/DS-1225 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Affects Versions: 1.8.2 >Reporter: Rania Stathopoulou > Labels: has-patch, has-pull-request > Attachments: > 0001-Show-display-values-input-forms-for-controlled-vocab.patch, README.txt, > show_displayValues_itemTag.diff > > > In submission process, when the "input-type" of an element is set to > "dropdown" (/dspace/config/input-forms.xml), > by default DSpace stores the "stored-value" and shows the "displayed-value" > in submission form. > Nevertheless, in item page (ItemTag) the "stored-value" is displayed which > usually is not user friendly. > The proposed improvement is applied in order to show the displayed values in > item page and has been implemented by National Documentation Centre (EKT - > http://www.ekt.gr). > Specifically, the user can set if he wants to show the displayed-value in Web > Interface Settings > webui.itemdisplay.default in dspace.cfg. > There are two options: > a) put (display) next to the respected metadata field in webui.itemdisplay, > in order to show the displayed-value(s) based on the respective(s) > stored-value(s) from the value-pairs-name in input forms > b) put (displayMultilanguage) next to the respected metadata field in > webui.itemdisplay, in order to show the localized displayed-value(s) based on > the respective(s) stored-value(s) from the value-pairs-name in input forms. > In this case, the displayed-value(s) are set as message keys and the message > values must be set in message.properties for each language supported by the > repository. > - > EXAMPLES > - > a) When in input forms we have: > > dc > language > > true > Type > dropdown > Select the language(s) of content of the item. To select more > than one value in the list, you may have to hold down the "CTRL" or "Shift" > key. > > > where: > > > Greek > gre > > > English > eng > > > French > fre > > > German > ger > > > Spanish > spa > > ... > > Then, we should put dc.language(display) in dspace.cfg. > In this case, in item page the word 'Spanish' will be shown instead of 'spa'. > a) When in input forms we have: > > dc > language > > true > Type > value-pairs-name="common_languages_Multilingual">dropdown > Select the language(s) of content of the item. To select more > than one value in the list, you may have to hold down the "CTRL" or "Shift" > key. > > > where: > dc-term="language_iso"> > > jsp.self-archive.dc.language.gre > gre > > > jsp.self-archive.dc.language.eng > eng > > > jsp.self-archive.dc.language.fre > fre > > > jsp.self-archive.dc.language.ger > ger > > > jsp.self-archive.dc.language.spa > spa > > ... > > Then, we should put dc.language(displayMultilingual) in dspace.cfg. > In this case, in item page the word 'Spanish' will be shown instead of 'spa' > if the user is in English interface and > 'Ισπανικά' if the user is in Greek interface. > e.g. (see Language field) > http://repository.edulll.gr/edulll/handle/1079
[Dspace-devel] [DuraSpace JIRA] (DS-1227) Tag cloud for any browse index in the home page of DSpace
[ https://jira.duraspace.org/browse/DS-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26146#comment-26146 ] Andrea Bollini commented on DS-1227: some other notes: 1) there are hardcoded queries that make direct use of the browse tables instead of use the browse API (so it doesn't work with Discovery) 2) some query are heavy, all the browse terms are selected https://github.com/DSpace/DSpace/pull/47/files#L4R509 3) the context is not properly closed (not in a finally block) https://github.com/DSpace/DSpace/pull/47/files#L4R520 4) there are dependencies from servlet 3.0alpha and tomcat.jsp > Tag cloud for any browse index in the home page of DSpace > - > > Key: DS-1227 > URL: https://jira.duraspace.org/browse/DS-1227 > Project: DSpace > Issue Type: New Feature > Components: JSPUI >Reporter: Kostas Stamatis >Assignee: Sands Fish > Labels: has-patch, has-pull-request, tag-cloud > Attachments: opencloud.jar, README.txt, tagcloud-patch.diff > > > This proposed extension (implemented by National Documentation Centre/EKT - > http://www.ekt.gr) allows the import of a tag cloud in the homepage of DSpace. > The tag cloud can include values from any of the browse indices (of metadata > type) of the repository and this is a configuration option along with many > other options that you can see later. > Tha tag cloud is implemented as a tag, meaning that it can be included in any > page of the DSpace repository besides the homepage. > USEFULNESS > - > Select a important browse index of your repository (i.e. subject) and include > all major subjects of your records in the home page of DSpace to attract > visitors. > CONFIGURATION FILES > --- > Tag cloud is fully configurable within the default dspace.cfg configuration > file of DSpace. The new configuration options are: > ### > # TAG CLOUD configuration # > ### > # > # Should display tag cloud in the home page? > # Possible values: true | false > webui.tagcloud.home.show = true > # > # Select the browse index to create a tag cloud for in the home page > # Possible values: any of the browse indices declared earlier in this conf > file > webui.tagcloud.home.bindex = subject > # > # Select the total tags to show > # Possible values: any integer from 1 to infinity > webui.tagcloud.home.maxtags = 50 > # > # Should display the score next to each tag? > # Possible values: true | false > webui.tagcloud.home.showscore = false > # > # The score that tags with lower than that will not appear in the rag cloud > # Possible values: any integer from 1 to infinity > webui.tagcloud.home.cutlevel = 5 > # > # Should display the tag as center aligned in the page or left aligned? > # Possible values: true | false > webui.tagcloud.home.showcenter = true > # > # The font size (in em) for the tag with the lowest score > # Possible values: any decimal > webui.tagcloud.home.fontfrom = 1.3 > # > # The font size (in em) for the tag with the highest score > # Possible values: any decimal > webui.tagcloud.home.fontto = 2.8 > # > # The case of the tags > # Possible values: Case.LOWER | Case.UPPER | Case.CAPITALIZATION | > Case.PRESERVE_CASE | Case.CASE_SENSITIVE > webui.tagcloud.home.tagcase = Case.PRESERVE_CASE > # > # If the 3 colors of the tag cloud should be independent of score > (random=yes) or based on the score > # Possible values: true | false > webui.tagcloud.home.randomcolors = true > # > # The ordering of the tags (based either on the name or the score of the tag) > # Possible values: Tag.NameComparatorAsc | Tag.NameComparatorDesc | > Tag.ScoreComparatorAsc | Tag.ScoreComparatorDesc > webui.tagcloud.home.tagorder = Tag.NameComparatorAsc > # > # The first color of the tags > # Possible values: hex value of the color (i.e. e3d67a) > webui.tagcloud.home.tagcolor1 = D96C27 > # > # The second color of the tags > # Possible values: hex value of the color (i.e. e3d67a) > webui.tagcloud.home.tagcolor2 = 424242 > # > # The third color of the tags > # Possible values: hex value of the color (i.e. e3d67a) > webui.tagcloud.home.tagcolor3 = 818183 > EXTERNAL LIBRARIES > -- > This extension makes use of the following external java library: > a) opencloud |(http://opencloud.mcavallo.org/): a java library for for > generating and managing tag clouds (under MIT licence) > EXAMPLES > --- > Repository: Managing Authority of the Operational Programme "Education and > Lifelong Learning" > URL: http://repository.edulll.gr/edulll/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, p
[Dspace-devel] [DuraSpace JIRA] (DS-1218) BrowseDAO based on discovery
[ https://jira.duraspace.org/browse/DS-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini resolved DS-1218. Resolution: Fixed pull request squashed and committed. I will update the documentation on the wiki in the next few days and will send a message to the release team when done to check "English" > BrowseDAO based on discovery > > > Key: DS-1218 > URL: https://jira.duraspace.org/browse/DS-1218 > Project: DSpace > Issue Type: New Feature > Components: Discovery >Reporter: Andrea Bollini >Assignee: Andrea Bollini >Priority: Major > Labels: has-pull-request > Fix For: 3.0 > > > Implementation of the BrowseDAO classes to use the data in the SOLR search > core (dspace-discovery) instead of Database query. > This contribution is supported by the University of Hong Kong that has > adopted the first version of this code since July 2010 > Software development by the CILEA SURplus Team (http://www.cilea.it) > Example: http://hub.hku.hk/browse?type=title -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1236) Auto update advance search drop down lists from configuration file
[ https://jira.duraspace.org/browse/DS-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26153#comment-26153 ] Andrea Bollini commented on DS-1236: Hi Kostas, some minor issues to fix: https://github.com/DSpace/DSpace/pull/49/files#L0R127 https://github.com/DSpace/DSpace/pull/49/files#L0R154 refer always to field1 instead of 2 and 3. It will be useful if you can add a check that assure backward compatibility if the new configuration parameters are not present (i.e. if the while loop exit with idx == 1 then you should populate the array with the pre-3.0 index names) Finally, due to some changes in the master branch the pull request cannot be automatically merged, can you resolve the merge conflict? > Auto update advance search drop down lists from configuration file > -- > > Key: DS-1236 > URL: https://jira.duraspace.org/browse/DS-1236 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Affects Versions: 1.8.2 >Reporter: Kostas Stamatis >Assignee: Andrea Bollini > Labels: has-patch, has-pull-request > Attachments: autosearchfields_patch.diff, README.txt > > > This proposed extension (implemented by National Documentation Centre/EKT - > http://www.ekt.gr) allows the automated creation of dropdown menus in advance > search according to configuration options. > This is not an option in DSpace 1.8.2 since the advanceSearch.jsp includes > the options in the select drop down menus in a hardcoded manner. > USEFULNESS > - > In case you change the search indices in the default dspace.cfg configuration > file, the drop down menus in the advance search page are not automatically > updated with these new indices. With this extension, you do not have to worry > about the advance jsp page since it is automatically updated from the > configuration file. > CONFIGURATION FILES > --- > In the default configuration file of DSpace (dspace.cfg) just declare the > search indices that you want to have in the drop down menus within advance > search page as follows: > # Declare search indices to appear in drop down menus > search.index.display.1 = author > search.index.display.2 = title > search.index.display.3 = keyword > search.index.display.4 = abstract > search.index.display.5 = author > search.index.display.6 = series > search.index.display.7 = abstract > search.index.display.8 = mime > search.index.display.9 = sponsor > search.index.display.10 = identifier > search.index.display.11 = language -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1237) Support date ranges in advance search
[ https://jira.duraspace.org/browse/DS-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26192#comment-26192 ] Andrea Bollini commented on DS-1237: Yes, currently the jsp don't use num_field out-of-box and imho we should not change this. The num_field is used by local customizations that want add more dropdown mostly to use as filter, take a look here: http://www.earth-prints.org/advanced-search > Support date ranges in advance search > - > > Key: DS-1237 > URL: https://jira.duraspace.org/browse/DS-1237 > Project: DSpace > Issue Type: New Feature > Components: JSPUI >Reporter: Kostas Stamatis > Labels: has-patch, has-pull-request > Attachments: daterange_patch.diff, README.txt > > > This proposed extension (implemented by National Documentation Centre/EKT - > http://www.ekt.gr) allows date range search in advance search. When a search > index is declared as a "date" search index in configuration file, then, when > selected in advance search drop down lists, a new drop down list appears to > select the range type (equals, before than, after than or between) and the > appropriate fields appear to the user to input the date ranges for the search. > The date range search is based on Lucene's range search mechanism. > The only limitation of this extension is that the companison is String-based > meaning that it works better if the metadata value in the date fields are > saved in the format -mm-dd. > USEFULNESS > - > In case you want to search for records that are dated within a period of > time, you can use this extension to add this functionality in DSpace's > advance search. > CONFIGURATION FILES > --- > In the default configuration file of DSpace (dspace.cfg) just declare the > search indices that you want to be of type date, as follows: > #Declare the indices that are of type date and want to have ranges in > searching > search.index.date.1 = date > EXAMPLES > > Repository: http://phdtheses.ekt.gr/eadd/advanced-search > Note: Select search by date and then a new option drop-down menu appears -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1217) DSpace Discovery for JSPUI
[ https://jira.duraspace.org/browse/DS-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1217: --- Status: Open (was: Received) > DSpace Discovery for JSPUI > -- > > Key: DS-1217 > URL: https://jira.duraspace.org/browse/DS-1217 > Project: DSpace > Issue Type: New Feature > Components: Discovery, JSPUI >Reporter: Andrea Bollini >Assignee: Andrea Bollini >Priority: Major > Labels: has-pull-request > Fix For: 3.0 > > > Porting of the discovery features (SOLR Search) to the JSPUI. > This contribution is supported by the University of Hong Kong that has > adopted the first version of this code since July 2010 > Software development by the CILEA SURplus Team (http://www.cilea.it) > Example: http://hub.hku.hk/simple-search?sort_by=1&query=&submit=search -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1217) DSpace Discovery for JSPUI
[ https://jira.duraspace.org/browse/DS-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini resolved DS-1217. Resolution: Fixed pull request squashed and committed. I will update the documentation on the wiki in the next few days and will send a message to the release team when done to check "English" > DSpace Discovery for JSPUI > -- > > Key: DS-1217 > URL: https://jira.duraspace.org/browse/DS-1217 > Project: DSpace > Issue Type: New Feature > Components: Discovery, JSPUI >Reporter: Andrea Bollini >Assignee: Andrea Bollini >Priority: Major > Labels: has-pull-request > Fix For: 3.0 > > > Porting of the discovery features (SOLR Search) to the JSPUI. > This contribution is supported by the University of Hong Kong that has > adopted the first version of this code since July 2010 > Software development by the CILEA SURplus Team (http://www.cilea.it) > Example: http://hub.hku.hk/simple-search?sort_by=1&query=&submit=search -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1223) Display frequencies of items in single browsing for selected indices
[ https://jira.duraspace.org/browse/DS-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26210#comment-26210 ] Andrea Bollini commented on DS-1223: we are trying to finalize this contribution but some issues arise: 1) the SOLR Browse has compilation errors due to this contribution 2) frequencies was not shown in XMLUI 3) the jump_to function in metadata browse is broken when frequencies are enabled 4) the browsing within a community not work (the query look for collection_id). Inside a collection it works 5) the query building is more messy than before 6) lyncodev report some wrong code indentation that need to be fixed points 1, 2 and 3 are addressed in my branch https://github.com/abollini/DSpace/tree/DS-1223 Kostas should look to the point 4 and 5 tomorrow (hopeful also 6) The test that I have performed in both UIs are: 1) check browsing pagination and sorting for both metadata and item browse in the repository scope 2) test the jump_to function (for date, item level browse as title and metadata browse) 3) test frequencies calculation in browse with and without authrority 4) as in point 1-3 inside a community 5) as in point 1-3 inside a collection 6) browse withdrawn item 7) browse of private items (possible only in XMLUI) 8) item mapper tool in collection admin 9) recent submission in site, community and collection > Display frequencies of items in single browsing for selected indices > > > Key: DS-1223 > URL: https://jira.duraspace.org/browse/DS-1223 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Affects Versions: 1.8.2 >Reporter: Christina Paschou > Labels: has-patch, has-pull-request > Attachments: browse_frequencies.diff, README.txt > > > DSpace provides by default two types of browsing, naming them single browsing > and full browsing according to the corresponding names of the .jsp files that > are responsible for handling each request (single.jsp & full.jsp). > Each type of browsing is defined accordingly and configured in different way > in the configuration file dspace.cfg. > The proposed improvement is applied for the case of browsing by a unique > index of metadata values from the item (single browsing). In this case, the > user can define for each metadata browse index whether he wishes to add next > to its various metadata values the frequencies of items that are included. > The configuration takes place in the dspace.cfg. > Examples: > http://phdtheses.ekt.gr/eadd/browse?type=subject > http://phdtheses.ekt.gr/eadd/browse?type=country > http://phdtheses.ekt.gr/eadd/browse?type=language > Attached you can find the patch file and a readme file with details about tha > configuration that is needed to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1223) Display frequencies of items in single browsing for selected indices
[ https://jira.duraspace.org/browse/DS-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26211#comment-26211 ] Andrea Bollini commented on DS-1223: as I have enabled frequencies display also in XMLUI it will be better to move back the configuration near the other general browse configuration > Display frequencies of items in single browsing for selected indices > > > Key: DS-1223 > URL: https://jira.duraspace.org/browse/DS-1223 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Affects Versions: 1.8.2 >Reporter: Christina Paschou > Labels: has-patch, has-pull-request > Attachments: browse_frequencies.diff, README.txt > > > DSpace provides by default two types of browsing, naming them single browsing > and full browsing according to the corresponding names of the .jsp files that > are responsible for handling each request (single.jsp & full.jsp). > Each type of browsing is defined accordingly and configured in different way > in the configuration file dspace.cfg. > The proposed improvement is applied for the case of browsing by a unique > index of metadata values from the item (single browsing). In this case, the > user can define for each metadata browse index whether he wishes to add next > to its various metadata values the frequencies of items that are included. > The configuration takes place in the dspace.cfg. > Examples: > http://phdtheses.ekt.gr/eadd/browse?type=subject > http://phdtheses.ekt.gr/eadd/browse?type=country > http://phdtheses.ekt.gr/eadd/browse?type=language > Attached you can find the patch file and a readme file with details about tha > configuration that is needed to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1236) Auto update advance search drop down lists from configuration file
[ https://jira.duraspace.org/browse/DS-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26216#comment-26216 ] Andrea Bollini commented on DS-1236: Hi Kostas, please review the configuration so that the default match the old dspace behaviour (you have listed author two times and included the mime index not longer here). To make the squash these commands should work git fetch upstream git checkout master git merge upstream/master git branch DS-1236-squashed git checkout DS-1236-squashed git merge --squash DS-1236 git commit -e # the next command will remove your local branch so that you can rename the new squashed branch with the old name and force update the pull request git branch -D DS-1236 git branch -m DS-1236-squashed DS-1236 git push --force origin DS-1236 > Auto update advance search drop down lists from configuration file > -- > > Key: DS-1236 > URL: https://jira.duraspace.org/browse/DS-1236 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Affects Versions: 1.8.2 >Reporter: Kostas Stamatis >Assignee: Andrea Bollini > Labels: has-patch, has-pull-request > Attachments: autosearchfields_patch.diff, README.txt > > > This proposed extension (implemented by National Documentation Centre/EKT - > http://www.ekt.gr) allows the automated creation of dropdown menus in advance > search according to configuration options. > This is not an option in DSpace 1.8.2 since the advanceSearch.jsp includes > the options in the select drop down menus in a hardcoded manner. > USEFULNESS > - > In case you change the search indices in the default dspace.cfg configuration > file, the drop down menus in the advance search page are not automatically > updated with these new indices. With this extension, you do not have to worry > about the advance jsp page since it is automatically updated from the > configuration file. > CONFIGURATION FILES > --- > In the default configuration file of DSpace (dspace.cfg) just declare the > search indices that you want to have in the drop down menus within advance > search page as follows: > # Declare search indices to appear in drop down menus > search.index.display.1 = author > search.index.display.2 = title > search.index.display.3 = keyword > search.index.display.4 = abstract > search.index.display.5 = author > search.index.display.6 = series > search.index.display.7 = abstract > search.index.display.8 = mime > search.index.display.9 = sponsor > search.index.display.10 = identifier > search.index.display.11 = language -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1223) Display frequencies of items in single browsing for selected indices
[ https://jira.duraspace.org/browse/DS-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26223#comment-26223 ] Andrea Bollini commented on DS-1223: from the pull request thread: https://github.com/DSpace/DSpace/pull/52 this contribution is ready to be merged but we have found two limit in the current implementation that cannot be solved: - if the metadata browse is configurated to be case insensitive the frequencies count are show distinct for the terms caseinsensitive equals (i.e. Test and Test will show two different frequencies but clicking on this browse value the user will get a list with the total number of item) - similar to the previous one, if the metadata browse include values with authority and the same authority is associated to multiple values (Variants support) the frequencies are count distinct for any values (i.e. looking to http://hub.hku.hk/browse?type=author&order=ASC&rpp=20&starts_with=palmer and http://hub.hku.hk/browse?type=author&order=ASC&rpp=20&starts_with=宗樹朝 you will get a different frequencies value for any entries "Palmer, David T" but all will link to the same - total - items list) The SOLRBrowse implementation is not affected by these issues. As these issues arise only on specific, not default, configuration I propose to accept the contribution and only make a warning statement that explain this limit suggesting to user that need this feature in buggy configuration to switch to SOLR. We are waiting for testing result on Oracle > Display frequencies of items in single browsing for selected indices > > > Key: DS-1223 > URL: https://jira.duraspace.org/browse/DS-1223 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Affects Versions: 1.8.2 >Reporter: Christina Paschou > Labels: has-patch, has-pull-request > Attachments: browse_frequencies.diff, README.txt > > > DSpace provides by default two types of browsing, naming them single browsing > and full browsing according to the corresponding names of the .jsp files that > are responsible for handling each request (single.jsp & full.jsp). > Each type of browsing is defined accordingly and configured in different way > in the configuration file dspace.cfg. > The proposed improvement is applied for the case of browsing by a unique > index of metadata values from the item (single browsing). In this case, the > user can define for each metadata browse index whether he wishes to add next > to its various metadata values the frequencies of items that are included. > The configuration takes place in the dspace.cfg. > Examples: > http://phdtheses.ekt.gr/eadd/browse?type=subject > http://phdtheses.ekt.gr/eadd/browse?type=country > http://phdtheses.ekt.gr/eadd/browse?type=language > Attached you can find the patch file and a readme file with details about tha > configuration that is needed to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1244) OpenSearch not working as expected when Discovery is enabled
[ https://jira.duraspace.org/browse/DS-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26241#comment-26241 ] Andrea Bollini commented on DS-1244: yes, it has been merged > OpenSearch not working as expected when Discovery is enabled > > > Key: DS-1244 > URL: https://jira.duraspace.org/browse/DS-1244 > Project: DSpace > Issue Type: Bug > Components: Discovery, XMLUI >Affects Versions: 1.8.2, 3.0 >Reporter: Nestor Oviedo > Labels: 404, Discovery, OpenSearch, open-search, simple-search > Fix For: 3.0 > > > We enabled the Discovery aspect (and disabled the SearchArtifact > aspect). It seemed there were no problem until we try the OpenSearch > service. > There are two main problems here: > 1) URL "/simple-search" returns a 404 error > 2) URL "/open-search" is not using Solr services > About problem 1, that value is defined in the > "websvc.opensearch.uicontext" property (in dspace.cfg). The DSpace > manual says it is for HTML requests and should be changed only for > non-standard servlet mapping. > As I can see, this property could be changed to "/discover" and the > OpenSearch returning HTML pages with results would be working as > expected. > If this is true, maybe this situation could be added to the DSpace manual. > About problem 2, I've seen the "/open-search" URL is matched in the > main sitemap.xmap (the one located in > /sitemap.xmap), and a special generator is > invoked to make the search and to create the RSS/ATOM with the > results.This special generator is > org.dspace.app.xmlui.cocoon.OpenSearchGenerator . > The problem here is that the search is made using the PostgreSQL index > instead of the Solr services. > I suspect a brand new generator should be created, which would use the > Solr services for searching. > We will be working on this. If anyone has some comment or suggest, it'd be > very welcome. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1244) OpenSearch not working as expected when Discovery is enabled
[ https://jira.duraspace.org/browse/DS-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini resolved DS-1244. Resolution: Fixed Fix Version/s: 3.0 > OpenSearch not working as expected when Discovery is enabled > > > Key: DS-1244 > URL: https://jira.duraspace.org/browse/DS-1244 > Project: DSpace > Issue Type: Bug > Components: Discovery, XMLUI >Affects Versions: 1.8.2, 3.0 >Reporter: Nestor Oviedo > Labels: 404, Discovery, OpenSearch, open-search, simple-search > Fix For: 3.0 > > > We enabled the Discovery aspect (and disabled the SearchArtifact > aspect). It seemed there were no problem until we try the OpenSearch > service. > There are two main problems here: > 1) URL "/simple-search" returns a 404 error > 2) URL "/open-search" is not using Solr services > About problem 1, that value is defined in the > "websvc.opensearch.uicontext" property (in dspace.cfg). The DSpace > manual says it is for HTML requests and should be changed only for > non-standard servlet mapping. > As I can see, this property could be changed to "/discover" and the > OpenSearch returning HTML pages with results would be working as > expected. > If this is true, maybe this situation could be added to the DSpace manual. > About problem 2, I've seen the "/open-search" URL is matched in the > main sitemap.xmap (the one located in > /sitemap.xmap), and a special generator is > invoked to make the search and to create the RSS/ATOM with the > results.This special generator is > org.dspace.app.xmlui.cocoon.OpenSearchGenerator . > The problem here is that the search is made using the PostgreSQL index > instead of the Solr services. > I suspect a brand new generator should be created, which would use the > Solr services for searching. > We will be working on this. If anyone has some comment or suggest, it'd be > very welcome. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1231) Index (for search) both display and stored values for fields using controlled vocabularies
[
https://jira.duraspace.org/browse/DS-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Bollini resolved DS-1231.
Resolution: Fixed
Fix Version/s: 3.0
> Index (for search) both display and stored values for fields using controlled
> vocabularies
> ---
>
> Key: DS-1231
> URL: https://jira.duraspace.org/browse/DS-1231
> Project: DSpace
> Issue Type: Improvement
> Components: DSpace API
>Affects Versions: 1.8.2
>Reporter: Rania Stathopoulou
> Labels: has-patch, has-pull-request
> Fix For: 3.0
>
> Attachments: README.txt, search_index_ControlledVocabulary
>
>
> In submission process, when the "input-type" of an element is set to
> "dropdown" (/dspace/config/input-forms.xml),
> by default DSpace stores the "stored-value" and shows the "displayed-value"
> in submission form.
> Nevertheless, in order for a user to find the item he must knows the
> "stored-value", since only this value is indexed.
> The proposed improvement is applied in order to index both the
> "displayed-value" and the "stored-value" of an item.
> Specifically, the user can set if he wants also to index the displayed-value
> in Fields to Index for Search by setting 'controlledVocabulary'
> or 'controlledVocabularyMultilingual' as value for [type] property for a
> respective search index.
> There are two options:
> a) put 'controlledVocabulary' next to the respective search index field in
> dspace.cfg, so both the "stored-value(s)" and the respective
> "displayed-value(s)" will be indexed
> b) put 'controlledVocabularyMultilingual' next to the respective search index
> field in dspace.cfg, so both the "stored-value(s)" and the respective
> localized "displayed-value(s)" will be indexed for all the repository
> supported locales.
> In this case, the displayed-value(s) are set as message keys and the message
> values must be set in message.properties for each language supported by the
> repository.
> -
> EXAMPLES
> -
> a) When in input forms we have:
>
> dc
> language
>
> true
> Type
> dropdown
> Select the language(s) of content of the item. To select more
> than one value in the list, you may have to hold down the "CTRL" or "Shift"
> key.
>
>
> where:
>
>
> Greek
> gre
>
>
> English
> eng
>
>
> French
> fre
>
>
> German
> ger
>
>
> Spanish
> spa
>
> ...
>
> Then, if we want to index the languages, we should put search.index.{i} =
> language:dc.language:controlledVocabulary in dspace.cfg.
> In this case, the same items will be found if someones searches by language
> for the word 'Spanish' or the word 'spa'.
> a) When in input forms we have:
>
> dc
> language
>
> true
> Type
> value-pairs-name="common_languages_Multilingual">dropdown
> Select the language(s) of content of the item. To select more
> than one value in the list, you may have to hold down the "CTRL" or "Shift"
> key.
>
>
> where:
> dc-term="language_iso">
>
> jsp.self-archive.dc.language.gre
> gre
>
>
> jsp.self-archive.dc.language.eng
> eng
>
>
> jsp.self-archive.dc.language.fre
> fre
>
>
> jsp.self-archive.dc.language.ger
> ger
>
>
> jsp.self-archive.dc.language.spa
> spa
>
> ...
>
> Then, if we want to index the languages, we should put search.index.{i} =
> language:dc.language:controlledVocabularyMultilingual in dspace.cfg.
> In this case, the same items will be found if someone searches by language
> for the word 'Spanish' or the word 'spa' or the word 'Ισπανικά' if the
> repository supports the English and Greek locale.
> e.g. (search for 'Greek' or 'Ελληνικά' as search type Language)
> http://repository.edulll.gr/edulll/advanced-search
> Important Note: The support of multilingual displayed values by the
> submission form, is an on-going work from National Documention Centre, which
> will be included in another patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
[Dspace-devel] [DuraSpace JIRA] (DS-1223) Display frequencies of items in single browsing for selected indices
[ https://jira.duraspace.org/browse/DS-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26243#comment-26243 ] Andrea Bollini commented on DS-1223: I have done the Oracle test, minor changes required. Kostas and I are doing the merge now... > Display frequencies of items in single browsing for selected indices > > > Key: DS-1223 > URL: https://jira.duraspace.org/browse/DS-1223 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Affects Versions: 1.8.2 >Reporter: Christina Paschou > Labels: has-patch, has-pull-request > Attachments: browse_frequencies.diff, README.txt > > > DSpace provides by default two types of browsing, naming them single browsing > and full browsing according to the corresponding names of the .jsp files that > are responsible for handling each request (single.jsp & full.jsp). > Each type of browsing is defined accordingly and configured in different way > in the configuration file dspace.cfg. > The proposed improvement is applied for the case of browsing by a unique > index of metadata values from the item (single browsing). In this case, the > user can define for each metadata browse index whether he wishes to add next > to its various metadata values the frequencies of items that are included. > The configuration takes place in the dspace.cfg. > Examples: > http://phdtheses.ekt.gr/eadd/browse?type=subject > http://phdtheses.ekt.gr/eadd/browse?type=country > http://phdtheses.ekt.gr/eadd/browse?type=language > Attached you can find the patch file and a readme file with details about tha > configuration that is needed to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1231) Index (for search) both display and stored values for fields using controlled vocabularies
[
https://jira.duraspace.org/browse/DS-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Bollini updated DS-1231:
---
Status: Open (was: Received)
> Index (for search) both display and stored values for fields using controlled
> vocabularies
> ---
>
> Key: DS-1231
> URL: https://jira.duraspace.org/browse/DS-1231
> Project: DSpace
> Issue Type: Improvement
> Components: DSpace API
>Affects Versions: 1.8.2
>Reporter: Rania Stathopoulou
> Labels: has-patch, has-pull-request
> Attachments: README.txt, search_index_ControlledVocabulary
>
>
> In submission process, when the "input-type" of an element is set to
> "dropdown" (/dspace/config/input-forms.xml),
> by default DSpace stores the "stored-value" and shows the "displayed-value"
> in submission form.
> Nevertheless, in order for a user to find the item he must knows the
> "stored-value", since only this value is indexed.
> The proposed improvement is applied in order to index both the
> "displayed-value" and the "stored-value" of an item.
> Specifically, the user can set if he wants also to index the displayed-value
> in Fields to Index for Search by setting 'controlledVocabulary'
> or 'controlledVocabularyMultilingual' as value for [type] property for a
> respective search index.
> There are two options:
> a) put 'controlledVocabulary' next to the respective search index field in
> dspace.cfg, so both the "stored-value(s)" and the respective
> "displayed-value(s)" will be indexed
> b) put 'controlledVocabularyMultilingual' next to the respective search index
> field in dspace.cfg, so both the "stored-value(s)" and the respective
> localized "displayed-value(s)" will be indexed for all the repository
> supported locales.
> In this case, the displayed-value(s) are set as message keys and the message
> values must be set in message.properties for each language supported by the
> repository.
> -
> EXAMPLES
> -
> a) When in input forms we have:
>
> dc
> language
>
> true
> Type
> dropdown
> Select the language(s) of content of the item. To select more
> than one value in the list, you may have to hold down the "CTRL" or "Shift"
> key.
>
>
> where:
>
>
> Greek
> gre
>
>
> English
> eng
>
>
> French
> fre
>
>
> German
> ger
>
>
> Spanish
> spa
>
> ...
>
> Then, if we want to index the languages, we should put search.index.{i} =
> language:dc.language:controlledVocabulary in dspace.cfg.
> In this case, the same items will be found if someones searches by language
> for the word 'Spanish' or the word 'spa'.
> a) When in input forms we have:
>
> dc
> language
>
> true
> Type
> value-pairs-name="common_languages_Multilingual">dropdown
> Select the language(s) of content of the item. To select more
> than one value in the list, you may have to hold down the "CTRL" or "Shift"
> key.
>
>
> where:
> dc-term="language_iso">
>
> jsp.self-archive.dc.language.gre
> gre
>
>
> jsp.self-archive.dc.language.eng
> eng
>
>
> jsp.self-archive.dc.language.fre
> fre
>
>
> jsp.self-archive.dc.language.ger
> ger
>
>
> jsp.self-archive.dc.language.spa
> spa
>
> ...
>
> Then, if we want to index the languages, we should put search.index.{i} =
> language:dc.language:controlledVocabularyMultilingual in dspace.cfg.
> In this case, the same items will be found if someone searches by language
> for the word 'Spanish' or the word 'spa' or the word 'Ισπανικά' if the
> repository supports the English and Greek locale.
> e.g. (search for 'Greek' or 'Ελληνικά' as search type Language)
> http://repository.edulll.gr/edulll/advanced-search
> Important Note: The support of multilingual displayed values by the
> submission form, is an on-going work from National Documention Centre, which
> will be included in another patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile secu
[Dspace-devel] [DuraSpace JIRA] (DS-1227) Tag cloud for any browse index in the home page of DSpace
[ https://jira.duraspace.org/browse/DS-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1227: --- Assignee: Andrea Bollini (was: Sands Fish) Status: Open (was: Received) this contribution need to be postponed to the next DSpace release (4.0). The following changes are required: 1) the browse API doesn't need to be changed in this way. Tag Cloud need to perform a metadata browse sorted by count (this is the only required extension to the browse API) ASC with unlimited pagination starting from the cutting level (similar to a jump to a letter in browse by author) 2) the home.jsp is messy, default configuration should be read directly in the tag library. I suggest to add an attribute that allow the user to choose the style to apply (i.e. using home some properties with ".home." inside will be used) 3) the browse processing should be invoked by a plugin (SiteProcessor, CollectionProcessor, etc.) and not directly in the jsp - similar to the recent submission code > Tag cloud for any browse index in the home page of DSpace > - > > Key: DS-1227 > URL: https://jira.duraspace.org/browse/DS-1227 > Project: DSpace > Issue Type: New Feature > Components: JSPUI >Reporter: Kostas Stamatis >Assignee: Andrea Bollini > Labels: has-patch, has-pull-request, tag-cloud > Attachments: opencloud.jar, README.txt, tagcloud-patch.diff > > > This proposed extension (implemented by National Documentation Centre/EKT - > http://www.ekt.gr) allows the import of a tag cloud in the homepage of DSpace. > The tag cloud can include values from any of the browse indices (of metadata > type) of the repository and this is a configuration option along with many > other options that you can see later. > Tha tag cloud is implemented as a tag, meaning that it can be included in any > page of the DSpace repository besides the homepage. > USEFULNESS > - > Select a important browse index of your repository (i.e. subject) and include > all major subjects of your records in the home page of DSpace to attract > visitors. > CONFIGURATION FILES > --- > Tag cloud is fully configurable within the default dspace.cfg configuration > file of DSpace. The new configuration options are: > ### > # TAG CLOUD configuration # > ### > # > # Should display tag cloud in the home page? > # Possible values: true | false > webui.tagcloud.home.show = true > # > # Select the browse index to create a tag cloud for in the home page > # Possible values: any of the browse indices declared earlier in this conf > file > webui.tagcloud.home.bindex = subject > # > # Select the total tags to show > # Possible values: any integer from 1 to infinity > webui.tagcloud.home.maxtags = 50 > # > # Should display the score next to each tag? > # Possible values: true | false > webui.tagcloud.home.showscore = false > # > # The score that tags with lower than that will not appear in the rag cloud > # Possible values: any integer from 1 to infinity > webui.tagcloud.home.cutlevel = 5 > # > # Should display the tag as center aligned in the page or left aligned? > # Possible values: true | false > webui.tagcloud.home.showcenter = true > # > # The font size (in em) for the tag with the lowest score > # Possible values: any decimal > webui.tagcloud.home.fontfrom = 1.3 > # > # The font size (in em) for the tag with the highest score > # Possible values: any decimal > webui.tagcloud.home.fontto = 2.8 > # > # The case of the tags > # Possible values: Case.LOWER | Case.UPPER | Case.CAPITALIZATION | > Case.PRESERVE_CASE | Case.CASE_SENSITIVE > webui.tagcloud.home.tagcase = Case.PRESERVE_CASE > # > # If the 3 colors of the tag cloud should be independent of score > (random=yes) or based on the score > # Possible values: true | false > webui.tagcloud.home.randomcolors = true > # > # The ordering of the tags (based either on the name or the score of the tag) > # Possible values: Tag.NameComparatorAsc | Tag.NameComparatorDesc | > Tag.ScoreComparatorAsc | Tag.ScoreComparatorDesc > webui.tagcloud.home.tagorder = Tag.NameComparatorAsc > # > # The first color of the tags > # Possible values: hex value of the color (i.e. e3d67a) > webui.tagcloud.home.tagcolor1 = D96C27 > # > # The second color of the tags > # Possible values: hex value of the color (i.e. e3d67a) > webui.tagcloud.home.tagcolor2 = 424242 > # > # The third color of the tags > # Possible values: hex value of the color (i.e. e3d67a) > webui.tagcloud.home.tagcolor3 = 818183 > EXTERNAL LIBRARIES > -- > This extension makes use of the following external java library
[Dspace-devel] [DuraSpace JIRA] (DS-1227) Tag cloud for any browse index in the home page of DSpace
[ https://jira.duraspace.org/browse/DS-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1227: --- Fix Version/s: 4.0 > Tag cloud for any browse index in the home page of DSpace > - > > Key: DS-1227 > URL: https://jira.duraspace.org/browse/DS-1227 > Project: DSpace > Issue Type: New Feature > Components: JSPUI >Reporter: Kostas Stamatis >Assignee: Andrea Bollini > Labels: has-patch, has-pull-request, tag-cloud > Fix For: 4.0 > > Attachments: opencloud.jar, README.txt, tagcloud-patch.diff > > > This proposed extension (implemented by National Documentation Centre/EKT - > http://www.ekt.gr) allows the import of a tag cloud in the homepage of DSpace. > The tag cloud can include values from any of the browse indices (of metadata > type) of the repository and this is a configuration option along with many > other options that you can see later. > Tha tag cloud is implemented as a tag, meaning that it can be included in any > page of the DSpace repository besides the homepage. > USEFULNESS > - > Select a important browse index of your repository (i.e. subject) and include > all major subjects of your records in the home page of DSpace to attract > visitors. > CONFIGURATION FILES > --- > Tag cloud is fully configurable within the default dspace.cfg configuration > file of DSpace. The new configuration options are: > ### > # TAG CLOUD configuration # > ### > # > # Should display tag cloud in the home page? > # Possible values: true | false > webui.tagcloud.home.show = true > # > # Select the browse index to create a tag cloud for in the home page > # Possible values: any of the browse indices declared earlier in this conf > file > webui.tagcloud.home.bindex = subject > # > # Select the total tags to show > # Possible values: any integer from 1 to infinity > webui.tagcloud.home.maxtags = 50 > # > # Should display the score next to each tag? > # Possible values: true | false > webui.tagcloud.home.showscore = false > # > # The score that tags with lower than that will not appear in the rag cloud > # Possible values: any integer from 1 to infinity > webui.tagcloud.home.cutlevel = 5 > # > # Should display the tag as center aligned in the page or left aligned? > # Possible values: true | false > webui.tagcloud.home.showcenter = true > # > # The font size (in em) for the tag with the lowest score > # Possible values: any decimal > webui.tagcloud.home.fontfrom = 1.3 > # > # The font size (in em) for the tag with the highest score > # Possible values: any decimal > webui.tagcloud.home.fontto = 2.8 > # > # The case of the tags > # Possible values: Case.LOWER | Case.UPPER | Case.CAPITALIZATION | > Case.PRESERVE_CASE | Case.CASE_SENSITIVE > webui.tagcloud.home.tagcase = Case.PRESERVE_CASE > # > # If the 3 colors of the tag cloud should be independent of score > (random=yes) or based on the score > # Possible values: true | false > webui.tagcloud.home.randomcolors = true > # > # The ordering of the tags (based either on the name or the score of the tag) > # Possible values: Tag.NameComparatorAsc | Tag.NameComparatorDesc | > Tag.ScoreComparatorAsc | Tag.ScoreComparatorDesc > webui.tagcloud.home.tagorder = Tag.NameComparatorAsc > # > # The first color of the tags > # Possible values: hex value of the color (i.e. e3d67a) > webui.tagcloud.home.tagcolor1 = D96C27 > # > # The second color of the tags > # Possible values: hex value of the color (i.e. e3d67a) > webui.tagcloud.home.tagcolor2 = 424242 > # > # The third color of the tags > # Possible values: hex value of the color (i.e. e3d67a) > webui.tagcloud.home.tagcolor3 = 818183 > EXTERNAL LIBRARIES > -- > This extension makes use of the following external java library: > a) opencloud |(http://opencloud.mcavallo.org/): a java library for for > generating and managing tag clouds (under MIT licence) > EXAMPLES > --- > Repository: Managing Authority of the Operational Programme "Education and > Lifelong Learning" > URL: http://repository.edulll.gr/edulll/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://ww
[Dspace-devel] [DuraSpace JIRA] (DS-1268) Wrong URL for OpenSearch description.xml document
[ https://jira.duraspace.org/browse/DS-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26280#comment-26280 ] Andrea Bollini commented on DS-1268: Please create a new pull request. Thanks, Andrea > Wrong URL for OpenSearch description.xml document > - > > Key: DS-1268 > URL: https://jira.duraspace.org/browse/DS-1268 > Project: DSpace > Issue Type: Bug > Components: Discovery, XMLUI >Affects Versions: 1.8.2, 3.0 >Reporter: Nestor Oviedo >Priority: Major > Labels: description.xml, discovery, open-search > > The recently merged and closed pull request > https://github.com/DSpace/DSpace/pull/80 (fixing the problem with OpenSearch > and Discovery) introduced a little bug on the rendering of the URL for the > description.xml document. > Originally, the websvc.opensearch.svccontext config property's value was > "open-search/". The problem is that class > org.dspace.app.xmlui.aspect.viewArtifacts.Navigation reads that property and > creates a dri:pageMeta/dri:metadata element with it and the buildHead > template (in page-structure.xsl) adds the "description.xml" string to it to > render the autodiscovery link. > After the pull request #80, when you have discovery enabled you should change > the mentioned property to "open-search/discover", resulting in the URL > "open-search/discoverdescription.xml" URL for the description document, which > is wrong. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1218) BrowseDAO based on discovery
[ https://jira.duraspace.org/browse/DS-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1218: --- Documentation Status: Complete or Committed (was: Needed) > BrowseDAO based on discovery > > > Key: DS-1218 > URL: https://jira.duraspace.org/browse/DS-1218 > Project: DSpace > Issue Type: New Feature > Components: Discovery >Reporter: Andrea Bollini >Assignee: Andrea Bollini >Priority: Major > Labels: has-pull-request > Fix For: 3.0 > > > Implementation of the BrowseDAO classes to use the data in the SOLR search > core (dspace-discovery) instead of Database query. > This contribution is supported by the University of Hong Kong that has > adopted the first version of this code since July 2010 > Software development by the CILEA SURplus Team (http://www.cilea.it) > Example: http://hub.hku.hk/browse?type=title -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1217) DSpace Discovery for JSPUI
[ https://jira.duraspace.org/browse/DS-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1217: --- Documentation Status: Complete or Committed (was: Needed) > DSpace Discovery for JSPUI > -- > > Key: DS-1217 > URL: https://jira.duraspace.org/browse/DS-1217 > Project: DSpace > Issue Type: New Feature > Components: Discovery, JSPUI >Reporter: Andrea Bollini >Assignee: Andrea Bollini >Priority: Major > Labels: has-pull-request > Fix For: 3.0 > > > Porting of the discovery features (SOLR Search) to the JSPUI. > This contribution is supported by the University of Hong Kong that has > adopted the first version of this code since July 2010 > Software development by the CILEA SURplus Team (http://www.cilea.it) > Example: http://hub.hku.hk/simple-search?sort_by=1&query=&submit=search -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1217) DSpace Discovery for JSPUI
[ https://jira.duraspace.org/browse/DS-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26368#comment-26368 ] Andrea Bollini commented on DS-1217: updated the wiki page: https://wiki.duraspace.org/display/DSDOC3x/Discovery > DSpace Discovery for JSPUI > -- > > Key: DS-1217 > URL: https://jira.duraspace.org/browse/DS-1217 > Project: DSpace > Issue Type: New Feature > Components: Discovery, JSPUI >Reporter: Andrea Bollini >Assignee: Andrea Bollini >Priority: Major > Labels: has-pull-request > Fix For: 3.0 > > > Porting of the discovery features (SOLR Search) to the JSPUI. > This contribution is supported by the University of Hong Kong that has > adopted the first version of this code since July 2010 > Software development by the CILEA SURplus Team (http://www.cilea.it) > Example: http://hub.hku.hk/simple-search?sort_by=1&query=&submit=search -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1218) BrowseDAO based on discovery
[ https://jira.duraspace.org/browse/DS-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26369#comment-26369 ] Andrea Bollini commented on DS-1218: documentation: https://wiki.duraspace.org/display/DSDOC3x/Configuration#Configuration-BrowseIndexConfiguration > BrowseDAO based on discovery > > > Key: DS-1218 > URL: https://jira.duraspace.org/browse/DS-1218 > Project: DSpace > Issue Type: New Feature > Components: Discovery >Reporter: Andrea Bollini >Assignee: Andrea Bollini >Priority: Major > Labels: has-pull-request > Fix For: 3.0 > > > Implementation of the BrowseDAO classes to use the data in the SOLR search > core (dspace-discovery) instead of Database query. > This contribution is supported by the University of Hong Kong that has > adopted the first version of this code since July 2010 > Software development by the CILEA SURplus Team (http://www.cilea.it) > Example: http://hub.hku.hk/browse?type=title -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1294) Autocomplete in discovery filter doesn't work
Andrea Bollini created DS-1294: -- Summary: Autocomplete in discovery filter doesn't work Key: DS-1294 URL: https://jira.duraspace.org/browse/DS-1294 Project: DSpace Issue Type: Bug Components: JSPUI Affects Versions: 3.0 Reporter: Andrea Bollini Assignee: Andrea Bollini Fix For: 3.0 The user input filter in JSPUI discovery should allow autocomplete. The JSON endpoint is misconfigured in the dspace.cfg -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1294) Autocomplete in discovery filter doesn't work
[ https://jira.duraspace.org/browse/DS-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1294: --- Documentation Status: (was: Needed) Status: Open (was: Received) > Autocomplete in discovery filter doesn't work > - > > Key: DS-1294 > URL: https://jira.duraspace.org/browse/DS-1294 > Project: DSpace > Issue Type: Bug > Components: JSPUI >Affects Versions: 3.0 >Reporter: Andrea Bollini >Assignee: Andrea Bollini > Fix For: 3.0 > > > The user input filter in JSPUI discovery should allow autocomplete. The JSON > endpoint is misconfigured in the dspace.cfg -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1294) Autocomplete in discovery filter doesn't work
[ https://jira.duraspace.org/browse/DS-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1294: --- Labels: has-pull-request (was: ) https://github.com/DSpace/DSpace/pull/98 > Autocomplete in discovery filter doesn't work > - > > Key: DS-1294 > URL: https://jira.duraspace.org/browse/DS-1294 > Project: DSpace > Issue Type: Bug > Components: JSPUI >Affects Versions: 3.0 >Reporter: Andrea Bollini >Assignee: Andrea Bollini > Labels: has-pull-request > Fix For: 3.0 > > > The user input filter in JSPUI discovery should allow autocomplete. The JSON > endpoint is misconfigured in the dspace.cfg -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1294) Autocomplete in discovery filter doesn't work
[ https://jira.duraspace.org/browse/DS-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini resolved DS-1294. Resolution: Fixed > Autocomplete in discovery filter doesn't work > - > > Key: DS-1294 > URL: https://jira.duraspace.org/browse/DS-1294 > Project: DSpace > Issue Type: Bug > Components: JSPUI >Affects Versions: 3.0 >Reporter: Andrea Bollini >Assignee: Andrea Bollini > Labels: has-pull-request > Fix For: 3.0 > > > The user input filter in JSPUI discovery should allow autocomplete. The JSON > endpoint is misconfigured in the dspace.cfg -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1297) org.dspace.core.PluginInstantiationException: Cannot load plugin class: java.lang.ClassNotFoundException: org.dspace.app.webui.search.LuceneSearchRequestProce
[ https://jira.duraspace.org/browse/DS-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1297: --- Component/s: JSPUI > org.dspace.core.PluginInstantiationException: Cannot load plugin class: > java.lang.ClassNotFoundException: > org.dspace.app.webui.search.LuceneSearchRequestProcessor > -- > > Key: DS-1297 > URL: https://jira.duraspace.org/browse/DS-1297 > Project: DSpace > Issue Type: Bug > Components: JSPUI > Environment: *Location*: http://demo.dspace.org/ > *User-Agent*: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.4 (KHTML, like > Gecko) Chrome/22.0.1229.94 Safari/537.4 > *Screen Resolution*: 1680 x 1050 >Reporter: Keiji Suzuki >Assignee: Andrea Bollini > Labels: collector-60e7afac > > When you search in JSPUI without discovery, this error is occured. The reason > why is the class name in the default dspace.cfg is wrong. > The line 1109 to 1110 say, > plugin.single.org.dspace.app.webui.search.SearchRequestProcessor = \ > org.dspace.app.webui.search.LuceneSearchRequestProcessor > but "org.dspace.app.webui.search.LuceneSearchProcessor" is right. > *Reporter*: Keiji Suzuki > *E-mail*: [mailto:zuki.ebe...@gmail.com] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1297) org.dspace.core.PluginInstantiationException: Cannot load plugin class: java.lang.ClassNotFoundException: org.dspace.app.webui.search.LuceneSearchRequestProce
[ https://jira.duraspace.org/browse/DS-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1297: --- Status: Open (was: Received) > org.dspace.core.PluginInstantiationException: Cannot load plugin class: > java.lang.ClassNotFoundException: > org.dspace.app.webui.search.LuceneSearchRequestProcessor > -- > > Key: DS-1297 > URL: https://jira.duraspace.org/browse/DS-1297 > Project: DSpace > Issue Type: Bug > Components: JSPUI > Environment: *Location*: http://demo.dspace.org/ > *User-Agent*: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.4 (KHTML, like > Gecko) Chrome/22.0.1229.94 Safari/537.4 > *Screen Resolution*: 1680 x 1050 >Reporter: Keiji Suzuki >Assignee: Andrea Bollini > Labels: collector-60e7afac > > When you search in JSPUI without discovery, this error is occured. The reason > why is the class name in the default dspace.cfg is wrong. > The line 1109 to 1110 say, > plugin.single.org.dspace.app.webui.search.SearchRequestProcessor = \ > org.dspace.app.webui.search.LuceneSearchRequestProcessor > but "org.dspace.app.webui.search.LuceneSearchProcessor" is right. > *Reporter*: Keiji Suzuki > *E-mail*: [mailto:zuki.ebe...@gmail.com] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-944) Authority Control Bug
[ https://jira.duraspace.org/browse/DS-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-944: -- Affects Version/s: 1.8.2 > Authority Control Bug > - > > Key: DS-944 > URL: https://jira.duraspace.org/browse/DS-944 > Project: DSpace > Issue Type: Bug >Affects Versions: 1.6.2, 1.7.2, 1.8.2 > Environment: Unix >Reporter: João Melo >Assignee: Andrea Bollini > > There is a bug using authority controls with firefox 4.0, IE 9, Chrome (for > Mac) - the only tested. > The list of items is retrieved from the server but isn't shown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-944) Authority Control Bug
[ https://jira.duraspace.org/browse/DS-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-944: -- Assignee: Andrea Bollini Status: Open (was: Received) > Authority Control Bug > - > > Key: DS-944 > URL: https://jira.duraspace.org/browse/DS-944 > Project: DSpace > Issue Type: Bug >Affects Versions: 1.6.2, 1.7.2, 1.8.2 > Environment: Unix >Reporter: João Melo >Assignee: Andrea Bollini > > There is a bug using authority controls with firefox 4.0, IE 9, Chrome (for > Mac) - the only tested. > The list of items is retrieved from the server but isn't shown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1381) Javascript errors in all pages
Andrea Bollini created DS-1381: -- Summary: Javascript errors in all pages Key: DS-1381 URL: https://jira.duraspace.org/browse/DS-1381 Project: DSpace Issue Type: Bug Components: JSPUI Affects Versions: 3.0 Reporter: Andrea Bollini Priority: Critical In all pages there is a javascript error TypeError: element.dispatchEvent is not a function [Interrompi per questo errore] element.dispatchEvent(event); This is due to the import of both the javascript library: Prototype and JQuery. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1297) org.dspace.core.PluginInstantiationException: Cannot load plugin class: java.lang.ClassNotFoundException: org.dspace.app.webui.search.LuceneSearchRequestProce
[ https://jira.duraspace.org/browse/DS-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini resolved DS-1297. Documentation Status: Not Required Resolution: Fixed Fix Version/s: 3.0 Fixed renaming the class according to the dspace.cfg The class name in dspace.cfg is "better" because it is consistent with the Discovery processor class name and SearchRequestProcessor Interface name > org.dspace.core.PluginInstantiationException: Cannot load plugin class: > java.lang.ClassNotFoundException: > org.dspace.app.webui.search.LuceneSearchRequestProcessor > -- > > Key: DS-1297 > URL: https://jira.duraspace.org/browse/DS-1297 > Project: DSpace > Issue Type: Bug > Components: JSPUI > Environment: *Location*: http://demo.dspace.org/ > *User-Agent*: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.4 (KHTML, like > Gecko) Chrome/22.0.1229.94 Safari/537.4 > *Screen Resolution*: 1680 x 1050 >Reporter: Keiji Suzuki >Assignee: Andrea Bollini > Labels: collector-60e7afac > Fix For: 3.0 > > > When you search in JSPUI without discovery, this error is occured. The reason > why is the class name in the default dspace.cfg is wrong. > The line 1109 to 1110 say, > plugin.single.org.dspace.app.webui.search.SearchRequestProcessor = \ > org.dspace.app.webui.search.LuceneSearchRequestProcessor > but "org.dspace.app.webui.search.LuceneSearchProcessor" is right. > *Reporter*: Keiji Suzuki > *E-mail*: [mailto:zuki.ebe...@gmail.com] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-944) Authority Control Bug
[ https://jira.duraspace.org/browse/DS-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-944: -- Component/s: JSPUI > Authority Control Bug > - > > Key: DS-944 > URL: https://jira.duraspace.org/browse/DS-944 > Project: DSpace > Issue Type: Bug > Components: JSPUI >Affects Versions: 1.6.2, 1.7.2, 1.8.2 > Environment: Unix >Reporter: João Melo >Assignee: Andrea Bollini > > There is a bug using authority controls with firefox 4.0, IE 9, Chrome (for > Mac) - the only tested. > The list of items is retrieved from the server but isn't shown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-944) Authority Control Bug
[ https://jira.duraspace.org/browse/DS-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26840#comment-26840 ] Andrea Bollini commented on DS-944: --- the bug is present also in the 3.0 (see also DS-1381) I have a fix for this (suggest authority feature rewrite with jquery) that is currently available on the CILEA/DSpace github repository (branch dspace_1.8.x_cris) I will open a pull request as soon as I will have access to my laptop (1-2 days) > Authority Control Bug > - > > Key: DS-944 > URL: https://jira.duraspace.org/browse/DS-944 > Project: DSpace > Issue Type: Bug > Components: JSPUI >Affects Versions: 1.6.2, 1.7.2, 1.8.2 > Environment: Unix >Reporter: João Melo >Assignee: Andrea Bollini > > There is a bug using authority controls with firefox 4.0, IE 9, Chrome (for > Mac) - the only tested. > The list of items is retrieved from the server but isn't shown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1381) Javascript errors in all pages
[ https://jira.duraspace.org/browse/DS-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1381: --- Documentation Status: Not Required (was: Needed) Assignee: Andrea Bollini Status: Open (was: Received) fix ready, I will commit within the next 2 days > Javascript errors in all pages > -- > > Key: DS-1381 > URL: https://jira.duraspace.org/browse/DS-1381 > Project: DSpace > Issue Type: Bug > Components: JSPUI >Affects Versions: 3.0 >Reporter: Andrea Bollini >Assignee: Andrea Bollini >Priority: Critical > > In all pages there is a javascript error > TypeError: element.dispatchEvent is not a function > [Interrompi per questo errore] > element.dispatchEvent(event); > This is due to the import of both the javascript library: Prototype and > JQuery. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1378) Anomalies & Duplicated entries with two simultaneous controlled vocabularies
[ https://jira.duraspace.org/browse/DS-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1378: --- Affects Version/s: 1.8.0 1.8.1 > Anomalies & Duplicated entries with two simultaneous controlled vocabularies > > > Key: DS-1378 > URL: https://jira.duraspace.org/browse/DS-1378 > Project: DSpace > Issue Type: Bug > Components: DSpace API, JSPUI >Affects Versions: 1.8.0, 1.8.1, 1.8.2 > Environment: CentOS 6.2, Ubuntu 10.04, PostgresQL >Reporter: emilio lorenzo >Assignee: Andrea Bollini >Priority: Major > Attachments: problema edición subject.png > > > from dspace.cfg: > plugin.selfnamed.org.dspace.content.authority.ChoiceAuthority = \ > org.dspace.content.authority.DSpaceControlledVocabulary > choices.plugin.dc.subject.unesco = unesco > choices.presentation.dc.subject.unesco = suggest > The ingest process (via input-forms.xml) works OK > But when EDITing the item, every time you try to change the > dc.subject.unesco field, TWO (always pairs of values) new dc.subject (not > dc.subject.unesco) fields are added WITH numeric values. ??? > See screen capture > (In Dspace 1.6.2 we replicated the problem with AuthorityControlled Field ie > with the plugin.named.org.dspace.content.authority.ChoiceAuthority -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1378) Anomalies & Duplicated entries with two simultaneous controlled vocabularies
[ https://jira.duraspace.org/browse/DS-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1378: --- Documentation Status: (was: Needed) Assignee: Andrea Bollini Status: Open (was: Received) > Anomalies & Duplicated entries with two simultaneous controlled vocabularies > > > Key: DS-1378 > URL: https://jira.duraspace.org/browse/DS-1378 > Project: DSpace > Issue Type: Bug > Components: DSpace API, JSPUI >Affects Versions: 1.8.0, 1.8.1, 1.8.2 > Environment: CentOS 6.2, Ubuntu 10.04, PostgresQL >Reporter: emilio lorenzo >Assignee: Andrea Bollini >Priority: Major > Attachments: problema edición subject.png > > > from dspace.cfg: > plugin.selfnamed.org.dspace.content.authority.ChoiceAuthority = \ > org.dspace.content.authority.DSpaceControlledVocabulary > choices.plugin.dc.subject.unesco = unesco > choices.presentation.dc.subject.unesco = suggest > The ingest process (via input-forms.xml) works OK > But when EDITing the item, every time you try to change the > dc.subject.unesco field, TWO (always pairs of values) new dc.subject (not > dc.subject.unesco) fields are added WITH numeric values. ??? > See screen capture > (In Dspace 1.6.2 we replicated the problem with AuthorityControlled Field ie > with the plugin.named.org.dspace.content.authority.ChoiceAuthority -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1378) Anomalies & Duplicated entries using the lookup authority feature in edit-item
[ https://jira.duraspace.org/browse/DS-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1378: --- Summary: Anomalies & Duplicated entries using the lookup authority feature in edit-item (was: Anomalies & Duplicated entries with two simultaneous controlled vocabularies) > Anomalies & Duplicated entries using the lookup authority feature in edit-item > -- > > Key: DS-1378 > URL: https://jira.duraspace.org/browse/DS-1378 > Project: DSpace > Issue Type: Bug > Components: DSpace API, JSPUI >Affects Versions: 1.8.0, 1.8.1, 1.8.2 > Environment: CentOS 6.2, Ubuntu 10.04, PostgresQL >Reporter: emilio lorenzo >Assignee: Andrea Bollini >Priority: Major > Attachments: problema edición subject.png > > > from dspace.cfg: > plugin.selfnamed.org.dspace.content.authority.ChoiceAuthority = \ > org.dspace.content.authority.DSpaceControlledVocabulary > choices.plugin.dc.subject.unesco = unesco > choices.presentation.dc.subject.unesco = suggest > The ingest process (via input-forms.xml) works OK > But when EDITing the item, every time you try to change the > dc.subject.unesco field, TWO (always pairs of values) new dc.subject (not > dc.subject.unesco) fields are added WITH numeric values. ??? > See screen capture > (In Dspace 1.6.2 we replicated the problem with AuthorityControlled Field ie > with the plugin.named.org.dspace.content.authority.ChoiceAuthority -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1381) Javascript errors in all pages
[ https://jira.duraspace.org/browse/DS-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini resolved DS-1381. Resolution: Fixed > Javascript errors in all pages > -- > > Key: DS-1381 > URL: https://jira.duraspace.org/browse/DS-1381 > Project: DSpace > Issue Type: Bug > Components: JSPUI >Affects Versions: 3.0 >Reporter: Andrea Bollini >Assignee: Andrea Bollini >Priority: Critical > Fix For: 3.0 > > > In all pages there is a javascript error > TypeError: element.dispatchEvent is not a function > [Interrompi per questo errore] > element.dispatchEvent(event); > This is due to the import of both the javascript library: Prototype and > JQuery. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1378) Anomalies & Duplicated entries using the lookup authority feature in edit-item
[ https://jira.duraspace.org/browse/DS-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini resolved DS-1378. Resolution: Fixed Fix Version/s: 3.0 > Anomalies & Duplicated entries using the lookup authority feature in edit-item > -- > > Key: DS-1378 > URL: https://jira.duraspace.org/browse/DS-1378 > Project: DSpace > Issue Type: Bug > Components: DSpace API, JSPUI >Affects Versions: 1.8.0, 1.8.1, 1.8.2 > Environment: CentOS 6.2, Ubuntu 10.04, PostgresQL >Reporter: emilio lorenzo >Assignee: Andrea Bollini >Priority: Major > Fix For: 3.0 > > Attachments: problema edición subject.png > > > from dspace.cfg: > plugin.selfnamed.org.dspace.content.authority.ChoiceAuthority = \ > org.dspace.content.authority.DSpaceControlledVocabulary > choices.plugin.dc.subject.unesco = unesco > choices.presentation.dc.subject.unesco = suggest > The ingest process (via input-forms.xml) works OK > But when EDITing the item, every time you try to change the > dc.subject.unesco field, TWO (always pairs of values) new dc.subject (not > dc.subject.unesco) fields are added WITH numeric values. ??? > See screen capture > (In Dspace 1.6.2 we replicated the problem with AuthorityControlled Field ie > with the plugin.named.org.dspace.content.authority.ChoiceAuthority -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-944) Authority Control Bug
[ https://jira.duraspace.org/browse/DS-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26871#comment-26871 ] Andrea Bollini commented on DS-944: --- Hi João, can you review my pull request? https://github.com/DSpace/DSpace/pull/130 > Authority Control Bug > - > > Key: DS-944 > URL: https://jira.duraspace.org/browse/DS-944 > Project: DSpace > Issue Type: Bug > Components: JSPUI >Affects Versions: 1.6.2, 1.7.2, 1.8.2 > Environment: Unix >Reporter: João Melo >Assignee: Andrea Bollini > > There is a bug using authority controls with firefox 4.0, IE 9, Chrome (for > Mac) - the only tested. > The list of items is retrieved from the server but isn't shown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-944) Authority Control Bug
[ https://jira.duraspace.org/browse/DS-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini resolved DS-944. --- Documentation Status: (was: Needed) Resolution: Fixed Fix Version/s: 3.0 merged https://github.com/DSpace/DSpace/pull/130 Tested on FF16, IE7, IE8, IE9, Chrome 23 > Authority Control Bug > - > > Key: DS-944 > URL: https://jira.duraspace.org/browse/DS-944 > Project: DSpace > Issue Type: Bug > Components: JSPUI >Affects Versions: 1.6.2, 1.7.2, 1.8.2 > Environment: Unix >Reporter: João Melo >Assignee: Andrea Bollini > Fix For: 3.0 > > > There is a bug using authority controls with firefox 4.0, IE 9, Chrome (for > Mac) - the only tested. > The list of items is retrieved from the server but isn't shown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1466) withdrawn and private items are indexed in Solr search
[ https://jira.duraspace.org/browse/DS-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27619#comment-27619 ] Andrea Bollini commented on DS-1466: I'm not able to reproduce the issue with withdrawn item. The issue IMHO is only present for private items. I have send a pull request to fix it, please note that I have had no time to test it but as far as I know it should work. https://github.com/DSpace/DSpace/pull/183 > withdrawn and private items are indexed in Solr search > -- > > Key: DS-1466 > URL: https://jira.duraspace.org/browse/DS-1466 > Project: DSpace > Issue Type: Bug > Components: Discovery >Affects Versions: 3.0 >Reporter: Ivan Masár >Assignee: Kevin Van de Velde >Priority: Major > Fix For: 3.1 > > > After withdrawing an item or making it private (discoverable=false), the item > still shows up in search results and recent items (XMLUI with Discovery). > Steps to reproduce: > 1) withdraw an item > 2) search for the item using Discovery > Expected result: > It doesn't show up in search results > Actual result: > It shows up in search results > Running update-discovery-index (even with the -c or -b parameter) doesn't > remove the item from index, either. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1080) Search results preview
[ https://jira.duraspace.org/browse/DS-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini closed DS-1080. -- Documentation Status: Complete or Committed (was: Needed) Resolution: Fixed Fix Version/s: 3.0 > Search results preview > -- > > Key: DS-1080 > URL: https://jira.duraspace.org/browse/DS-1080 > Project: DSpace > Issue Type: New Feature > Components: Discovery, XMLUI >Reporter: Howard Shand >Assignee: Mark Diggory >Priority: Major > Fix For: 3.0 > > Attachments: DRI-example.xml, example.jpg, Solr-Example.xml > > > Show a preview of search results. > When search results are based on full text search, show the keywords in their > context (with some highlighting) similar to the functionality of most search > engines. > Example of the system we were previously using is attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1466) withdrawn and private items are indexed in Solr search
[ https://jira.duraspace.org/browse/DS-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reassigned DS-1466: -- Assignee: Andrea Bollini (was: Kevin Van de Velde) > withdrawn and private items are indexed in Solr search > -- > > Key: DS-1466 > URL: https://jira.duraspace.org/browse/DS-1466 > Project: DSpace > Issue Type: Bug > Components: Discovery >Affects Versions: 3.0 >Reporter: Ivan Masár >Assignee: Andrea Bollini >Priority: Major > Fix For: 3.2 > > > After withdrawing an item or making it private (discoverable=false), the item > still shows up in search results and recent items (XMLUI with Discovery). > Steps to reproduce: > 1) withdraw an item > 2) search for the item using Discovery > Expected result: > It doesn't show up in search results > Actual result: > It shows up in search results > Running update-discovery-index (even with the -c or -b parameter) doesn't > remove the item from index, either. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1571) Dspace JSPUI discovery CRITICAL bug
[ https://jira.duraspace.org/browse/DS-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1571: --- Component/s: XMLUI > Dspace JSPUI discovery CRITICAL bug > --- > > Key: DS-1571 > URL: https://jira.duraspace.org/browse/DS-1571 > Project: DSpace > Issue Type: Bug > Components: JSPUI, XMLUI >Affects Versions: 3.0, 3.1 >Reporter: Denis Fdz >Assignee: Andrea Bollini >Priority: Blocker > Attachments: jspui-facet-dtissued.jpg, screen-capture.png, > xmlui-facet-dtissued.jpg > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Hi all, > I submitted some items to http://demo.dspace.org/jspui/ and I noticed that > discovery doesn't works fine. > If I have big ranges of dates, the nearest date range doesn't appear. > We should correct this as soon as posible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1571) Dspace JSPUI discovery CRITICAL bug
[ https://jira.duraspace.org/browse/DS-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1571: --- Attachment: jspui-facet-dtissued.jpg xmlui-facet-dtissued.jpg > Dspace JSPUI discovery CRITICAL bug > --- > > Key: DS-1571 > URL: https://jira.duraspace.org/browse/DS-1571 > Project: DSpace > Issue Type: Bug > Components: JSPUI, XMLUI >Affects Versions: 3.0, 3.1 >Reporter: Denis Fdz >Assignee: Andrea Bollini >Priority: Blocker > Attachments: jspui-facet-dtissued.jpg, screen-capture.png, > xmlui-facet-dtissued.jpg > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Hi all, > I submitted some items to http://demo.dspace.org/jspui/ and I noticed that > discovery doesn't works fine. > If I have big ranges of dates, the nearest date range doesn't appear. > We should correct this as soon as posible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1571) DSpace discovery CRITICAL bug when date facet produce range
[ https://jira.duraspace.org/browse/DS-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-1571: --- Summary: DSpace discovery CRITICAL bug when date facet produce range (was: Dspace JSPUI discovery CRITICAL bug) > DSpace discovery CRITICAL bug when date facet produce range > --- > > Key: DS-1571 > URL: https://jira.duraspace.org/browse/DS-1571 > Project: DSpace > Issue Type: Bug > Components: JSPUI, XMLUI >Affects Versions: 3.0, 3.1 >Reporter: Denis Fdz >Assignee: Andrea Bollini >Priority: Blocker > Attachments: jspui-facet-dtissued.jpg, screen-capture.png, > xmlui-facet-dtissued.jpg > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Hi all, > I submitted some items to http://demo.dspace.org/jspui/ and I noticed that > discovery doesn't works fine. > If I have big ranges of dates, the nearest date range doesn't appear. > We should correct this as soon as posible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1571) DSpace discovery CRITICAL bug when date facet produce range
[ https://jira.duraspace.org/browse/DS-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28348#comment-28348 ] Andrea Bollini commented on DS-1571: The bug is present in a sligthly different form also for XMLUI. The JSPUI is missing the nearest date range, XMLUI the second one (1800-1899) with the sample data. To reproduce just submit three items with 1650, 1750, 1850 as date.issued > DSpace discovery CRITICAL bug when date facet produce range > --- > > Key: DS-1571 > URL: https://jira.duraspace.org/browse/DS-1571 > Project: DSpace > Issue Type: Bug > Components: JSPUI, XMLUI >Affects Versions: 3.0, 3.1 >Reporter: Denis Fdz >Assignee: Andrea Bollini >Priority: Blocker > Attachments: jspui-facet-dtissued.jpg, screen-capture.png, > xmlui-facet-dtissued.jpg > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Hi all, > I submitted some items to http://demo.dspace.org/jspui/ and I noticed that > discovery doesn't works fine. > If I have big ranges of dates, the nearest date range doesn't appear. > We should correct this as soon as posible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1601) fulltext:[* TO *] discovery query throws exception
[
https://jira.duraspace.org/browse/DS-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28555#comment-28555
]
Andrea Bollini commented on DS-1601:
The issue is due to the highlighting component that is trying to rewrite the
range query in a bigger boolean query (all terms in your fulltext field).
Basic query without highlighting works differently because they are rewritten
as ConstantScoreQuery, see
http://lucene.472066.n3.nabble.com/maxClauseCount-Exception-tp3767435p3811329.html
We should try to "understand" such query and disable at runtime the highlighting
> fulltext:[* TO *] discovery query throws exception
> --
>
> Key: DS-1601
> URL: https://jira.duraspace.org/browse/DS-1601
> Project: DSpace
> Issue Type: Bug
> Components: Discovery
>Affects Versions: 3.0, 3.1
>Reporter: Ivan Masár
> Labels: discovery, highlighting, solr
>
> The fulltext:[* TO *] Discovery query can be used to find all items that have
> a bitstream. This used to work in DSpace 1.8, but is broken in DSpace 3 when
> search results highlighting is enabled.
> I was able to get it to work by setting maxClauseCount to 4096 (the default
> is 1024), but the query also took quite long.
> INFO: [search] webapp=/solr path=/select
> params={f.dc.title_hl.hl.fragsize=0&f.dc.title_hl.hl.snippets=5&sort=score+desc&hl.fl=dc.description.abstract_hl&hl.fl=dc.title_hl&hl.fl=dc.contributor.author_hl&hl.fl=fulltext_hl&f.fulltext_hl.hl.fragsize=250&wt=javabin&hl=true&rows=10&version=2&f.fulltext_hl.hl.snippets=2&f.dc.description.abstract_hl.hl.snippets=2&f.dc.contributor.author_hl.hl.snippets=5&start=0&q=fulltext:[*+TO+*]&f.dc.contributor.author_hl.hl.fragsize=0&hl.usePhraseHighlighter=true&fq=NOT(withdrawn:true)&fq=read:(g0)&f.dc.description.abstract_hl.hl.fragsize=250}
> hits=15863 status=500 QTime=3118
> Jul 12, 2013 5:03:35 PM org.apache.solr.common.SolrException log
> SEVERE: org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount
> is set to 1024
> at org.apache.lucene.search.BooleanQuery.add(BooleanQuery.java:136)
> at org.apache.lucene.search.BooleanQuery.add(BooleanQuery.java:127)
> at
> org.apache.lucene.search.ScoringRewrite$1.addClause(ScoringRewrite.java:51)
> at
> org.apache.lucene.search.ScoringRewrite$1.addClause(ScoringRewrite.java:41)
> at
> org.apache.lucene.search.ScoringRewrite$3.collect(ScoringRewrite.java:95)
> at
> org.apache.lucene.search.TermCollectingRewrite.collectTerms(TermCollectingRewrite.java:38)
> at
> org.apache.lucene.search.ScoringRewrite.rewrite(ScoringRewrite.java:93)
> at
> org.apache.lucene.search.MultiTermQuery.rewrite(MultiTermQuery.java:304)
> at
> org.apache.lucene.search.highlight.WeightedSpanTermExtractor.extract(WeightedSpanTermExtractor.java:158)
> at
> org.apache.lucene.search.highlight.WeightedSpanTermExtractor.getWeightedSpanTerms(WeightedSpanTermExtractor.java:385)
> at
> org.apache.lucene.search.highlight.QueryScorer.initExtractor(QueryScorer.java:217)
> at
> org.apache.lucene.search.highlight.QueryScorer.init(QueryScorer.java:185)
> at
> org.apache.lucene.search.highlight.Highlighter.getBestTextFragments(Highlighter.java:205)
> at
> org.apache.solr.highlight.DefaultSolrHighlighter.doHighlightingByHighlighter(DefaultSolrHighlighter.java:490)
> at
> org.apache.solr.highlight.DefaultSolrHighlighter.doHighlighting(DefaultSolrHighlighter.java:401)
> at
> org.apache.solr.handler.component.HighlightComponent.process(HighlightComponent.java:131)
> at
> org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:194)
> at
> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:129)
> at org.apache.solr.core.SolrCore.execute(SolrCore.java:1372)
> at
> org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:356)
> at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:252)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.dspace.solr.filters.LocalHostRestrictionFilter.doFilter(LocalHostRestrictionFilter.java:60)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at
> org.apache.catalina.core.StandardContextVal
[Dspace-devel] [DuraSpace JIRA] (DS-491) Ability to map collections to multiple communities
Andrea Bollini commented on DS-491 Ability to map collections to multiple communities Hi Kostas, I'm not particularly interested in this feature because we use the collection only to provide type based aggregation for items (article, book, etc.), so really in our case a collection don't need to be shared with other communities (often we only have a single top level community "Research materials", all other views by department, etc. can be provided using discover/browse). Anyway, I think that the best way to implement this feature is to mimic as much as possible the implementation of the item mapper, so: 1) a new permission for community and collection mapping should be added. By default the community admin (of the owning community) should be able to perform the mapping. The mapping UI tool should work primary at the community level, it will be nice if a move tool will be provided to (like the move feature in edit-item that is able to change the owning collection and change an existent mapping) 2) introduce the concept of "owningCommunity" 3) we already have problem with the current breadcrumb implementation, it doesn't respect the navigation history of the user: are you go to the item page from a browse, a search, from a mapped collection, etc. for the mapped items see for example http://demo.dspace.org/jspui/handle/10673/4 we only show the owning collection path in the breadcrumb 4) in this case IMHO it could be better if all the parent paths are shown, as this primary matter for the search box inside the collection home page that could be reached from different communities. Implementing this could be difficult so it could be also delayed to a future improvement. Finally, we need to pay attention to avoid cyclic graph in community - community - collection relationship Community ComA - Community ComB --- Collection ColA Community ComC -(map) Community ComA The community ComC should be not mappable in ComA or ComB. Hope this help, Andrea This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1272) Enable Discovery By Default in XMLUI
Andrea Bollini updated DS-1272 Enable Discovery By Default in XMLUI Change By: Andrea Bollini (31/Jul/13 8:19 PM) Summary: Enable Discovery By Default in XMLUI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1272) Enable Discovery By Default in XMLUI
Andrea Bollini updated DS-1272 Enable Discovery By Default in XMLUI Change By: Andrea Bollini (31/Jul/13 8:20 PM) Description: This Issue addresses configuration changes to support Discovery being enabled in DSpace XMLUI and JPSUI off the shelf in DSpace 3.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1611) Enable Discovery By Default in JSPUI
Andrea Bollini created DS-1611 Enable Discovery By Default in JSPUI Issue Type: Improvement Assignee: Andrea Bollini Components: Discovery, JSPUI Created: 31/Jul/13 8:22 PM Description: This Issue addresses configuration changes to support Discovery being enabled in DSpace JSPUI off the shelf in DSpace 4.0 As discovery will be the default for XMLUI (DS-1272) too, in this issue we will disable unnecessary consumer (search on )lucene Fix Versions: 4.0 Project: DSpace Priority: Minor Reporter: Andrea Bollini This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1611) Enable Discovery By Default in JSPUI
Andrea Bollini updated DS-1611 Enable Discovery By Default in JSPUI Change By: Andrea Bollini (31/Jul/13 8:49 PM) Status: Received Accepted This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1615) The message "The file is restricted" showed when attempting to login
Andrea Bollini closed DS-1615 as Cannot Reproduce The message "The file is restricted" showed when attempting to login Change By: Andrea Bollini (07/Aug/13 7:11 AM) Resolution: Cannot Reproduce Status: Received Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1615) The message "The file is restricted" showed when attempting to login
Andrea Bollini commented on DS-1615 The message "The file is restricted" showed when attempting to login Are you loggedin from a different windows? I'm not able to reproduce. If I try to access the bitstream after login (as dspacedemo+sub...@gmail.com ) I get the following message: This bitstream is restricted You do not have the credentials to access the restricted bitstream Hinari-Oare-Agora_Leaflet.pdf. The message that you have reported are shown to the user before login because DSpace can't know if the user will login as administrator or with an account with insufficient privileges. I will mark this bug as "cannot reproduce" please feel free to reopen if I have misunderstand something This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1616) Localhost is not longer supported as a valid URL Solr
Andrea Bollini created DS-1616 Localhost is not longer supported as a valid URL Solr Issue Type: Bug Affects Versions: 4.0 Assignee: Unassigned Components: Discovery Created: 08/Aug/13 12:32 PM Description: After the introduction of the UrlValidator in SolrServiceImpl https://github.com/DSpace/DSpace/blame/master/dspace-api/src/main/java/org/dspace/discovery/SolrServiceImpl.java#L100 the default configuration for solr on the localhost not longer work > 2013-08-08 12:31:14,613 ERROR org.dspace.discovery.SolrServiceImpl @ Error while initializing solr, invalid url: http://localhost:8080/solr/search I'm going to submit a pull request to fix this Fix Versions: 4.0 Project: DSpace Priority: Critical Reporter: Andrea Bollini This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1616) Localhost is not longer supported as a valid URL Solr
Andrea Bollini commented on DS-1616 Localhost is not longer supported as a valid URL Solr https://github.com/DSpace/DSpace/pull/271 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1616) Localhost is not longer supported as a valid URL Solr
Andrea Bollini closed DS-1616 as Fixed Localhost is not longer supported as a valid URL Solr merged Change By: Andrea Bollini (08/Aug/13 1:24 PM) Documentation Status: Needed Not Required Resolution: Fixed Status: Received Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1586) SLF4J and JCL Bridge version incompatibility
Andrea Bollini closed DS-1586 as Fixed SLF4J and JCL Bridge version incompatibility merged pull request https://github.com/DSpace/DSpace/pull/269 Change By: Andrea Bollini (08/Aug/13 1:26 PM) Documentation Status: Needed Not Required Resolution: Fixed Status: Code Review Needed Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1611) Enable Discovery By Default in JSPUI
Andrea Bollini commented on DS-1611 Enable Discovery By Default in JSPUI pull request here: https://github.com/DSpace/DSpace/pull/272 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1611) Enable Discovery By Default in JSPUI
Andrea Bollini commented on DS-1611 Enable Discovery By Default in JSPUI merged as it was a trivial change and there was a general agreement about this change in the IRC meeting http://irclogs.duraspace.org/index.php?date=2013-07-31 get this in the master soon so to have more eyes to review it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1272) Enable Discovery By Default in XMLUI
Andrea Bollini closed DS-1272 as Fixed Enable Discovery By Default in XMLUI Change By: Andrea Bollini (08/Aug/13 2:22 PM) Resolution: Fixed Status: Accepted Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1611) Enable Discovery By Default in JSPUI
Andrea Bollini closed DS-1611 as Fixed Enable Discovery By Default in JSPUI Change By: Andrea Bollini (08/Aug/13 2:21 PM) Resolution: Fixed Status: Accepted Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1617) Switch to SOLRBrowseDAOs implementation as default in DSpace 4.0
Andrea Bollini created DS-1617 Switch to SOLRBrowseDAOs implementation as default in DSpace 4.0 Issue Type: Task Assignee: Unassigned Components: DSpace API Created: 08/Aug/13 2:29 PM Description: As agreed in the IRC meeting http://irclogs.duraspace.org/index.php?date=2013-07-31 this issue will track the progress to make SolrBrowseDAOs implemention the default in dspace 4.0 Fix Versions: 4.0 Project: DSpace Priority: Major Reporter: Andrea Bollini This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1617) Switch to SOLRBrowseDAOs implementation as default in DSpace 4.0
Andrea Bollini commented on DS-1617 Switch to SOLRBrowseDAOs implementation as default in DSpace 4.0 pull request here: https://github.com/DSpace/DSpace/pull/273 also enabling by default the show frequencies in metadata browse as there are no performance penalities with the SOLR implementation This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1619) Unable to remove items after enabling SOLRBrowseDAOs
Andrea Bollini created DS-1619 Unable to remove items after enabling SOLRBrowseDAOs Issue Type: Bug Affects Versions: 3.2, 3.1, 3.0 Assignee: Andrea Bollini Components: DSpace API Created: 10/Aug/13 11:05 AM Description: This issue has been reported the first time in the dspace-tech mailing list: http://www.mail-archive.com/dspace-tech@lists.sourceforge.net/msg22950.html Il 31/07/2013 11:28, Gustavo ha scritto: > DSpace 3.0 allow customize which browse engine is utilized. > I use now SOLR Browse Engine(browseCreateDAO.class = org.dspace.browse.SolrBrowseCreateDAO). This class not add/remove any row in communities2item table. When I add an item no new row are add in the communities2item table. > Above I used browseCreateDAO.class = org.dspace.browse.BrowseCreateDAOPostgres when I add an item, a new row are add in the communities2item table each item. > When I attempt to erase an item add with the old configuration browseCreateDAO.class = org.dspace.browse.BrowseCreateDAOPostgres since the new configuration browseCreateDAO.class = org.dspace.browse.SolrBrowseCreateDAO no row are deleted from communities2item and an error ocurr > Excepción: >> org.postgresql.util.PSQLException: ERROR: update o delete en «item» >> viola la llave foránea «communities2item_item_id_fkey» en la tabla «communities2item» >> Detail: La llave (item_id)=(1984) todavía es referida desde la tabla >> «communities2item». Fix Versions: 4.0 Project: DSpace Priority: Minor Reporter: Andrea Bollini This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1619) Unable to remove items after enabling SOLRBrowseDAOs
Andrea Bollini commented on DS-1619 Unable to remove items after enabling SOLRBrowseDAOs Executing the command dspace dsrun org.dspace.browse.IndexBrowse -r -f all the browse related tables, view and index are removed except for the communities2item table that is not cleaned. You can easly fix this running the following sql: delete from communities2item; if you re-enable a dbms browse (postgres or oracle) just need to re-run the dspace dsrun org.dspace.browse.IndexBrowse -r -f and the communities2item will be re-populated. For DSpace 4.0 a patch will be post shortly to make this further step (sql delete) unnecessary to allow smooth switch to SOLRBrowseDAOs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1617) Switch to SOLRBrowseDAOs implementation as default in DSpace 4.0
Andrea Bollini closed DS-1617 as Fixed Switch to SOLRBrowseDAOs implementation as default in DSpace 4.0 merged as it was a trivial change and there was a general agreement about this change in the IRC meeting http://irclogs.duraspace.org/index.php?date=2013-07-31 get this in the master soon so to have more eyes to review it Change By: Andrea Bollini (10/Aug/13 12:38 PM) Resolution: Fixed Status: Received Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1619) Unable to remove items after enabling SOLRBrowseDAOs
Andrea Bollini closed DS-1619 as Fixed Unable to remove items after enabling SOLRBrowseDAOs done here: https://github.com/DSpace/DSpace/commit/027072068a1a0967a08634f2d4cf2d1dbab2a9aa keep the documentation status to needed to track the need to add a notice in the upgrade section about the need to run dspace dsrun org.dspace.browse.IndexBrowse -r -f Change By: Andrea Bollini (10/Aug/13 12:41 PM) Resolution: Fixed Status: Received Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1188) collection view doesn't show content by default
Andrea Bollini commented on DS-1188 collection view doesn't show content by default I'm going to test your pull request and trying to rebase / squash your commit in a single one that implement the features keeping proper author attribution. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1188) collection view doesn't show content by default
Andrea Bollini commented on DS-1188 collection view doesn't show content by default JSPUI contribution has been merged: https://github.com/DSpace/DSpace/pull/262 https://github.com/DSpace/DSpace/commit/5a04e9bad974f56c4d9cdadfea79a2b090e48df2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1557) Discovery JSPUI 3.1 dc.date.issued bad works
Andrea Bollini closed DS-1557 as Duplicate Discovery JSPUI 3.1 dc.date.issued bad works Change By: Andrea Bollini (12/Aug/13 9:50 AM) Documentation Status: Needed Resolution: Duplicate Status: Received Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1557) Discovery JSPUI 3.1 dc.date.issued bad works
Andrea Bollini updated DS-1557 Discovery JSPUI 3.1 dc.date.issued bad works Change By: Andrea Bollini (12/Aug/13 9:50 AM) Fix Version/s: 4.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1571) DSpace discovery CRITICAL bug when date facet produce range
Andrea Bollini updated DS-1571 DSpace discovery CRITICAL bug when date facet produce range Change By: Andrea Bollini (12/Aug/13 9:50 AM) Affects Version/s: 3.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
