Re: [Dspace-devel] multi-vote about remaining 3.0 tasks
My votes, all -1 are valid until the issues reported in JIRA are solved +1 #5 Maven Project Consolidation 0 #46 Batch import from major bibliographic formats -1 #47 Add tag cloud support in home page -1 #48 imp Add support for concatenating multiple values in item display instead of line breaks -1 #49 Auto update advance search drop down lists from configuration file -1 #50 Allow date range searches in advance search -1 #51 Display advance search form after an advance search -1 #52 Display frequencies of items in single browsing for selected indices 0 #53 Export items in various bibliographic formats -1 #54 Show display values (input-forms) for controlled vocabularies in ItemTag -1 #55 Indexing both stored and display-value from input-forms for search +1 #60 Initial contribution: porting Discovery to the JSPUI 0 #61 Enabling Dynamic DSpace Configuration Manager services#1 Dynamic configuration alternative (File based) 0 #63 Statistics implementation in Elastic Search +1 #67 BrowseDAO based on discovery 0 #69 @mire solr statistics contribution 0 #71 Controlled vocabulary support for the XMLUI +1 #72 Atmire dspace 3.0 versioning contribution +1 #73 authority field in Batch Metadata Editor +1 #74 display bitstream read access permissions on item page +1 #75 Configurable Workflow Improvements +1 #76 Ldap improvements Andrea-- 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] R: Dspace and CAS problem (SSL)
Probably you are using a selfsigned certificate. You need to trust the cas ssl certificate in the jvm that is used to run dspace (tomcat). Look to the keytool help to check the exact parameter. The truststore is usually stored in a file named cacerts in the lib/security of your jre. Hope this help, Andrea Inviato da Samsung Mobilerevskill revskil...@gmail.com ha scritto:Hi everyone. I'm running Dspace behind Apache Proxy (listen in port 443) with servername https://dspace My CAS server is running as https://casserver When i submit login form from CAS server, the client returned the error below in log file: *012-10-13 08:57:21,500 ERROR org.dspace.authenticate.CASAuthentication @ Unexpected exception caught javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(Unknown Source) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Unknown Source) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Unknown Source) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(Unknown Source) at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(Unknown Source) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)* As i see, this is problem with Dspace when it must verify the server certificate in order to process service ticket from CAS server. Do you know how to fix this problem ? Thank you very much. -- TRUONG HOANG DUNG* **Librarian Researcher **Information and Library Centre Mobile: 0121.411.5322 Email: dun...@hpu.edu.vn* *Hai Phong Private University* http://lib.hpu.vn -- 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] R: Re: Dspace and CAS problem (SSL)
Hi revskill, the most simple thing to do is access the casserver url from your browser and download the shown certificate. I have not a pc here so I can't check the command myself... Try to follow the instructions listed here: http://blog.lesc.se/2009/09/how-to-makejava-ssl-trust-certificate.html?m=1 Be sure to indicate your cacerts as trustore file. Andrea Inviato da Samsung Mobilerevskill revskil...@gmail.com ha scritto:I see. Now i had 2 files casserver.crt and casserver.key from CAS server (signed from my own CA.crt and CA.key) I had dspace.crt and dspace.key (signed from those CA.crt and CA.key, too), can you point me specifically how to trust that CA.crt from JVM truststore ? Thank you very much. 2012/10/13 bollini boll...@cilea.it Probably you are using a selfsigned certificate. You need to trust the cas ssl certificate in the jvm that is used to run dspace (tomcat). Look to the keytool help to check the exact parameter. The truststore is usually stored in a file named cacerts in the lib/security of your jre. Hope this help, Andrea Inviato da Samsung Mobile revskill revskil...@gmail.com ha scritto: -- TRUONG HOANG DUNG* **Librarian Researcher **Information and Library Centre Mobile: 0121.411.5322 Email: dun...@hpu.edu.vn* *Hai Phong Private University* http://lib.hpu.vn -- 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
Re: [Dspace-devel] [Dspace-tech] DSpace 1.5.2 Release Coordinator and Issue Tracking.
Dear DSpace users developers, the 1.5.2 release is close, the central event is the Testhaton day: March 25, 2009. All the work should really be done before the testhaton day, only marginal bugs or bugs discovered during the testhaton itself should be fixed after this event. I hearthly invite all you to get involved in this process, please check the planning on the JIRA system (http://jira.dspace.org/jira/browse/DS) and feel free to add your comments, post new bugs, patches or improvement requests. For instance, we need your opinion about this topic: http://jira.dspace.org/jira/browse/DS-89 DSpace is an open source project, your opinion must drive our roadmap! Finally, I'm happy to announce that my company, CILEA, will provide a test instance for the testhaton and a member of our customer support staff will be involved in testing. But I would be more confortable if another additional instance is available, to insure that during the testhaton one instance will always be available even when the other is down for configuration change or patch check. Please let me know who is able to provide such instance. Next week, I will write you a reminder about the testhaton. A wiki page will be available with info about the URL and configuration of test instances and all the instructions needed to get involved. Don't miss this opportunity! See you on the #dspace IRC channel http://wiki.dspace.org/index.php/DSpaceResources#Chat_Room or the mailing list to drive together the 1.5.2 release. Best regards, Andrea Bradley McLean ha scritto: I'm happy to announce that Andrea Bollini has taken on the role of Release Coordinator for DSpace 1.5.2. He has recently updated the status page at http://wiki.dspace.org/index.php/Next_Release_Status and is working closely with other committers to prepare the release. Issue tracking for 1.5.2 has been moved from SourceForge to a Jira, hosted at http://jira.dspace.org/jira/browse/DS Interested parties are encouraged to review, comment, and vote on the issues there. If you register, you can also subscribe to updates on issues that interest you. If you have questions about DSpace 1.5.2 feel free to contact either Andrea or myself. Bradley McLean, Technology Director, DSpace Foundation -- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com ___ DSpace-tech mailing list dspace-t...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Dott. Andrea Bollini Project Manager, IT Architect Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. -- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] Reminder 1.5.2 Testhaton Day
Hi all, just a reminder: the 25 March will be the testhaton day for the 1.5.2 release, get involved! A wiki page for the event is in place http://wiki.dspace.org/index.php/Testhaton_1_5_2 feel free to add your test instances and any notes (use cases or missed features to be tested). We will do our best to perform as many tests as possible but our resources are limited so your help is needed too! Most of the work scheduled for this release has been completed http://jira.dspace.org/jira/browse/DS/fixforversion/10012 however some issues are still in progress so additional SVN commits may occur today. Best regards, Andrea -- Dott. Andrea Bollini Project Manager, IT Architect Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. -- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] Next language pack release
Hi all, we have some new languages available in the i18n translation and some update, I think that a new release of the dspace-api-lang and dspace-xmlui-lang could be appropriate should we make it immediately after the 1.5.2 release? Andrea -- Dott. Andrea Bollini Project Manager, IT Architect Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Next language pack release
Hi Claudia, please let me know if I wrong 1 uptodate jspui translation (de) (revision 3642) and 2 uptodate xmlui translations (de, it) (revision 3646) also the italian jspui is already up-to-date ;-) We can tag these as 1.5.2.0 and adjust the versioning in the api-lang and xmlui-lang dependency. Other translations will be updated but this can take a while. They have to be tagged, when they arrive. well, before to release the 1.5.2 I will tag the i18n modules and update the dependency so that the 1.5.2.0 will be the low version required. some new languages will be available also if not full up-to-date JSPUI: Thai XMLUI: ca, el, es, ja, pt_BR New translations or update might be in 1.5.2.1 and next. Furthermore we need a way to ease the customization of message catalogues for those using the bin distribution. One other thing, it would be good to have the languages exposed configurable. Most people are not aware that they got all the available message catalogues per default. I haven't understand what you mean, does the basic overlay method not work for the bin distribution? or are you saying that more documentations is required? Andrea Sunny greetings Claudia Andrea Bollini schrieb: Hi all, we have some new languages available in the i18n translation and some update, I think that a new release of the dspace-api-lang and dspace-xmlui-lang could be appropriate should we make it immediately after the 1.5.2 release? Andrea -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Dott. Andrea Bollini Project Manager, IT Architect Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] [DSpace-changelog] SF.net SVN: dspace:[3684] branches/dspace-1_5_x/dspace
-1_5_x/dspace-xmlui/dspace-xmlui-api/src/main/java/org/dspace/app/xmlui/cocoon/HttpServletRequestCocoonWrapper.java
2009-04-06 22:15:05 UTC (rev 3683)
+++
branches/dspace-1_5_x/dspace-xmlui/dspace-xmlui-api/src/main/java/org/dspace/app/xmlui/cocoon/HttpServletRequestCocoonWrapper.java
2009-04-06 22:52:38 UTC (rev 3684)
@@ -152,11 +152,11 @@
}
public String getRemoteUser() {
- return this.getRemoteUser();
+ return this.cocoonRequest.getRemoteUser();
}
public String getRequestURI() {
- return this.getRequestURI();
+ return this.cocoonRequest.getRequestURI();
}
public StringBuffer getRequestURL() {
@@ -168,15 +168,15 @@
}
public String getServletPath() {
- return this.getServletPath();
+ return this.cocoonRequest.getServletPath();
}
public HttpSession getSession() {
- return this.getSession();
+ return (HttpSession)
this.cocoonRequest.getSession();
}
public HttpSession getSession(boolean arg0) {
- return this.getSession(arg0);
+ return (HttpSession)
this.cocoonRequest.getSession(arg0);
}
public Principal getUserPrincipal() {
Modified:
branches/dspace-1_5_x/dspace-xmlui/dspace-xmlui-api/src/main/java/org/dspace/app/xmlui/cocoon/PropertyFileReader.java
===
---
branches/dspace-1_5_x/dspace-xmlui/dspace-xmlui-api/src/main/java/org/dspace/app/xmlui/cocoon/PropertyFileReader.java
2009-04-06 22:15:05 UTC (rev 3683)
+++
branches/dspace-1_5_x/dspace-xmlui/dspace-xmlui-api/src/main/java/org/dspace/app/xmlui/cocoon/PropertyFileReader.java
2009-04-06 22:52:38 UTC (rev 3684)
@@ -76,8 +76,11 @@
Properties props = new Properties();
InputStream in = new FileInputStream(propertyFile);
- props.load(in);
- in.close();
+try {
+ props.load(in);
+} finally {
+ in.close();
+}
final String[] parameterNames =
parameters.getNames();
This was sent by the SourceForge.net collaborative development
platform, the world's largest Open Source development site.
--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
___
DSpace-changelog mailing list
dspace-change...@lists.sourceforge.net
mailto:dspace-change...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-changelog
--
Mark R. Diggory
http://purl.org/net/mdiggory/homepage - Bio
http://www.atmire.com - Institutional Repository Solutions
http://www.togather.eu - Before getting together, get t...@ther
--
Mark R. Diggory
http://purl.org/net/mdiggory/homepage - Bio
http://www.atmire.com - Institutional Repository Solutions
http://www.togather.eu - Before getting together, get t...@ther
--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
--
Dott. Andrea Bollini
Project Manager, IT Architect Systems Integrator
Sezione Servizi per le Biblioteche e l'Editoria Elettronica
CILEA, http://www.cilea.it
tel. +39 06-59292853
cel. +39 348-8277525
---
Disclaimer: the content of this email is confidential and may be privileged,
and it must not be disclosed or copied without the sender's consent. If you
have received this message in error, please notify the sender and remove it
from your system. The content of this email does not constitute legal advice,
nor any responsibility is accepted for loss or damage incurred
[Dspace-devel] DSpace 1.5.2 RC2 released
Dear DSpace Community, We are pleased to announce the release of DSpace 1.5.2 RC2. Please refer to the http://jira.dspace.org/jira/browse/DS/fixforversion/10012 and SVN history for details about the modifications. http://wiki.dspace.org/index.php/DSpace_Release_1.5.2_Notes#SVN_Repository_History The final release of 1.5.2 should be out on or after 14th April. We request that community members interested in testing this release candidate please download it and verify that they can complete upgrade and fresh installation. We request that the svn branch be frozen until we do complete the final release, if developers do have further fixes, please request their addition through the developers list before moving forward with SVN commits. The documentation for this release is bundled within the package. DSpace 1.5.2 RC2 can be downloaded from the files area at https://sourceforge.net/project/showfiles.php?group_id=19984 or with SVN from http://dspace.svn.sf.net/svnroot/dspace/tags/dspace-1_5_2-rc2/ Please use the mailing lists to provide feedback on this release. Those wishing to do development work with DSpace are strongly encouraged to obtain the source code using SVN. This is very straightforward and a guide to doing this is available here: http://wiki.dspace.org/ContributionGuidelines We would also like to take this opportunity to invite you all to take part in the DSpace development process. Extra developer hands are always welcome, but there are other ways you can help: - Test the system and report bugs - Provide documentation (for end users and institutions, as well as technical) - Provide or update language packs - Share your deployment experiences - Donate content and metadata for testing and research - Share your technical experience and ideas Please visit the DSpace Wiki to see the various resources and collaboration tools available to the DSpace community: http://wiki.dspace.org/DspaceResources Sincerely, Andrea Bollini -- Dott. Andrea Bollini Project Manager, IT Architect Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] need opinion on GSOC project(Submission Enhancements)
Hi Gaurav, welcome! I like to see this information stored in database so that you have less concern about write/read lock and a more scalable solution when a hight number of collections are availables (at the moment we are maintaining a DSpace repository with more then 1000 collections). I want to suggest a few things: 1) the role that is allowed to change the submission configuration should be configurable in dspace.cfg (collection admin or system admin) 2) a collection could have more then one available type of submission, in this case the select collection step is required to ask to the user which form has to be used 2.1) I think to the type of submission as a combination of exactly one form-definition and one submission-process 3) an import configuration tool should be provided for both: upgrade and fast system admin management (an update mode should be useful but I don't think that it is mandatory) Andrea gaurav kejriwal ha scritto: Dear Dspace Community, I have been selected for Google Summer of Code 2009 for my project on Submission Enhancements to work under the guidance of my mentors Claudia Juergen and Stuart Lewis.My project aims at developing UIs for the Dspace admins so that they can manage the input forms and submission workflow.Also the project aims at allowing item type based submission.More details can be found at the wiki page http://wiki.dspace.org/index.php/Google_Summer_of_Code_2009_Submission_Enhancements. To implement this,we can follow 2 approaches.Either we can manage the forms and submission work flow through db or just create a new updated inputforms.xml/item-submissions.xml file when the admin chooses the options through UI without disturbing the core database. I need the community to suggest which approach will be better considering future Dspace development.Please suggest which approach will be better to follow. Thanks Regards Gaurav -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Dott. Andrea Bollini Project Manager, IT Architect Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Alternative way to store embargo data
Hi Richard, I have uploaded a draft of the modifications that I propose for the dspace-api. I hope that with the patch it will be more clear. Please take a look if possible, Andrea Richard Rodgers ha scritto: Hi Andrea: I'm not clear about how such a proposed change would work: even if we change the time of policy imposition to when the workspace item is created, there is no way in the submission UI to manipulate them. To bring over and expose the parts of the admin UI necessary to manage policies on the submission side seems a bit daunting, and could substantially complicate a workflow that many seem to want to simplify: many admins find it a confusing model, let alone submitters. However, I do think that you are right that a metadata approach (like the one proposed for the emabargo work) is a promising one to solve the problem Claudia raises: to influence the policies during submission. In fact, that is precisely what the embargo framework does - it provides a means to express in metadata fields values that are *programmatically interpreted* at submission time to affect policies. Since these are just interfaces, and you can add any logic you want behind them, you could use the embargo framework to enforce item-specific access policies entered at submit time that *don't* involve embargo (even bitstream-level, if desired). But maybe I have misunderstood what is being proposed, or the attendant complexity. I will post the current embargo code to the wiki shortly, so the discussion can be more concrete Thanks, Richard On Mon, 2009-08-03 at 09:59 +0200, Andrea Bollini wrote: Hi Richard, I write primary to you as chair of the embargo functionality workgroup for 1.6 Claudia has recently added a jira issue, DS-267, http://jira.dspace.org/jira/browse/DS-267 about the opportunities to make modifiable during the submission process the final permission applied to the item and its bitstreams. As you can read from my comment: http://jira.dspace.org/jira/browse/DS-267?focusedCommentId=10442page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_10442 I think that we can easily archive this goal if we change the time when the policies of the item/bitstreams are defined. At the moment, we define the policy of the published item when them go in the archive thought the InstallItem class that call the inheritCollectionDefaultPolicies. I propose to make a similar call during the WorkspaceItem creation so that we have the policies already in place during the submission and we can manage them. I see that this solution partially overlaps with your assumption to use item metadata to store Embargo data but, IMHO my approach doesn't break your solution only make an alternative way available. In particular, if you are fine with moving the inherit policies from the archiving process to the start of submission, I will be able to share with the community the CILEA solution for embargo (JSPUI only) based on the first version of the work make by the Leiden University http://wiki.dspace.org/index.php/Embargo_on_Bitstream_(JSP) Our solution allows to define, independently for any bitstreams, an access policy of anonymous read from a starting date, an restricted access to one or more groups specificated in the dspace.cfg or a wide classic open access rule. The type and numbers of embargo options are configurable in the dspace.cfg on a collection basis. Please add your comment on the jira system: DS-267, best Andrea PS: please note that for share our embargo solution with the community I will need to perform some re-engineering to extract it from other our customizations, so I like to perform them only if we agree with the dspace API core change related to the time of resource policy definition or at least we really want evaluate this change -- Dott. Andrea Bollini Project Manager, IT Architect Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now
Re: [Dspace-devel] Authority Control for DSpace, part 1: encoding of references to entries (concepts)
Hi Christophe, I am back after some time in the country side. I discover today the committer meeting transcript. This was exactly what I expected to happen ;-) [16:15] bradmc All of that sounds good; are we ready to move on to community admin? [16:15] bollini I'm expect some comments after that the IRC transcription will be post to the list First, I am Christophe and not Dupriez! I hope meeting all of you in Göteborg to break the ice! yes you are definitely Christophe for me ;-) look forward to meet you in Goteborg [4:07pm] bollini: we have received many comments from Dupriez and documentation about a different approach My implemented specs (http://www.windmusic.org/dspace) did not received any approval by comitters: the reaction was Larry and Andrea starting the same work! This is not fully true, as far as I know Larry has started is work exactly when he has opened the discussion about authority, sharing before he's spec and solution proposal... I have read your documentation (very good) and I have send back few comments (to your first emails) but Larry, and now myself, is gone ahead because under strictly customer timeline. This limit has been underline by Larry in his first email... [4:08pm] bollini: but we have not received any codes and (as far as I know) the Dupriez code works on an old dspace 1.4 or less My work is on the basis of DSpace 1.4.2 the main difficult to update it to the 1.5 could be the change to the browse system [4:09pm] bollini: with the Larry model and few changes that I have made we can cover the functional requirements of Dupriez I do not see how you may support indexation and retrieval by translations, synonyms and broader concepts (or precise concepts). I plan to share these changes next week so that you can check it yourself, anyway in brief I give an opportunitiy to the ChoiseAuthority class to give any translations/synonyms at the time of indexing so to add also them to the index. I also store the exact authority key in a separate index to allow precise concepts search. I have not a solution for broader concept at the moment, but I think that we can add this functionality after to have experienced on some real case. Furthermore, if concepts are prefixed by qualifiers (like the MeSH as used in Pubmed) and suffixed by quantities (like top in PubMed or instruments quantities in WindMusic), the Larry Model is not enough either. [4:10pm] stuartlewis: Excellent - sounds good. Are you going to liaise with Christophe to check that his functional requirements are met? [4:10pm] bollini: the only think that remains out is the out-of-box SKOS integration of the Dupriez model [4:10pm] bollini: no Stuart, I haven't Data structures are VERY important, especially this one which will impact BlackLight integration (my next endeavour: http://projectblacklight.org/). They should be discussed before final development and integration, on the basis of what can be measured on some prototypes. I agree, we need prototypes for evaluate different approaches WindMusic is there to test (it is operational from the customer point of view). It will be demonstrated at DSUG 2009 (Göteborg): in 20 minutes!!! I hope that we can check together if the Larry prototype with these last changes will work for your use case I disagree with the idea of not completing the reflexion on the design of the data structure. If we agree on data storage, then contributing code becomes much more easier. For my work, I rejected the idea of Larry because it was not providing all the functionalities my customer needed (he wants even more now that he intensively uses the system: support of reflexive see also relations, I think that having in the hand the authority key you can interrogate the authority provider during the item splash page rendering and build as complex as needed inter navigation links auto-complete based on a key more sophisticated than just the title...) The auto-complete behaviors is already pluggable so how (and where) you search the authority is fully customizable I am not a committer (or a release coordinator). I cannot afford to make a patch to a running target (1.6 or so) and have it rejected without discussion. I wants to have an approval on specs and then on data structures and then on software architecture and then on independant contributions. this could be a too long process (at least for my related projects deadline), I suggest to you to share the code early and don't worry about have it rejected without a discussion, this is not the case we can use your code to full fit requirements again not covered, better understanding your (customer) needs and also improve existing code. So the main principle I need to make accepted now is below: Anywhere some text may be entered as data, one (and eventually more) indexing string may be specified (helped by a menu or an auto-complete when
[Dspace-devel] 1.6 JIRA Cleanup
Sorry to have missed the last meeting... I have reviewed the IRC transcription and I want confirm/reject some tasks. I confirm that I can work on DS-259 - Minor/Bug - Community/collection admin should not to be able to delete their admin group - http://jira.dspace.org/jira/browse/DS-259 - DS-228 - Major/New Feature - Community Admin XMLUI: Delegated Admins Patch - http://jira.dspace.org/jira/browse/DS-228 DS-260 - Critical/Bug - Template item some times has owningCollection filled and some times not - http://jira.dspace.org/jira/browse/DS-260 (only fix the differences behaviour of jspui and xmlui no change to the use of the item also for template item) DS-270 - Major/Improvement - Make delegate admin permissions configurable - http://jira.dspace.org/jira/browse/DS-270 DS-236 - Authority Control, and plug-in choice control for Metadata Fields - http://jira.dspace.org/jira/browse/DS-236 [I will post the patch for jspui/postgres and some additions in the next few days] About the DS-267 - Major/New Feature - Item submission - possibility to overwrite the default item policies as inherited from the owning collection during item submission - http://jira.dspace.org/jira/browse/DS-267 I need a general consensus against the use of DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ actions on Item, Bundle e Bitstream objects - please add your comments on the jira issue. The admin UI is already able to manage the changes made by this patch (I have tested only on JSPUI but for the XMLUI could be needed only minimal changes). Changes to the submission UI are not required, I can build a patch for add embargo facility using this infrastructure but I'm not sure to be able to do it in time for 1.6 Finally, the issue DS-82 Initial Questions and Collection Template not in sync - ID: 1456321 http://jira.dspace.org/jira/browse/DS-82 was previously assigned to me but I'm not able to accomplish it (please read the comments in jira) Best, Andrea -- Dott. Andrea Bollini Project Manager, IT Architect Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] Deferred constraint and make authoritation system configurable
Hi all, I'm working on http://jira.dspace.org/jira/browse/DS-270 I'm pretty near to a solution but I need to take a decision about how manage the deletion of subcommunity/collection. The goal is to make configurable if a local admin (community/collection) is allowed to remove his subcommunities, collections and items. The problem is that the Community.removeCollection but also Community.removeSubCommunity and Collection.removeItem drop the relation with here parent at the start of the procedure so, if the subelement is an orphan, we can't more derive permissions from the parent. If you take a look a the current code you will see comments like this //make the right to remove the item explicit because the implicit // relation //has been removed. This only has to concern the currentUser // because //he started the removal process and he will end it too. //also add right to remove from the item to remove it's bundles. AuthorizeManager.addPolicy(ourContext, item, Constants.DELETE, ourContext.getCurrentUser()); AuthorizeManager.addPolicy(ourContext, item, Constants.REMOVE, ourContext.getCurrentUser()); // Orphan; delete it item.delete(); I see two options here: 1) we can go on with the current practise of manually add all the permissions that we would inherited from the parent but this will make the remove method less clear and the authorization logic more scattered 2) we can check for subelement that will become orphan before, and subsequently remove them. Deferring at the end the drop of the relation. In this case we will need to defer the constraint check (for example community2collection_collection_id_fkey on table community2collection ) during the subelement deletion. What do you think? could be appropriate use constraint deferring? Thanks for you suggestion, Andrea -- Dott. Andrea Bollini Project Manager, IT Architect Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Upgrade directions for 1.6
Hi Jeffrey, I try to help, these are some personal note about 1.5-1.6 migration... pretty far to be complete! 1) yes, you need to run an update sql script dspace/[postgres|oracle]/ please put a notice for the oracle users like this: Please note that the last 3 rows of the output of the sql script will be additional queries to run against your db. They are need to make changes to some foreign key definition, look to the comments inside the sql script for additional information. 2) the suggestion should be to start from scratch with a new dspace.cfg and paste in it your changes; use the dspace.cfg in [dspace-src-folder]/dspace/config/ so you need only to run mvn package and after the ant update without the -Dconfig parameter 3) you need to execute index-init because the authority control framework change the definition of the browsing tables. Hope this help, Andrea Jeffrey Trimble ha scritto: I need a little assistance in making sure our directions for upgrading a current installation of DSpace 1.5 to 1.6 are going to be correct. As I start to code the documentation this week, here are the list of issues I need assistance with. PRAENOTANDA: I have not attempted to upgrade any of my test or developmental environments, because, I'm not sure the trunk is complete. 1. Do we have an Update the Database step where an SQL script is going to run? 2. Update of dspace.cfg files. In the past we have had very confusing directions in which we have instructed users to perform the update_configs directions. It was always after the complete update of DSpace, and before the customization options. I have al y when attempting to perform it. So, I just ignore that step, and manually update the dspace.cfg file. So, here's my suggestions/questions to this: -- If you are going to run ant -Dconfig=[dspace]/config/dspace.cfg update_configs, it should be the step before you run the normal ant -Dconfig=[dspace]/config/dspace.cfg update. Is there agreement here? 3. Are there additional steps that need to be included? Such as: -- index-init -- additional configurations that need special attention that the directions in the config file needs enhanced? I hope to have a preliminary upgrade section written by the middle of the week for feedback. T divJeff Jeffrey Trimble System LIbrarian William F. Maag Library Youngstown State University 330.941.2483 (Office) jtrim...@cc.ysu.edu mailto:jtrim...@cc.ysu.edu http://www.maag.ysu.edu http://digital.maag.ysu.edu I must not fear. Fear is the m ill permit it to pass over me and through me... --Litany against fear -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Dott. Andrea Bollini Project Manager, IT Architect Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] Is the trunk out-of-date?
Hi all, I'm a little out-of-date with the last development and the 1.6.2 release... is the trunk broken? what should be the starting point for 1.7 development? the parent pom http://fisheye3.atlassian.com/browse/dspace/dspace/trunk/pom.xml?r=HEAD in the trunk say 6 version1.6.1-SNAPSHOT/version Thanks, Andrea -- Dott. Andrea Bollini Project Manager, IT Architect Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Difference between 'communities2item' and 'community2item' ?
Hi Tim, just to confirm you that the content of the communities2item table and of the community2item view is different. I have checked many installations and the communities2item is always larger than the community2item view. I don't remember why this is needed... Andrea Il 02/08/2010 18:59, Tim Donohue ha scritto: All, Hopefully someone more familiar with this area of the DSpace code can help me figure this out because I'm a bit confused about something I've never noticed before. In our DB, we have a table named 'communities2item' and a view named 'community2item'. From what I can tell, they are used as follows: * communities2item table Used by the org.dspace.browse.BrowseEngine and org.dspace.search.Harvest -- so, essentially it is used by our Browse Search UIs. * community2item view Used by Item.getCommunities() to determine all the communities that a particular item is held in. This method is in turn used by the DSIndexer (in buildItemLocationString()) to add to the Search Index. What is the big difference between these two sets of data? I've noticed locally that 'communities2item' is actually larger than my 'community2item' -- it seems some items never make it into the latter (not sure why, as they are 'in archive' and not deleted). Anyone know why this repetition of data is necessary? At a quick glance, it seems like these are serving the same purpose -- but, I haven't dug deep enough to be certain. - Tim -- Dott. Andrea Bollini Project Manager, IT Architect Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] DSpace Discovery and DSpace 1.7
Hi all, I started to take a look at dspace discovery. I'm very excited to see a SOLR integration in DSpace to manage the search and browse functionalities so I really hope that we can include this nice addition in DSpace 1.7. I like to see some discussion about the following details: *- integration with the authority framework* as far as I can see there is not integration at this point. I will be happy to handle this by myself. My idea is to store, when the confidence level is greater than a configurable value, the authority key in a field _authority (ie. contributor_authority) when there is no authority key or the confidence level is not good enought we should store the simple metadata.value in the solr field (ie contributor). A similar rule should apply to facetting. We can't use directly the same field used for the search because we need to sort facet for browsing (think about diacrytics in names). I'm thinking to store the facet value with the following syntax sort_value|||display_form|||authority_key(if any) When the facet is shown we should use the authority_key to build the filter (on the field_authority) or the display_form if there is not authority_key *- use of a custom solr build* https://scm.dspace.org/svn/repo/modules/dspace-solr/trunk/README I'm not happy to manage a custom build of solr, I think that in the long way it could be an expensive task. The SOLR-236 is still not included in the main SOLR distribution and there is a lot of debate around it. The version that we have currently included seems already modified to fix some bugs... a new major release of solr (1.4) has been released and we should move to it as soon as possible before than more works on solr are build. Why do we need this custom build? I think that Dryad is not using it... instead from the screenshoot on the dspace wiki https://wiki.duraspace.org/display/DSPACE/DSpace+Discovery+HowTo I see that in xmlui there is a group by option, is this the reason for the custom build or is it needed for other? *- old browse and search provider* if we add discovery at dspace 1.7 should we remove the old search browser provider? I don't see a valid reason to keep it in place and duplicate maintenace effort... Andrea -- Dott. Andrea Bollini Project Manager, IT Architect Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] Different strategies to implement metadata browse with Discovery
Hi all, as discussed in the last IRC Dev meeting I'm working on a porting of the dspace-discovery idea to the JSPUI. As side effect I'm trying to better understand and (if possible) improve discovery self... I have mainly completed the replacement of DSpace Lucene engine with the one provided by Sorl/Discovery, faceting on search results work well also for metadata with authority key. Now I'm thinking about the use of SOLR to replace the dspace browse system, I'm facing with several issues that I want try to summarize showing different strategies. Use SOLR for browsing has IMHO the following pros: - we will use an external well established library to manage our browse system - we will use an unified approach for search and browse - performance? probably but I have not real data comparison between indexing and query time in our current Browse system and SOLR 1) SOLR facets are not good for pagination: - As far as I know there is not out-of-box way to get answer to this question: how many facet I have for this field in this query? - you can navigate facet result using offset and limit (show facet from position X to position Y) but you can't ask to start with the facet My Value or from a facet that start with letter X This mean that we are not able with SOLR to reproduce the same features of our the current browse system, no total count of authors, keywords, etc. and not jump to a position in the index... So if we use this approach we should remove some existent functionalities or look to the SOLR facet component to see if we are able to improve it and contribute back to the SOLR community. 2) Using SOLR TermsComponent: during my exploration I found this new component in SOLR 1.4 http://wiki.apache.org/solr/TermsComponent It allows great pagination on field terms (total count, offset, limit, jump to are all supported)... but it doesn't work in a combined way with query. This mean that we are not able to use it to provide browse of metadata values within a community or collection. We could workaround this limit making several copies of the browse metadata in solr field specific of a community or collection, i.e we will have solr fields like author_m64 (author in community with id 64) and so on. I'm not sure if there are issues to put so much fields for document. For any metadata browse we will get one addition field for any community and collection, so with repository with a height number of communities/collections, for example 200 communities and 2k collections, we will get document with potential 2,2K fields for any browse. 3) the last option that I see is to add a new core to SOLR (i.e. browse), the SOLR browse document could have the following fields browse-type (author, keywords, publishers, etc.),browse-unique-value (the value to lookup),value (the value to display),authority_key (the authority key if any),sort (the sort value), item_id (repeatable, the id of all item that use this term) using a solr core browse centric instead of a core item centric will simplify and resolve all our pagination issues. Instead new issues arise related to filling and keep up-to-date this new index... after a first raw evaluation I think that we need how many solr insert/update as current db browse insert/update... pros of this strategy vs previous - integration of additional information, indexing of authority source could be easily integrated. If you have a directory of institutional author and you want put all the institutional author in the browse index you can easly accomplish this also if there is no item for an institutional author. The same thing apply to subject classification, etc. cons: - there are not facet opportunities, we can't filter authors in the repository in a specific topic (based on item keywords) My preference is for the solution 2 but I will be happy to hear other idea. Andrea Dott. Andrea Bollini Project Manager, IT Architect Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA,http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Dspace-devel mailing list
Re: [Dspace-devel] [DuraSpace JIRA] Updated: (DS-704) Update pdfbox library to improve performance and out-of-box support for pdf extraction
Hi Jose,
please looks at the last comment in the Jira issue
https://jira.duraspace.org/browse/DS-704?focusedCommentId=17807page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_17807
https://jira.duraspace.org/browse/DS-704?focusedCommentId=17807page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_17807
Andrea
Il 18/10/2010 18:04, Blanco, Jose ha scritto:
I tried using this patch and I get the following message:
1) com.ibm.icu:icu4j:jar:3.8.1
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.ibm.icu -DartifactId=icu4j
-Dversion=3.8.1 -Dpackaging=jar -Dfile=/path/to/file
Where do I get icu4j:jar:3.8.1?
Thank you!
Jose
-Original Message-
From: Tim Donohue (DuraSpace JIRA) [mailto:no-re...@duraspace.org]
Sent: Monday, October 18, 2010 10:13 AM
To: dspace-devel@lists.sourceforge.net
Subject: [Dspace-devel] [DuraSpace JIRA] Updated: (DS-704) Update pdfbox
library to improve performance and out-of-box support for pdf extraction
[
https://jira.duraspace.org/browse/DS-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue updated DS-704:
---
Status: Open (was: Received)
+1 I'd vote to go ahead and upgrade the version of PDFBox we are using in
DSpace 1.7.0. I know there were several issues with the older version.
Update pdfbox library to improve performance and out-of-box support for pdf
extraction
--
Key: DS-704
URL: https://jira.duraspace.org/browse/DS-704
Project: DSpace
Issue Type: Improvement
Components: DSpace API
Reporter: Andrea Bollini
Assignee: Andrea Bollini
Fix For: 1.7.0
Attachments: dspace-pdfbox.patch
We have found that update the pdfbox library to the last stable version
(1.2.1) solve all our current issues with pdf text extraction and improve
performance.
This could help people that want rely on the DSpace out-of-box pdf
extractor without using XPDF.
Below some samples of exception that go away updating the pdfbox version.
Patch attached against trunk r5439
==
java.io.IOException: Error: Could not find font(COSName{F1.0}) in map={}
at org.pdfbox.util.operator.SetTextFont.process(SetTextFont.java:83)
at org.pdfbox.util.PDFStreamEngine.processOperator(PDFStreamEngine.java:452)
at org.pdfbox.util.PDFStreamEngine.processSubStream(PDFStreamEngine.java:215)
at org.pdfbox.util.PDFStreamEngine.processStream(PDFStreamEngine.java:174)
at org.pdfbox.util.PDFTextStripper.processPage(PDFTextStripper.java:336)
at org.pdfbox.util.PDFTextStripper.processPages(PDFTextStripper.java:259)
at org.pdfbox.util.PDFTextStripper.writeText(PDFTextStripper.java:216)
at
org.dspace.app.mediafilter.PDFFilter.getDestinationStream(PDFFilter.java:139)
===
java.lang.ClassCastException: org.pdfbox.cos.COSArray cannot be cast to
org.pdfbox.cos.COSDictionary
at org.pdfbox.filter.FlateFilter.decode(FlateFilter.java:70)
at org.pdfbox.cos.COSStream.doDecode(COSStream.java:290)
at org.pdfbox.cos.COSStream.doDecode(COSStream.java:243)
at org.pdfbox.cos.COSStream.getUnfilteredStream(COSStream.java:170)
at org.pdfbox.pdfparser.PDFStreamParser.init(PDFStreamParser.java:101)
at org.pdfbox.cos.COSStream.getStreamTokens(COSStream.java:132)
at org.pdfbox.util.PDFStreamEngine.processSubStream(PDFStreamEngine.java:202)
at org.pdfbox.util.PDFStreamEngine.processStream(PDFStreamEngine.java:174)
at org.pdfbox.util.PDFTextStripper.processPage(PDFTextStripper.java:336)
at org.pdfbox.util.PDFTextStripper.processPages(PDFTextStripper.java:259)
at org.pdfbox.util.PDFTextStripper.writeText(PDFTextStripper.java:216)
at
org.dspace.app.mediafilter.PDFFilter.getDestinationStream(PDFFilter.java:139)
java.io.IOException: Unknown colorspace array type:COSName{DeviceRGB}
at
org.pdfbox.pdmodel.graphics.color.PDColorSpaceFactory.createColorSpace(PDColorSpaceFactory.java:116)
at org.pdfbox.pdmodel.PDResources.getColorSpaces(PDResources.java:264)
at org.pdfbox.util.PDFStreamEngine.processSubStream(PDFStreamEngine.java:193)
at org.pdfbox.util.PDFStreamEngine.processStream(PDFStreamEngine.java:174)
at org.pdfbox.util.PDFTextStripper.processPage(PDFTextStripper.java:336)
at org.pdfbox.util.PDFTextStripper.processPages(PDFTextStripper.java:259)
at org.pdfbox.util.PDFTextStripper.writeText(PDFTextStripper.java:216)
at
org.dspace.app.mediafilter.PDFFilter.getDestinationStream(PDFFilter.java:139)
===
java.lang.NullPointerException
at org.pdfbox.pdmodel.PDPageNode.getAllKids(PDPageNode.java:194)
at org.pdfbox.pdmodel.PDPageNode.getAllKids(PDPageNode.java:182)
at
org.pdfbox.pdmodel.PDDocumentCatalog.getAllPages(PDDocumentCatalog.java:226
Re: [Dspace-devel] Authority control via METS / SWORD ingest?
Hi Stuart, yes you can set authority values via the METS ingester / SWORD as the authority key is now part of the DIM. You only need to write a custom XSLT that extract the authority key from the incoming xml file and reassemble it in the DIM: dim:field schema=dc element=contributor qualifier=author *authority=n79-21164 confidence=600* Mark Twain /dim:field Note that if you don't directly set an authority key using the XSLT / DIM process, the authority framework will ask the ChoiceAuthority plugin to do this calling the public Choices getBestMatch(String text,int collection,String locale); method. The description found in the wiki page https://wiki.duraspace.org/display/DSPACE/Authority+Control+of+Metadata+Values is up-to-date. Hope this help, Andrea Il 24/01/2011 07:48, Stuart Lewis ha scritto: Hi all, Apologies - but I don't know too much about the internals of the Authority Control system. Is it possible to pass metadata via the METS ingester / SWORD, that makes use of authority control? Thanks, Stuart Lewis Digital Development Manager Te Tumu Herenga The University of Auckland Library Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand Ph: +64 (0)9 373 7599 x81928 -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Dott. Andrea Bollini Project Manager, IT Architect Systems Integrator Sezione Servizi per le Biblioteche e l'Editoria Elettronica CILEA, http://www.cilea.it tel. +39 06-59292853 cel. +39 348-8277525 --- Disclaimer: the content of this email is confidential and may be privileged, and it must not be disclosed or copied without the sender's consent. If you have received this message in error, please notify the sender and remove it from your system. The content of this email does not constitute legal advice, nor any responsibility is accepted for loss or damage incurred as a result of acting upon its contents or attachments. The statements and opinions expressed in this email are those of the author and do not necessarily reflect those of the employer. -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] [Dspace-commit] [DSpace 3.0] - Request For Heads Up On Contributions
Hi all, I'm happy to say that CILEA and the Hong Kong University will work to release all the enhancements developed for the Hub (HKU IR) http://hub.hku.hk/ to the DSpace community. This could be a big contribution that will require some time to full happen. The features that we really want try to contribute in time for inclusion in the 3.0 are: - discovery for JSPUI http://hub.hku.hk/simple-search?sort_by=1query=submit=search - Improved statistics, data visualization http://hub.hku.hk/rp/stats/item.html?handle=10722/143976 - Pubmed Metrics http://hub.hku.hk/handle/10722/42292 (look on the left, at the citations box and the pubmed central count link) The most important feature, the Researcher Page ( http://hub.hku.hk/rp/rp00058 ), will be released as an addon/extension. I hope that we can find an easy way to add it to existent DSpace installation (1.8.2 or 3.0) as done for the discovery module. The Researcher Page module allows the istitution to show relevant information about her researchers, projects, facilities, etc. and re-use the same data to build authorities to use for metadata input as for example the item contributors. Some related presentations: http://hub.hku.hk/handle/10722/133863 http://hub.hku.hk/handle/10722/61139 http://hub.hku.hk/handle/10722/145800 At the next Open Repository there will be a presentation and a poster around these topics. https://www.conftool.net/or2012/index.php?page=browseSessionssearch=palmer Best, Andrea Il 04/06/2012 21:15, Sands Alden Fish ha scritto: Hi all, I'd like to put out a call for early notification of any enhancements or contributions that are intended to be committed for the DSpace 3.0 release. This does not constitute a commitment or adherence to any schedule (outside of the standard DSpace 3.0 schedule). The release team would just like to have an idea of anything that is coming down the pipe (especially major architectural changes that will impact other projects), so that we can know what this release is starting to look like, and what work will need to be done coordinating and testing contributions. (I will add a quick note here to say that it would be /fantastic/ if contributions were submitted with unit tests, to allow for easier testing and integration work, and a more robust release.) If there are contributions that you intend to make to this release, regardless of how small or large, please take a minute to add them on the following wiki page, under the New features in DSpace 3.0 (very tentative) section. https://wiki.duraspace.org/display/DSPACE/DSpace+Release+3.0+Notes Thanks from the DSpace 3 Release Team! -- sands fish Senior Software Engineer MIT Libraries Technology Research Development sa...@mit.edu mailto:sa...@mit.edu E25-131 -- 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-commit mailing list dspace-com...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-commit -- Dott. Andrea Bollini boll...@cilea.it ph. +39 06 59292853 - mob. +39 348 8277525 - fax +39 06 5913770 CILEA - Consorzio Interuniversitario http://www.cilea.it/disclaimer -- 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] BrowseDAO based on discovery: additional information
Hi all, I see that in the first replies to the vote for 3.0 inclusion nobody as expressed an opinion about BrowseDAO based on discovery. Trying to help who is still undecided I want to make some clarification: 1) the pull request has been already merged with the last discovery enhancement by atmire 2) before merge (if approved) I want make the following change: revert DBMS browse to be the default, revert solr search core schema configuration to index and persist any unspecified solrdoc field 3) the SOLR browse is Access Rights Awareness. As noted by Bram in JIRA comment ( https://jira.duraspace.org/browse/DS-1218?focusedCommentId=25910page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-25910 ) this complete the new discovery feature and in my opinion it keep the platform behavior more predicable 4) it can easly turned on/off and the code is really isolated, very small changes to the search services has been requested to implement it 5) I will take care of any issues that this contribution could introduce 6) the changes in the SOLR search service have introduced the support for proper manage authority in faceting and projection that was a big missing feature in Discovery Best, Andrea -- Dott. Andrea Bollini boll...@cilea.it ph. +39 06 59292853 - mob. +39 348 8277525 - fax +39 06 5913770 CILEA - Consorzio Interuniversitario http://www.cilea.it/disclaimer -- 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
Re: [Dspace-devel] multi-vote about remaining 3.0 tasks
A correction: #67 BrowseDAO based on discovery +4 2 -0 PASSED Andrea Il 08/09/2012 10:17, helix84 ha scritto: Hello, the voting deadline has passed, I'll try to tally the votes. This one is difficult, so please someone check my counts. This was a commiter vote, even though it was held in public place, I should have stressed that (sorry, Lyncode). I marked some failed votes as conditionally failed, which means that if voter's comments will be fixed, it will be merged. Hereby I'd like to ask those of you (mostly Andrea) who voted -1 to keep an eye out whether the conditions you stated were met and if they have, please do the merge. Technically, I assumed the -1 votes would be changed to 0 when all conditions were met (because I can't just assume +1), then I applied the normal voting conditions. #5 Maven Project Consolidation +60 -0 PASSED #46 Batch import from major bibliographic formats +41 -1 CONDITIONAL FAIL #47 Add tag cloud support in home page +30 -3 CONDITIONAL FAIL #48 Add support for concatenating multiple values in item display instead of line breaks +32 -1 CONDITIONAL FAIL #49 Auto update advance search drop down lists from configuration file +41 -1 CONDITIONAL FAIL #50 Allow date range searches in advance search +32 -1 CONDITIONAL FAIL #51 Display advance search form after an advance search +41 -1 CONDITIONAL FAIL #52 Display frequencies of items in single browsing for selected indices +32 -1 CONDITIONAL FAIL #53 Export items in various bibliographic formats +22 -2 FAILED #54 Show display values (input-forms) for controlled vocabularies in ItemTag +31 -2 CONDITIONAL FAIL #55 Indexing both stored and display-value from input-forms for search +30 -3 CONDITIONAL FAIL #60 Initial contribution: porting Discovery to the JSPUI +60 -0 PASSED #61 Enabling Dynamic DSpace Configuration Manager +04 -2 FAILED services#1 Dynamic configuration alternative (File based) +04 -2 FAILED #63 Statistics implementation in Elastic Search +32 -0 PASSED #67 BrowseDAO based on discovery +22 -0 PASSED #69 @mire solr statistics contribution +51 -0 PASSED #71 Controlled vocabulary support for the XMLUI +51 -0 PASSED #72 Atmire dspace 3.0 versioning contribution +60 -0 PASSED #73 authority field in Batch Metadata Editor +60 -0 PASSED #74 display bitstream read access permissions on item page +51 -0 PASSED #75 Configurable Workflow Improvements +50 -0 PASSED #76 Ldap improvements +50 -0 PASSED Still, someone needs to do the actual work of merging all the pull requests, so look if they're assigned and take them up if they're not! Thanks. I'll update the DSpace 3.0 Tasks wiki page with these results later (Sunday). Regards, ~~helix84 -- 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 -- Dott. Andrea Bollini boll...@cilea.it ph. +39 06 59292853 - mob. +39 348 8277525 - fax +39 06 5913770 CILEA - Consorzio Interuniversitario http://www.cilea.it/disclaimer -- 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] Need to update the I18N modules contribution
Hi all, as we are including changes in 3.0 that require changes and integration to the messages i18n files we should think about a release of the related modules https://github.com/DSpace/dspace-api-lang https://github.com/DSpace/dspace-xmlui-lang I think that the DCAT group could help here so I have added them in cc, sorry if this is not appropriate. A general call for translation could help too. Please note that in the last commit I have changed the key of a message used by the JSPUI: https://github.com/DSpace/DSpace/commit/12b4d6b296b4399f4ae707adf60e07bc08786c7e#L0L810 this mean that all the languages other than the default one (English) will show a bad ???...??? label in the advanced search. I'm not sure that this commit is the only that will cause similar issues but it will better if we have a strategy to fix these before the final release. Best, Andrea -- Dott. Andrea Bollini boll...@cilea.it ph. +39 06 59292853 - mob. +39 348 8277525 - fax +39 06 5913770 CILEA - Consorzio Interuniversitario http://www.cilea.it/disclaimer -- 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
Re: [Dspace-devel] IDE development issues with DSpace 3.0 + build.properties
Hi all,
I use eclipse with WTP (tomcat) but probably this method should be
applicable also to other IDE.
I edit the context.xml file in tomcat server configuration as follow
Context
!-- Default set of monitored resources --
WatchedResourceWEB-INF/web.xml/WatchedResource
!-- Uncomment this to disable session persistence across Tomcat
restarts --
!-- Manager pathname= / --
!-- Uncomment this to enable Comet connection tacking (provides
events
on session expiration as well as webapp lifecycle) --
!-- Valve
className=org.apache.catalina.valves.CometConnectionManagerValve
/ --
Parameter name=dspace-config value=e:/dspace3/config/dspace.cfg
override=false /
Parameter name=dspace.dir value=e:/dspace3 override=false /
Parameter name=LocalHostRestrictionFilter.localhost value=false
override=false /
Environment name=solr/home value=e:/dspace3/solr
type=java.lang.String
override=false /
/Context
this allow me to run without change or need to filter the web.xml the
JSPUI, XMLUI and SOLR.
Please note that there are a bug with apache tomcat 6.0.30-32 that
prevent this to work:
https://issues.apache.org/bugzilla/show_bug.cgi?id=50700
Hope this help,
Andrea
Il 18/10/2012 17:33, Robin Taylor ha scritto:
Very very quickly thrown together so just for discussion, you could do
something like...
In dspace/pom.xml
profiles
profile
idfilterwebxml/id
activation
property
namefilterwebxml/name
/property
/activation
properties
filter.booleantrue/filter.boolean
/properties
/profile
/profiles
and in dspace-jspui/pom.xml
filtering${filter.boolean}/filtering
And then activate the profile with 'mvn package -Dfilterwebxml'
On 18/10/12 15:12, TAYLOR Robin wrote:
Hi Tim,
I agree, its not ideal to require developers to edit the poms for this
purpose. Off the top of my head, could the resource element in the UI
pom be activated by a profile ? filtering would be set to true by
default but the developer would need to run 'mvn package -P
filterwebxml' , or something similar. I'll try it out if I get time.
Cheers.
On 18/10/12 14:45, Tim Donohue wrote:
Hi Robin,
On 10/18/2012 5:00 AM, Robin Taylor wrote:
Hi Tim,
I don't think it was a mistake. I think part of the original motivation
was to simplify the whole business of filtering but it may have been
simplified at the expense of some useful features. In the short term you
can cause any web.xml file to be filtered by setting
filteringtrue/filtering in the appropriate UI pom, would that
suffice ? Its set to false by default to allow filtering during the Ant
phase.
Thanks for the response suggestion. That could be a possible
workaround. Though, admittedly, I think that's less developer/IDE
friendly than before.
Personally, I'm not a fan of requiring developers to tweak the POM
source code before they can successfully enable webapp debugging in
their IDE. I think that's my main point of frustration here -- it used
to be a simple maven flag you set in your IDE
(-Ddspace.config=[path-to-dspace.cfg]) that let you run a webapp from
your IDE, and now you actually have to dig into Maven POM(s) and edit them.
If there was a way to support webapp debugging out-of-the-box again
alongside the new build.properties, I think that'd be ideal. I'm gonna
dig around a bit more myself to see if I can get it working let
everyone know what I come up with.
If anyone else comes up with other alternatives, let me know.
Essentially, as far as I can tell, running a DSpace webapp from *any*
IDE is not going to work properly unless you edit the POMs. The reason
is that variables in the web.xml files are no longer filtered via Maven
-- instead they get filtered later on via Ant, as Robin mentions.
In the long term I think the problem is that we use dspace.cfg to filter
dspace.dir in web.xml, but dspace.cfg already lives in dspace.dir, its
all a bit contrary. My feeling is that dspace.dir should be set outwith
the webapp, by an environment variable or some such, so that the same
webapp can be used in multiple environments without having to be rebuilt
or refiltered.
I agree with you on this. The underlying problem is just that we have a
messy way of doing things. I agree too that maybe dspace.dir really
should be a system environment variable (DSPACE_HOME) or something like
that. Something to think about for 4.0 next year.
- Tim
--
Dott. Andrea Bollini
boll...@cilea.it
ph. +39 06 59292853 - mob. +39 348 8277525 - fax +39 06 5913770
CILEA - Consorzio Interuniversitario
http://www.cilea.it/disclaimer
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Re: [Dspace-devel] Startup sequence, ConfigurationService vs. ConfigurationManager, and the nature of the services framework
Hi Mark,
I'm trying, without success, to reproduce the issues that I have
reported during the last IRC developer chat (early access to
configurationservice cause issues).
Digging in our current code (not yet shared on github for the
dspace-cris project :-( ) I see that we use with success the
ConfigurationService. We inject it in a Factory that produce a
datasource suitable for initialize an Hibernate session...so as
far I can see... no issues in early use
Looking to our internal svn history I see a note that say that a
previous attempt done using ConfigurationManager fails because the
ConfigurationManager was not fully initialized during the spring
context startup.
Sure the ConfigurationService and ConfigurationManager have
different lifecycle and this is confusing.
About this sentence
The only reason why a
ConfigurationService is created first seems to be that we want to be
able to configure additional Spring configuration files to be loaded
in some cases. Since this seems to be only for testing -- it only
ever appears in a test Properties resource -- we should probably find
some other way to provide this one String and not use the main
configuration code to fetch it.
We use it to configure the location of the spring configuration
files for additional module (for example dspace-cris add it own
org.dspace.kernel.config.SpringLoader to allow the override of
default configuration in dspace/config/spring/cris/*.xml)
Of course we can decide to remove the need of such configuration
introducing the convention to read anything under
dspace/config/spring/*/*.xml
I'm not sure about the advantage vs complexity to wrap the Spring
container in our custom infrastracture, at the moment I can only
see complexity issues, the advantage (to be uncoupled with spring)
that I can imagine is only theoretical and will require a lot of
work to be real (we need to produce other servicemanager, we need
to change a lot of configurations/documentations as we are going
to configure everything as spring beans).
Sure the 2.0 team that has produced the dspace-services
infrastructure can talk more about advantages.
Andrea
Il 09/05/2013 17:46, Mark H. Wood ha scritto:
Digging into the code, I find that there is no GuiceServiceManager.
In fact the only extensions of ServiceManagerSystem are
DSpaceServiceManager (the one we actually call),
MockServiceManagerSystem, ExternalServiceManagerSystem (a
subinterface), and SpringServiceManager.
So DSpaceServiceManager is managing a list of one ServiceManagerSystem
which is always SpringServiceManager. This can probably be
simplified.
If there were only one ServiceManager, it could create a
ConfigurationService whenever it needs to. In the case of
SpringServiceManager it could create the ApplicationContext before the
ConfigurationService -- in fact the chosen ConfigurationService could
be specified in the ApplicationContext's configuration if that were
useful, and injected to key objects. The only reason why a
ConfigurationService is created first seems to be that we want to be
able to configure additional Spring configuration files to be loaded
in some cases. Since this seems to be only for testing -- it only
ever appears in a test Properties resource -- we should probably find
some other way to provide this one String and not use the main
configuration code to fetch it. Possibly it could be a system
property or a Context parameter. Making that change removes the
sequencing requirement for ConfigurationService and
ApplicationContext.
I have never been able to figure out why one would want more than one
ServiceManager running in a given instance of DSpace. (Nor can I see
why we would want more than one Kernel, which is also provided for.)
Comments?
--
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
--
Andrea
Bollini
Dipartimento Servizi e Soluzioni per
l'Amministrazione Universitaria
Divisione Ricerca
Via de
[Dspace-devel] R: Re: Bizarre DSpace Browse Failure
Not really. The SOLRBrowseDAO works for both jspui than xmlui. You don't need a custom aspect because it implements exactly the same API than the DBMS browse dao, in fact you need to set it as the browsedao plugin implementation. As helix says it is not enabled by default in 3.x Andrea Inviato da Tablet Samsunghelix84 heli...@centrum.sk ha scritto:No, you can't remove them yet. The browse aspect still depends on them. That's the one that renders the /browse urls. Advanced search is handled by Discovery if you enabled Discovery. The next step in Discovery development is to make the discovery aspect render the browse indices, but that code doesn't exist yet for XMLUI (only for jspui and it's not enabled by default). On May 20, 2013 8:22 PM, Hilton Gibson hilton.gib...@gmail.com wrote: I tried using our browse index today (http://scholar.sun.ac.za) to find all titles with knowledge economy. It did not work as well as the advanced search, which I assume is based on the solr discovery service. I am thinking of removing the browse indexes. We have discovery, advanced search and of course google scholar to do searches with. Are the browse indexes useful and accurate? Comments on the list welcome, I am sitting undecided, on the fence, with this one. Cheers hg On 20 May 2013 19:02, Sands Alden Fish sa...@mit.edu wrote: Ivan, thanks for the pointer. This is one aspect of repo administration I've never had to deal with in the past. It is possible that the previous tech lead on this project modified those settings without re-running index-init. I assume there's no issue with rerunning index-init as many times as needed? Do you have to rebuild the indexes after re-running that, or is that just taken care of as part of the process? -Sands P.S. - hg, thanks for the link, it's useful to see your process written out. From: ivan.ma...@gmail.com [ivan.ma...@gmail.com] on behalf of helix84 [heli...@centrum.sk] Sent: Monday, May 20, 2013 12:11 PM To: Sands Alden Fish Cc: dspace-devel@lists.sourceforge.net Subject: Re: [Dspace-devel] Bizarre DSpace Browse Failure On Mon, May 20, 2013 at 6:03 PM, Sands Alden Fish sa...@mit.edu wrote: We have Discovery turned off. Any help or hints would be appreciated. The table bi_2_dis does not seem to be specified anywhere in the codebase. Hi Sands, the bi_2_dis table belongs to the second browse index (webui.browse.index.2) and has to be regenerated after changing that property. Those properties also have to be numbered sequentially with no gaps. I'm only pointing that out because you tried to look it up in the codebase, while it's in fact generated by index-init. I assume you have tried running index-init, have you? Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Hilton Gibson Systems Administrator JS Gericke Library Room 1025C Stellenbosch University Private Bag X5036 Stellenbosch 7599 South Africa Tel: +27 21 808 4100 | Cell: +27 84 646 4758 http://library.sun.ac.za http://scholar.sun.ac.za http://ar1.sun.ac.za http://aj1.sun.ac.za-- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] Item state definitions
As agreed in yesterday dev meeting I have start a page to gather informations about DSpace state. https://wiki.duraspace.org/display/~bollini/DSpace+Item+state+definitions Please note that I'm not an experienced user of the wiki so if it is appropriate, preferable to move the page in other space just let me know (also direction on how to make this move will be appreciate ;-) ) Andrea -- Andrea Bollini Dipartimento Servizi e Soluzioni per l'Amministrazione Universitaria Divisione Ricerca Via dei Tizii, 6 00185 Roma, Italy tel. +39 06 59 292 853 - mob. +39 348 82 77 525 http://www.cineca.it -- Try New Relic Now We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Ability to map collections to multiple communities - your opinion
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 Il 31/07/2013 11:27, Kostas Stamatis ha scritto: Dear developers, I would like to ask your opinion regarding the issue https://jira.duraspace.org/browse/DS-491for the ability to map collections to multiple communities. There are some issues that arose while trying to implement this feature. I mention them here: 1) Who will be able to do these assignments? Sys admin? Or the community admin as well? What happens when the community admins (from the communities that will host the same collection) are different? Should we permit only from an edit community form to specify the child collections or should we also allow in edit collection form parent communities to be specified? 2) What happens with the collection policies? If the collection policies are inherited from the parent community, if this collection belongs to a new community as well, and the second community has different policies, which community's policies will be inherited by the collection? 3) Regarding UI, in a collection's home page, the breadcrumb displays the father community. As long as this collection has one parent community this works well. What should happen if there are two parent communities? 4) The same problem can be found also in the same page in the search box in the select scope. Which community must appear there? During the last dev meeting on Weds, July 24, 2013, we discussed some of them (https://jira.duraspace.org/browse/DS-491?focusedCommentId=28722page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28722) Most of us agreed that the collection must have an owning community which is always the community under which the collection was initially created. Thus, I guess this solves problem number 2 but not 1, 3 and 4. 3 and 4 can be solved if we display the owning community in the breadcrumb (I do not know if this is correct). I would like to hear your opinion in order for this issue to be solved and be included in 4.0. Regards, Kostas Stamatis -- 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=49501711iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Andrea Bollini Dipartimento Servizi e Soluzioni per l'Amministrazione Universitaria Divisione Ricerca Via dei Tizii, 6 00185 Roma, Italy tel. +39 06 44 486 087 - mob. +39 348 82 77 525 http://www.cineca.it -- 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
Re: [Dspace-devel] collaborating on branches/pull requests
issue: actually we don't have a really plugin/addon mechanism for dspace. Any contribution need to make some customization to the DSpace core to be able to compile/integrate their features (sometimes to the pom files others also to java classes). For DSpace-CRIS we have had to setup several branch on the CILEA/DSpace fork to manage such integration I'm sorry, I have more issues to report than answers. A long term solution requires that: 1) we need to have a real plugin/addon mechanism 2) we need to setup a directory of hight rated/supported addon (incubation) and a directory of trusted, available out of box, addons 3) we need a market place Andrea Do you approve? Disapprove? Have any comments? Do you have any additional use cases that could be adressed by shared repositories? Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- 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=48897031iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Andrea Bollini Dipartimento Servizi e Soluzioni per l'Amministrazione Universitaria Divisione Ricerca Via dei Tizii, 6 00185 Roma, Italy tel. +39 06 44 486 087 - mob. +39 348 82 77 525 http://www.cineca.it -- 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=48897031iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] Best practice to merge a PR
Hi all, I'm doing some experiment to understand the best way to manage PR (sorry for the long email). First: I like to do rebase, long running branch make the history graph hard to understand (I also like to squash micro commit when done by the same author). Second: I dislike to see a PR marked by github only as closed when it is really merged (probably github could provide in a near future statistics about the nr of pull requests and the % of acceptance). This mean also that close a PR to make a new rebased PR is not a best practice for me. So for the pull request 241 I have done the following from my command line $ git remote -v bramhttps://github.com/bram-atmire/DSpace (fetch) bramhttps://github.com/bram-atmire/DSpace (push) dspace https://github.com/DSpace/DSpace (fetch) dspace https://github.com/DSpace/DSpace (push) kevin https://github.com/KevinVdV/DSpace (fetch) kevin https://github.com/KevinVdV/DSpace (push) lap82 https://github.com/lap82/DSpace (fetch) lap82 https://github.com/lap82/DSpace (push) mwood https://github.com/mwoodiupui/DSpace (fetch) mwood https://github.com/mwoodiupui/DSpace (push) origin https://github.com/abollini/DSpace (fetch) origin ... and many other :-) git pull dspace master git checkout -b DS-1432 git pull kevin DS-1432 git rebase master git checkout master git merge -m Merge pull request #241 rebased --no-ff DS-1432 git push origin master git push dspace master in this way I get the PR 241 to automatically note my commit https://github.com/DSpace/DSpace/pull/241#ref-commit-15ed2fb unfortunately it refers to my repository probably due to have push first to my origin... After this step the PR was still open on GitHub... but also automatically mergeable so I have closed it manually. But, trying to see what could happen clicking on the git merge button I have made a test on my local git repository on a new branch $ git checkout -b test Switched to a new branch 'test' bollini@BOLLINI-P-NEW /e/dspace4/source/DSpace (test) $ git merge kevin/DS-1432 Merge made by the 'recursive' strategy. bollini@BOLLINI-P-NEW /e/dspace4/source/DSpace (test) $ git diff master bollini@BOLLINI-P-NEW /e/dspace4/source/DSpace (test) $ git log commit f89802d41feab6dd23f60b0cf53fb4a7f41e5321 Merge: 15ed2fb 74e615c Author: Andrea Bollini a.boll...@cineca.it Date: Fri Sep 6 10:42:57 2013 +0200 Merge remote-tracking branch 'kevin/DS-1432' into test commit 15ed2fb52c89e7bfc1ac1bef67944d2c791f7cbf Merge: 90c86da b3aca64 Author: Andrea Bollini a.boll...@cineca.it Date: Fri Sep 6 10:36:33 2013 +0200 Merge pull request #241 rebased IMHO this mean that if I do a fast forward merge for a rebased pull request and after just push the green botton of github we are able to achieve clean history and proper statistics for PRs? what do you think? any tips from git/github experts? Andrea -- Andrea Bollini Dipartimento Servizi e Soluzioni per l'Amministrazione Universitaria Divisione Ricerca Via dei Tizii, 6 00185 Roma, Italy tel. +39 06 44 486 087 - mob. +39 348 82 77 525 http://www.cineca.it -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] R: Re: JSPUI Bootstraped
Hi Joao, yes please join us to complete the restylish of jspui, I want include our PR in 4.0 Currently I think that we have covered the 90/95% of pages/functionalities from both public and backoffice side. The missing one should still work but look old/messy. My collegue Luigi Andrea Pascarelli is working on the final check and functionalities (as for example js input in submission:authority and controlled vocabulary). Best, Andrea Inviato da Tablet SamsungKostas Stamatis kstama...@ekt.gr ha scritto:Hello Joao, how are you doing? There is currently a PR from Andrea regarding the look feel of JSPUI ( https://github.com/DSpace/DSpace/pull/321 https://github.com/DSpace/DSpace/pull/321). It seems to be similar work from the two sides J: JSPUI and Bootstrap. Regarding your question: “Would it be a good addition?” the answer is definitely YES, the oldish DSpace (JSP)UI needs a new refreshing look feel style! Regards, Kostas From: João Melo [mailto:jm...@lyncode.com] Sent: Thursday, October 10, 2013 2:00 AM To: dspace-devel Subject: [Dspace-devel] JSPUI Bootstraped Hi all, I've been trying to bootstrap the JSPUI. There is some work left to do, but, I guess it may help the community producing more stylish DSpace designs. What do you think? Would it be a good addition? From my analysis, the good thing is that we could then use what bootstrap http://getbootstrap.com/ (v3) has to offer. However, this will be a disruptive change in the way that is a heavy change to the previous JSPUI styling philosophy. Demo: http://demo-dspace.lyncode.com:8080/ -- http://www.lyncode.com/images/lyncode/N.png Thanks, João Melo (My Portfolio http://www.lyncode.com/m/jmelo/ ) DSpace Department Lyncode: http://www.google.com/url?q=http%3A%2F%2Fwww.lyncode.com%2Fsa=Dsntz=1usg =AFrqEzdV8iS6rMxflxnn138XReuRfUG3OQ Official website http://www.google.com/url?q=http%3A%2F%2Ftwitter.com%2Flyncodesa=Dsntz=1; usg=AFrqEzeDuT3ZqMW5uVIA8AoxtTtAeiCX3Q Follow us on Facebook http://www.google.com/url?q=http%3A%2F%2Fwww.facebook.com%2Flyncodesa=Dsn tz=1usg=AFrqEzcWXjHa3gKBGLsNVxktapxkiWDnww -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] New look feel for JSPUI in 4.0
*** apologies for cross posting *** Hi developers, as agreed in the last special IRC meeting dedicated to the PR review for 4.0 http://irclogs.duraspace.org/index.php?date=2013-10-11 (starting from 15:36 ) me and Andrea Pascarelli have made the PR #321 https://github.com/DSpace/DSpace/pull/321 https://github.com/CILEA/DSpace/tree/bootstrap ready to merge and I will push the green button *tomorrow at 14 October 2013, 10 am EDT.** **http://www.timeanddate.com/worldclock/fixedtime.html?msg=Merge+of+new+JSPUI+look%26feeliso=20131014T16p1=215* We can fix any minor issues or restylish eventually missing pages later but it is required that this PR go in as soon as possible to allow better testing and avoid conflict with other pending PR. *What is it?** *This PR will completely change the lookfeel of the JSP UI switching from a table based layout to a fluid layout build upon Bootstrap3 (the CSS framework providen by Twitter and used by GitHub and much other, see: http://getbootstrap.com/ ) The bootstrap framework itself promise to make our new layout responsive, some behaviour are already implemented as the collapsing of the navigation bar to the app menu icon in small device, others can be introduced as further enhancements. Anyway the fluid layout should assure, unlike now, that the UI is fully usable also in tablet and phone. We have tried to restylish all the pages (both public and administrative/submission), some minor functionalities could be miss but as we have seen during the revision this normally mean that the content block look no so good as the other pages but all should still work and be readable. Many screenshots of the new layout are available on the JIRA Issue: https://jira.duraspace.org/browse/DS-1675 anyone interested in the JSPUI is asked to checkout the branch and start to familiarize with it. *About the migration:* No special actions are required to activate the new look feel. Users that have done personalization in the JSPUI are required to reapply their changes to the new jsp most likely as they have done in past upgrade. New jsp should work out of box but the content block should look old. JSP code should look more clean with many html twicks removed (center tag, fake table, etc.) and easy to customaze moving div block to rearrange the content in the page. CSS manually tweks should, at least in this first version, not required/useful to make customizations. The best way to change the theme is to use UIs to build custom bootstrap theme Bootstrap theme generator: http://getbootstrap.com/customize/ JQueryUI theme roller (we use redmond in the out-of-box theme): http://jqueryui.com/themeroller/ -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] R: private vs. withdrawn items: some concerns questions
Tim, you are rigth there are major issues with the current implementation. If you do a submission as a normal user (not an administrator) and there are no workflow you will get also an internal error (due to lack of permission to perform the withdrawn). As this is a bug I have that currently on my to do list for 4.0 after the feature freeze. Sorry to haven't share this info before(probably I should also fire a jira issue for that...) Andrea Inviato da Tablet SamsungTim Donohue tdono...@duraspace.org ha scritto:Hi all, I know we've had this discussion before, but all I seem to get is more and more confused about what a private item is supposed to mean. Andrea did a good job previously of trying to define the differences here: https://wiki.duraspace.org/display/~bollini/DSpace+Item+state+definitions But, we have an oddity in the implementation of private vs. withdrawn item. Essentially *both* of these types of items are effectively withdrawn items. Clicking Make Private does the following: 1. sets 'discoverable=false' 2. withdraws the item from the archive https://github.com/DSpace/DSpace/blob/master/dspace-xmlui/src/main/java/org/dspace/app/xmlui/aspect/administrative/FlowItemUtils.java#L329 The odd thing is that withdrawing an item already makes it no longer visible/findable (what is discoverable=false even adding?). So, why do we have this new make private option anyways? It's also worth noting that withdrawing an item removes it from the in_archive state, which means the item is no longer being checked by things like the Checksum checker (and can no longer be processed by things like Curation Tasks, since they only operate on in_archive Items, as Collection.getItems() only returns that) https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/content/Item.java#L1866 Conclusion: Private items are no longer in_archive, and therefore are not really being preserved/maintained in the same way as a normal item. They are ignored by the Checksum Checker, by Curation Tasks, and likely other things. Is it just me, or does this sound like a major bug in how 'private' items are being handled? Or maybe I'm still just confused here? - Tim -- Tim Donohue Technical Lead for DSpace DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135031iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135031iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] R: Re: R: private vs. withdrawn items: some concerns questions
yes, private items should not be withdrawn. Probably it is sufficient to remove the withdrawn / restore call from the make private method and merge my PR about the fix for private items searcheable in discovery (https://github.com/DSpace/DSpace/pull/183 ). Anyway I plan to look to these issues next week if other can jump in first I will be glad. Andrea Inviato da Tablet SamsungTim Donohue tdono...@duraspace.org ha scritto:Hi Andrea, A brief followup. I've verified the other bug you mentioned. So, I logged two new JIRA tickets related to private items: https://jira.duraspace.org/browse/DS-1711 (Private items should not be withdrawn) https://jira.duraspace.org/browse/DS-1712 (AuthorizeException when a Non-admin marks item as private) Feel free to claim one (or more) of them if you plan to work on it. As mentioned, I'd be glad to help do some testing, etc. Others are more than welcome to chime in on these ideas or help with fixes as well. There definitely seems to be a bit of cleanup to be done here. - Tim On 10/17/2013 1:31 PM, Tim Donohue wrote: Hi Andrea, In my opinion, if we are going to have private items, they should NOT be withdrawn. It seems more reasonable that they should just be normal items where discoverable=false and in_archive=true (i.e. they are not withdrawn, instead they are just hidden from search/browse) I just entered another ticket related to both withdrawn private items -- in either case they reset any special permissions/embargo on an Item. So, if you set an Embargo on an Item, and then temporarily make it private (e.g. maybe you realized there was a mistake somewhere and wanted time to fix it), as soon as you make the Item available again (make public), the previous embargo/special permissions are overridden and the Item is make immediately public. See: https://jira.duraspace.org/browse/DS-1710 I'd also love to see these private items issues get cleaned up for 4.0. I'm not sure if I'll have much time to do coding. But, I'd gladly help with testing any fixes. - Tim On 10/17/2013 1:17 PM, Andrea Bollini wrote: Tim, you are rigth there are major issues with the current implementation. If you do a submission as a normal user (not an administrator) and there are no workflow you will get also an internal error (due to lack of permission to perform the withdrawn). As this is a bug I have that currently on my to do list for 4.0 after the feature freeze. Sorry to haven't share this info before(probably I should also fire a jira issue for that...) Andrea Inviato da Tablet Samsung Tim Donohue tdono...@duraspace.org ha scritto: Hi all, I know we've had this discussion before, but all I seem to get is more and more confused about what a private item is supposed to mean. Andrea did a good job previously of trying to define the differences here: https://wiki.duraspace.org/display/~bollini/DSpace+Item+state+definitions But, we have an oddity in the implementation of private vs. withdrawn item. Essentially *both* of these types of items are effectively withdrawn items. Clicking Make Private does the following: 1. sets 'discoverable=false' 2. withdraws the item from the archive https://github.com/DSpace/DSpace/blob/master/dspace-xmlui/src/main/java/org/dspace/app/xmlui/aspect/administrative/FlowItemUtils.java#L329 The odd thing is that withdrawing an item already makes it no longer visible/findable (what is discoverable=false even adding?). So, why do we have this new make private option anyways? It's also worth noting that withdrawing an item removes it from the in_archive state, which means the item is no longer being checked by things like the Checksum checker (and can no longer be processed by things like Curation Tasks, since they only operate on in_archive Items, as Collection.getItems() only returns that) https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/content/Item.java#L1866 Conclusion: Private items are no longer in_archive, and therefore are not really being preserved/maintained in the same way as a normal item. They are ignored by the Checksum Checker, by Curation Tasks, and likely other things. Is it just me, or does this sound like a major bug in how 'private' items are being handled? Or maybe I'm still just confused here? - Tim -- Tim Donohue Technical Lead for DSpace DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135031iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https
[Dspace-devel] Fwd: Re: [Dspace-general] Request for information on repository request-copy Button
Hi Eloy, we are trying to include a Request Copy feature out-of-box in DSpace 4.0. Actually we have a PR for the XML UI that is based on your addon https://github.com/DSpace/DSpace/pull/338 I'm trying to upgrade the last code that I found for JSP UI here http://projecto.rcaap.pt/index.php/lang-pt/consultar-recursos-de-apoio/remository?func=fileinfoid=358 you can found my experiment here: https://github.com/abollini/DSpace/tree/DS-824 Today, is the last day to merge new feature in the master for DSpace 4.0. I will appreciate if you can give a try to my public branch (still work in progress), provide feedback or better help me to complete the JSPUI side. Andrea Messaggio originale Oggetto: Re: [Dspace-general] Request for information on repository request-copy Button Data: Thu, 17 Oct 2013 21:27:20 -0400 Mittente: Stevan Harnad amscifo...@gmail.com A: Global Open Access List (Successor of AmSci) g...@eprints.org CC: dspace-gene...@lists.sourceforge.net -- Forwarded message -- From: *Eloy Rodrigues* eloy---sdum.uminho.pt http://eloy---sdum.uminho.pt Date: Thu, Oct 17, 2013 at 4:23 PM Dear Stevan, I completely support the request to have the ?Request Copy? functionality embedded in the ?vanilla? DSpace versions. We?ve been upgrading the Request Copy Add-on (for the jsp interface, that it?s the one we are using) since we first developed it. We are currently upgrading the Add-on for DSpace 3.2 (we are upgrading our repository to DSpace 3.2), and the ?production? version of the Add-on is for DSpace 1.8xx repositories. We are obviously willing to contribute the Addon code to be included in the DSpace core, and strongly support that integration. Best, Eloy Rodrigues Direcção Campus de Gualtar, 4710 - 057 Braga - Portugal Telefone +351 253 604 156/7/8; Fax +351 253 604 159 tel:%2B351%20253%20604%20159 Campus de Azurém, 4800 058 Guimarães Telefone +351 253 510 168 tel:%2B351%20253%20510%20168; Fax +351 253 510 117 tel:%2B351%20253%20510%20117 http://www.sdum.uminho.pt http://www.sdum.uminho.pt/| Siga-noscid:image002.gif@01CC2142.3D962530 http://www.facebook.com/pages/Braga-Portugal/Bibliotecas-da-Universidade-do-Minho/78518268502cid:image003.gif@01CC2142.3D962530 http://twitter.com/bibliotecasUM -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135031iu=/4140/ostg.clktrk ___ Dspace-general mailing list dspace-gene...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-general -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135031iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] DSpace REST API
Hi Kostas,
here my viewpoint
1) I prefer the header method. A missing header should be read as the
current version.
2) I agree with you. It is usually to find a common template across REST
API implementation and we should follow the common practice
3) Detailed errors information are desirable so also in this case, I
agree with you about the opportunity to introduce a response error object
Andrea
Il 04/11/2013 10.13, Kostas Stamatis ha scritto:
Dear developers,
I have some comments, regarding the Jersey Rest API, after a
discussion we had with Peter Dietz in the dspace IRC channel some
days ago.
1) REST API versioning
---
As read from some sites and blogs, the versioning of a REST API can
be denoted either in the URL or in the mime type of the HTTP
communication (in the Accept and Content-Type header fields).
ex1: http://example.dspace.com/rest/v1/communities
ex2:
===
GET /communities HTTP/1.1
Accept: application/vnd.dspace.rest-v1+json
===
HTTP/1.1 200 OK
Content-Type: application/vnd.dspace.rest-v1+json
Either has advantages and disadvantages, as I read. For example, the
former is said to be wrong since the same resource may have more than
one URIs pointing to it. The latter helps the backward compatibility.
From what I read, I think that most preferable is the second method.
[1], [2]. [3] and [4] are for reference.
We would like to hear your opinion on that.
2) REST API responses
---
I had the chance to play around with the REST API the previous days.
What I noticed is the heterogeneity of the responses. communities
JSON endpoint returns an array while the communities/{id} endpoint
returns a map. I would expect, all the responses to return the same
response template within which someone can find the actual response.
Something like the real response being wrapped around another object
that has other fields as well. This template has the following pros:
i) Other metadata can be inserted in the response, like the request
params, the api version, the response time of the server (and I guess
others as well)
ii) It helps the backward compatibility, since the response can change
in the future by adding new metadata in it, but clients can still
operate correctly. As it is now, any addition (apart from within the
actual response) will break any client.
iii) Clients can benefit from having a general parser to parse the
template and more specific ones to parse the actual response.
Again, we would like to hear your opinion on that.
3) REST API error responses
--
At this time, errors are returned as HTTP status errors which is fine.
There is also the option (not implemented yet) errors to be returned
as part of a valid response. That is, the aforementioned template
could include metadata about the status of the response, the error
code (if exists) and a localized message. Of course, HTTP status
errors, in some cases, could also apply.
When the error is embedded in the response, the actual error problem
could be sent to the user instead of just an HTTP error code.
Once again... we need you opinion here as well.
Best regards,
Kostas Stamatis
[1] http://barelyenough.org/blog/2008/05/versioning-rest-web-services/
[2]
http://barelyenough.org/blog/2008/05/versioning-rest-web-services-tricks-and-tips/
[3]
http://jersey.576304.n2.nabble.com/Restful-Service-Versioning-td6332833.html
[4]
http://stackoverflow.com/questions/389169/best-practices-for-api-versioning/6750376#6750376
--
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
--
Andrea Bollini
Dipartimento Servizi e Soluzioni per l'Amministrazione Universitaria
Divisione Ricerca
Via dei Tizii, 6
00185 Roma, Italy
tel. +39 06 44 486 087 - mob. +39 348 82 77 525
http://www.cineca.it
--
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] upgrade 3.2 a 4 , dspace solr problems
if the index are (all the segments from all the cores) in a 3.x version of lucene, solr 4 is able to read them. If you have a running copy of dspace 3.x you can just hit all the solr cores for optimize wget http://yoursolrurl[:port]/solr/search/update?optimize=true wget http://yoursolrurl[:port]/solr/statistics/update?optimize=true check also point 10 of the installation procedure https://wiki.duraspace.org/display/DSDOC4x/Upgrading+From+3.x+to+4.0 hope this help, Andrea PS: if you still have issues please be sure to post the log of the solr server both from solr.log* and catalina.out* Il 21/01/2014 16.22, jnempu ha scritto: Hi guys, i understand that Dspace 4 works with solr 4. So i been upgrading since 1.4.2 version. So everything goes well up to 4 version upgrade. I run all commands like: - dspace-index-init - dspace-index-update - dspace-discovery - etc- , with no results. So the question is , how can i transfrom my old index into the new Solr4. The index in statics ara in 3.x version of lucene. Thanxs in advance. -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Andrea Bollini Dipartimento Servizi e Soluzioni per l'Amministrazione Universitaria Divisione Ricerca Via dei Tizii, 6 00185 Roma, Italy tel. +39 06 44 486 087 - mob. +39 348 82 77 525 http://www.cineca.it -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] A more efficient Git Workflow?
Hi all, I have found this well documented git workflow adopted by another open source project http://www.net-snmp.org/wiki/index.php/Git_Workflow essentially it looks as we are managing in an inefficient way the bug fixing of old release (i.e. 3.x, 1.8). They merge bug fix on the old release maintenance branch where the bug is present and merge upward (1.8.x - 3.x - 4.x - master), instead it looks as we are essentially recommending to work always on the master. Andrea -- Andrea Bollini Dipartimento Servizi e Soluzioni per l'Amministrazione Universitaria Divisione Ricerca Via dei Tizii, 6 00185 Roma, Italy tel. +39 06 44 486 087 - mob. +39 348 82 77 525 http://www.cineca.it -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] A more efficient Git Workflow?
Hi Ivan, you are right our community is different... probably we will be never (or not in a short/medium time) able to manage 3 real maintenance versions but we have a least 2 active versions, the 4.x and the next one (5.0 snapshot). According to this workflow it looks better manage bugs as PR against 4.x than as PR against the master. In this way if we miss to merge something to the master we can do it later also in one go for multiple patches/bug fixes. The opposite direction is not so easy as it requires cherry pick and is untracked by git, so we need to assure by ourself that we don't miss bug fix. Also the famous GitFlow branching model http://nvie.com/posts/a-successful-git-branching-model/ suggest to work on the maintenance branch and after merge that in the develop branch (in our case the master). Andrea Il 23/01/2014 12.36, helix84 ha scritto: Hi Andrea, I don't think this workflow would currently work for us. The reason is that we're letting bugs sit for too long before we get to them. I bet you can still find bugs filed against DSpace 1.5 that were never fixed. Even patches tend to sit for a long time before we review them. As I see it, it would happen quite often that a PR would be filed today against the 1_8_x branch. When we finally resolve it in 2 years (unfortunately, this is really not uncommon for us), that branch will be long unsupported and the oldest supported branch in that time will be 4_x. That will require one more task. So much for the disadvantages. As for advantages, I don't really see any. There's not really a difference in porting effort in one direction or the other (e.g. 3-4 vs. 4-3). As a developer, you're probably already working on a branch close to master, so it's easier for you to just fix things in the current DSpace version than check out an older one, fix it there and build it; no advantage there, either. Moreover, we declared the last 3 releases supported for security bug fixes. We didn't say anything about bug fix support. After a new major version is released, it's very rare for us to release a minor version of the previous release. There's a lot we would have to improve in our processes (time to fix bugs, actual support for previous releases) before we could consider this change in Git workflow. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Andrea Bollini Dipartimento Servizi e Soluzioni per l'Amministrazione Universitaria Divisione Ricerca Via dei Tizii, 6 00185 Roma, Italy tel. +39 06 44 486 087 - mob. +39 348 82 77 525 http://www.cineca.it -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] A more efficient Git Workflow?
Il 23/01/2014 15.10, helix84 ha scritto: On Thu, Jan 23, 2014 at 2:41 PM, Andrea Bollini a.boll...@cineca.it wrote: According to this workflow it looks better manage bugs as PR against 4.x than as PR against the master. In this way if we miss to merge something to the master we can do it later also in one go for multiple patches/bug fixes. We currently do the opposite - as soon as we decide a minor release is coming out, we scour master for bugfixes and backport them. This is a manual, error prone, boring, activity... The two approaches are really interchangable and equally difficult, so as long as we stick to either one of them, we should be fine. No really. Assuming that we are doing the thing well (all the patches go in 4.x) we can release a 4.1 at any time without any activity and at the time of feature freeze we just need to run git merge dspace-4.x from the current master to assure that all the bugs go in the next 4.1. The opposite direction is not so easy as it requires cherry pick and is untracked by git, so we need to assure by ourself that we don't miss bug fix. I'm not sure what you mean by untracked by git. Do you mean regular merges of the release branch to the master branch after each fix is commited to the release branch? You're right in that this is not possible to do in the other direction because on master, there are non-bugfix changes intermingled with bugfixes. But a merge is something you have to do from the command line (i.e. GitHub doesn't make it easier; we can also think about make post-hock on git so to trigger an automatic merge over the master when a commit is done in the maintenance branch. This sound probably adventurous but it is usually in enterprise workflow where there is a QA phase and CI (moreover we have both... testhaton and Travis/Bamboo). Andrea well, unless you want to fire additional PRs for the same thing, which we recently agreed is not a good thing because it fragments the discussion to many places), just like cherry-pick. What advantages do you see to a merge as opposed to a cherry-pick? Or did you mean something else? Also the famous GitFlow branching model http://nvie.com/posts/a-successful-git-branching-model/ suggest to work on the maintenance branch and after merge that in the develop branch (in our case the master). Like I said above, the important thing is to standardize on one way. This happens to describe the other way that the one we use, but I really see no advantages to it. Oh, and I forgot to mention one advantage to our current model I see. It assures that if we forget to port the bugfix, it will be in all subsequent releases, it will only miss from an old release. In the reverse scenario, if we forget, it's fixed in the old version and not in the future versions. I admit this doesn't happen to us very often, but it's possible. The second important advantage is in case of conflict (i.e. for complex fixes that touch code with unrelated changes between the two branches). If we fix on master and have a problem with conflicts that are hard to resolve, we can just decide to give up on the fix for old release. If we start from the old one, we *have to* push through to fix the the newer branch. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Andrea Bollini Dipartimento Servizi e Soluzioni per l'Amministrazione Universitaria Divisione Ricerca Via dei Tizii, 6 00185 Roma, Italy tel. +39 06 44 486 087 - mob. +39 348 82 77 525 http://www.cineca.it -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Configure active IdentifierProvider types per Collection?
Yes, it is. We have the same requirements for ETD and I expect that similar requirements will arise for DataSet collection at some point. Our solution, actually part of our enterprise version and not released as open source, is much different than the new infrastructure to mint identifiers so I still need to figure if we can switch to the community solution and, maybe, improve it providing additional functionalities. Anyway, just few details to give you the idea: - the doi registration is an administrator functionality - we can configure multiple criteria (SOLR query) that are used to retrieve items that potentially need to register DOI - for any criteria we have a configurable class that guess the identifier, so to have more meaning identifier than a sequence number - the administrator has an UI console where can register the identifier, monitor the process (datacite e crossref both implements a two-phase registration), customize the suggested DOI - our functionality actually provide support for the datacite and crossref providers Best, Andrea Il 22/01/2014 16.49, Mark H. Wood ha scritto: I have a local requirement to mint and register DOIs for new submissions to our ETD collections, but nowhere else in the same instance. Is this something that would be generally useful? (I'm lazy and don't want to maintain a local modification :-) -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Andrea Bollini Dipartimento Servizi e Soluzioni per l'Amministrazione Universitaria Divisione Ricerca Via dei Tizii, 6 00185 Roma, Italy tel. +39 06 44 486 087 - mob. +39 348 82 77 525 http://www.cineca.it -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] A more efficient Git Workflow?
The real point here is not against what the PR is fired but from which branch contributors start to work. We cannot change a PR but we can open a PR from a third repository vs our repository but this doesn't matter as if the contributor start to work on the bug fix from the master we will get all the new features that are already in the master as part of the PR. But which is our real scenario? contributors that want to fix a bug on which version work? I guess that they work on the version in use at their institution not on the master. So we are actually asking them more work, they have the patch ready for the old release and we ask to work on the master. Of course they need to work on the master to contribute new features. Just want to note that the atlassian git stash product work in this direction too... https://confluence.atlassian.com/display/STASH/Automatic+branch+merging#Automaticbranchmerging-Branchorderingalgorithm Andrea Il 24/01/2014 10.28, helix84 ha scritto: Those are finally some good arguments :) I imagine merging from release to master brach only at the time of feature freeze is too late. I'd definitely favour continuous porting as soon as the fixes appear (before the branches diverge which means conflicts). But even though I like the idea of doing it with a commit hook, I'm afraid that won't be practical. For one, we will have to teach people to open bug fixes against the release branch. When they open it against master (which will happen), we'll have to open a new PR (including fetching the branch into your repo, which is manual work and has its own disadvantages) because 1) we have no way of changing the target branch of the existing PR and 2) merging it into master and then porting it to release would mean that the commit hook will try to put it into master the second time. That (patch already applied) probably would be a special case of a failed merge, which we would need to handle anyway within the hook. Regards, ~~helix84 -- Andrea Bollini Dipartimento Servizi e Soluzioni per l'Amministrazione Universitaria Divisione Ricerca Via dei Tizii, 6 00185 Roma, Italy tel. +39 06 44 486 087 - mob. +39 348 82 77 525 http://www.cineca.it -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Instead of bending metadata, add multiple-valued attributes to DSpaceObject?
feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Andrea Bollini Dipartimento Servizi e Soluzioni per l'Amministrazione Universitaria Divisione Ricerca Via dei Tizii, 6 00185 Roma, Italy tel. +39 06 44 486 087 - mob. +39 348 82 77 525 http://www.cineca.it -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] R: XMLUI auto-commit behavior versus JSPUI auto-abort behavior
Miss an explicit commit or rollback, where explicit can mean also annotation or aop based demarcation, is imho a bug. So, also without an exception the transaction should be aborted. Andrea Inviato da Samsung Mobile div Messaggio originale /divdivDa: Tim Donohue tdono...@duraspace.org /divdivData:23/07/2014 19:24 (GMT+01:00) /divdivA: dspace-devel dspace-devel@lists.sourceforge.net /divdivOggetto: [Dspace-devel] XMLUI auto-commit behavior versus JSPUI auto-abort behavior /divdiv /divHi Developers, After a bit of digging on a very odd bug (DS-2012), Pascal-Nicolas Becker, Peter Dietz and I discovered a strange behavior difference in how XMLUI and JSPUI deal with uncommitted database changes: https://jira.duraspace.org/browse/DS-2072 Simply, the JSPUI aborts any changes that you fail to explicitly commit. Whereas, XMLUI auto-commits them (as long as no Exceptions were thrown). See DS-2072 for much more detials. Obviously having opposite behaviors is not ideal (it makes UI-specific bugs even harder to figure out). Thoughts on which behavior seems more correct or ideal? - Tim -- Tim Donohue Technical Lead for DSpace DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] PLEASE VOTE on whether to include Services API refactoring in DSpace 6.0
Il 06/08/2015 16:47, Tim Donohue ha scritto: Hi Developers / Committers, As mentioned in yesterday's developers meeting, I'm calling a public VOTE around whether we include the Services API refactoring in the upcoming DSpace 6.0 release. As this change constitutes a major code refactor of the dspace-api (DSpace Java API), we'd appreciate feedback from anyone on this direction for 6.0. (If you have not yet read about the Services API refactoring, a brief summary and links to more information is provided at the end of this email) +1 It is an important step forward to the necessary modernization of the DSpace sourcecode. We at Cineca envision that this step will help DSpace to proceed faster. We think that it is better to make this change immediately in 6.0 to avoid a strong overlapping with the new single UI project. I can also anticipate that we will help as required to move the JSPUI module and the DSpace-CRIS extension to the new business layer. Best, Andrea -- Andrea Bollini International Business Development, Deputy Leader Open Source Open Standards Strategy, Head Cineca Via dei Tizii, 6 00185 Roma, Italy tel. +39 06 44 486 087 - mob. +39 348 82 77 525 http://www.cineca.it -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Updated: (DS-125) Date type can't be repeatable in the submission
[ http://jira.dspace.org/jira/browse/DS-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-125: -- Summary: Date type can't be repeatable in the submission (was: Date type can't be repeteable in the submission) Date type can't be repeatable in the submission --- Key: DS-125 URL: http://jira.dspace.org/jira/browse/DS-125 Project: DSpace 1.x Issue Type: Bug Components: JSPUI, XMLUI Affects Versions: 1.5.0, 1.5.1 Reporter: Andrea Bollini Priority: Trivial If you define a date metadata as repeatable it doesn't work properly in the submission both for JSPUI and XMLUI. In the JSPUI the value are not saved, in the XMLUI only a value are allowed, the add button replace the previous value. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Work started: (DS-66) bitstream format registry, setting bitstream internal - ID: 1896055
[ http://jira.dspace.org/jira/browse/DS-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on DS-66 started by Andrea Bollini. bitstream format registry, setting bitstream internal - ID: 1896055 --- Key: DS-66 URL: http://jira.dspace.org/jira/browse/DS-66 Project: DSpace 1.x Issue Type: Bug Components: XMLUI Affects Versions: 1.5.0, 1.5.1 Reporter: Andrea Bollini Assignee: Andrea Bollini Fix For: 1.5.2 Attachments: DS-66-xmlui-upload-file-internal-format.patch A bitstream with a format flagged as internal in the bitstream format registry should not be submittable. In the xmlui this setting has no effect. Followups: Date: 2009-03-04 17:31 Sender: cjuergen Just tried it with 1.5.x (today) and the effect remains. Bitstreams marked as internal are not (as supposed) submittable via jspui but are submittable via xmlui Date: 2009-03-04 17:10 Sender: bollini The bugs appers to be fixed in 1.5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Assigned: (DS-99) Non-admin user and admin menu options (1.5.1 XMUI only) - ID: 2353606
[ http://jira.dspace.org/jira/browse/DS-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reassigned DS-99: Assignee: Andrea Bollini Non-admin user and admin menu options (1.5.1 XMUI only) - ID: 2353606 - Key: DS-99 URL: http://jira.dspace.org/jira/browse/DS-99 Project: DSpace 1.x Issue Type: Bug Components: DSpace API, XMLUI Affects Versions: 1.5.1 Reporter: Stuart Lewis Assignee: Andrea Bollini Fix For: 1.5.2 Attachments: DS-99-context-menu.patch From: https://sourceforge.net/tracker/index.php?func=detailaid=2353606group_id=19984atid=119984 I had a problem with non admin users having access to admin and context menu options (when submitting a new item) in DSpace 1.5.1 XML. Although access to these page is prevented, we don't want our users seeing the options. I had a look around and noticed that org.dspace.browse.BrowseConsumer was being fired when a new item was created. In its constructor context.setIgnoreAuthorization(true) was being called but there was no corresponding context.setIgnoreAuthorization(false). In the meantime I have added a call to context.setIgnoreAuthorization(false) at the end the indexItem method. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Closed: (DS-109) Consistent treatment to users in special groups
[
http://jira.dspace.org/jira/browse/DS-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Bollini closed DS-109.
-
Resolution: Won't Fix
Fix Version/s: 1.5.2
Assignee: Andrea Bollini
The methods are consistent with them javadoc. They are not used in auth check,
they are only used as support for the edit group functionality
Consistent treatment to users in special groups
---
Key: DS-109
URL: http://jira.dspace.org/jira/browse/DS-109
Project: DSpace 1.x
Issue Type: Improvement
Components: DSpace API
Affects Versions: 1.5.0, 1.5.1, 1.5.2
Reporter: Bruc Liong
Assignee: Andrea Bollini
Fix For: 1.5.2
We populate users into their groups via the use of special groups on the
fly (as part of Shibboleth authN integration into DSpace) and had been
noticing that the mapped users cannot gain access to their resources despite
they have the aforementioned groups in the special group.
Temporary fix for this is to persist the group membership, e.g.
int[] groupIDs = AuthenticationManager.getSpecialGroups(context,request);
for(int i=0;igroupIDs.length;i++){
Group g = Group.find(context, groupIDs[i]);
//.
g.addMember(eperson);
g.update();
}
This is not ideal, it would be better if the special groups are
loaded/integrated into Group.isMember(eperson), or Group.isMember(groupid),
etc calls. These isMember seem to be only honouring explicit users assigned
in DB. Currently special groups only included in Group.allMemberGroupIDs and
isMember(context,groupid).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Assigned: (DS-122) Problems with repeatable metadata
[ http://jira.dspace.org/jira/browse/DS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reassigned DS-122: - Assignee: Andrea Bollini Problems with repeatable metadata - Key: DS-122 URL: http://jira.dspace.org/jira/browse/DS-122 Project: DSpace 1.x Issue Type: Bug Components: JSPUI Affects Versions: 1.5.2 Reporter: Nilde De Paoli Assignee: Andrea Bollini Priority: Blocker Fix For: 1.5.2 The system doesn't respect the filling order of the values of the repeatable metadata. Moreover the buttons 'add' and 'remove' for the multi-value metadata are not so clear. When you want to add a value, two new boxes are shown and the button 'remove' delete the value of the next box, not that of the box near to it. See bug http://jira.dspace.org/jira/browse/DS-37 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Resolved: (DS-67) Impossible retry/resume after upload a file with internal format
[ http://jira.dspace.org/jira/browse/DS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini resolved DS-67. -- Resolution: Fixed Impossible retry/resume after upload a file with internal format Key: DS-67 URL: http://jira.dspace.org/jira/browse/DS-67 Project: DSpace 1.x Issue Type: Bug Components: JSPUI Affects Versions: 1.5.1 Reporter: Andrea Bollini Assignee: Andrea Bollini Priority: Minor Fix For: 1.5.2 Attachments: DS-67-jspui-upload-file-internal-format.patch If you mark the pdf format as internal in the format registry, the jspui show you an error page when trying to upload a such file, but nor the retry button or go to my dspace and resume the submission enable you to upload a different file (an exception is thrown when you reach the upload step). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Closed: (DS-64) xmlui selection of authentication method - ID: 2086673
[ http://jira.dspace.org/jira/browse/DS-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini closed DS-64. Resolution: Fixed xmlui selection of authentication method - ID: 2086673 --- Key: DS-64 URL: http://jira.dspace.org/jira/browse/DS-64 Project: DSpace 1.x Issue Type: Bug Components: XMLUI Affects Versions: 1.5.1 Reporter: Andrea Bollini Assignee: Andrea Bollini Priority: Minor Fix For: 1.5.2 Attachments: xmlui-selector-auth-fix, xmlui-selector-auth-fix-v2.patch If you got 1 method in the authentication stack, the user is presented with an additional selection of authentication step even if he in reality got only one method available, e.g. using password and ip based authentication. Implicit methods shouldn't be counted at this point. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Assigned: (DS-126) Request to [dspace-base-url]/bitstream throw NPE
[ http://jira.dspace.org/jira/browse/DS-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reassigned DS-126: - Assignee: Andrea Bollini Request to [dspace-base-url]/bitstream throw NPE Key: DS-126 URL: http://jira.dspace.org/jira/browse/DS-126 Project: DSpace 1.x Issue Type: Bug Components: JSPUI Affects Versions: 1.5.0, 1.5.1 Reporter: Andrea Bollini Assignee: Andrea Bollini Priority: Minor Fix For: 1.5.2 Attachments: bitstream-url.patch In JSPUI request to the [dspace-base-url]/bitstream throw NPE instead of a page not found as done by the XMLUI -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Resolved: (DS-66) bitstream format registry, setting bitstream internal - ID: 1896055
[ http://jira.dspace.org/jira/browse/DS-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini resolved DS-66. -- Resolution: Fixed bitstream format registry, setting bitstream internal - ID: 1896055 --- Key: DS-66 URL: http://jira.dspace.org/jira/browse/DS-66 Project: DSpace 1.x Issue Type: Bug Components: XMLUI Affects Versions: 1.5.0, 1.5.1 Reporter: Andrea Bollini Assignee: Andrea Bollini Fix For: 1.5.2 Attachments: DS-66-xmlui-upload-file-internal-format.patch A bitstream with a format flagged as internal in the bitstream format registry should not be submittable. In the xmlui this setting has no effect. Followups: Date: 2009-03-04 17:31 Sender: cjuergen Just tried it with 1.5.x (today) and the effect remains. Bitstreams marked as internal are not (as supposed) submittable via jspui but are submittable via xmlui Date: 2009-03-04 17:10 Sender: bollini The bugs appers to be fixed in 1.5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Updated: (DS-115) metadata not showed in verify step
[ http://jira.dspace.org/jira/browse/DS-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-115: -- Attachment: DS-115-verify-jsp-fix.patch metadata not showed in verify step -- Key: DS-115 URL: http://jira.dspace.org/jira/browse/DS-115 Project: DSpace 1.x Issue Type: Bug Components: JSPUI Affects Versions: 1.5.2 Reporter: Nilde De Paoli Priority: Minor Fix For: 1.5.2 Attachments: DS-115-verify-jsp-fix.patch During submission process, the metadata 'type' and 'language' are not viewed, even if they have been filled in. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Commented: (DS-120) Cocoon 2.2 hijacks the dspace.log file
[ http://jira.dspace.org/jira/browse/DS-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=10202#action_10202 ] Andrea Bollini commented on DS-120: --- It works fro me, I have been applied to the testhaton instance: http://dspace-testhaton.cilea.it/xmlui We need to add a note in the upgrade instructions PS: Tim this also fix the DS-85 issue, right? Cocoon 2.2 hijacks the dspace.log file Key: DS-120 URL: http://jira.dspace.org/jira/browse/DS-120 Project: DSpace 1.x Issue Type: Bug Components: XMLUI Affects Versions: 1.5.2 Reporter: Tim Donohue Assignee: Mark Diggory Priority: Blocker Fix For: 1.5.2 Attachments: log4j.properties.patch It seems the upgrade to Cocoon 2.2 now causes Cocoon to hijack the dspace.log file. Normal DSpace logging no longer appears in the dspace.log when using the XMLUI. Instead the dspace.log just includes logging from Cocoon 2.2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-2) Not found page returns 200 OK instead of 404 Not Found - ID: 2002866
[ http://jira.dspace.org/jira/browse/DS-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-2: - Assignee: Mark Wood (was: Bradley McLean) Added info about SVN commit: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3387 Not found page returns 200 OK instead of 404 Not Found - ID: 2002866 -- Key: DS-2 URL: http://jira.dspace.org/jira/browse/DS-2 Project: DSpace 1.x Issue Type: Bug Components: XMLUI Affects Versions: 1.5.0 Reporter: Charles Kiplagat Assignee: Mark Wood The Manakin not found page does not set the HTTP Response header to 404. e.g. as at 2008-06-26 the following URLs all returned 200 OK: http://researcharchive.vuw.ac.nz/blah http://repositories.tamu.edu/blah https://oa.doria.fi/blah This is a problem for automated system monitoring, log analysis, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-150) Usage event (statistics) plugin hook for 1.5 - ID: 2025998
[ http://jira.dspace.org/jira/browse/DS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-150: --- Added info about SVN commit: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3402 Usage event (statistics) plugin hook for 1.5 - ID: 2025998 -- Key: DS-150 URL: http://jira.dspace.org/jira/browse/DS-150 Project: DSpace 1.x Issue Type: Improvement Reporter: Charles Kiplagat Assignee: Mark Wood Fix For: 1.5.2 Attachments: suei-1.5.patch Enable a pluggable usage event monitor class for e.g. collecting statistical data on community, collection, item, and bitstream views. The intent is to factor event capture out of some of the various statistical projects and just let them plug into a common event stream. This patch replaces parts of patches 1927351 and 1927360. Designed to be simple, lightweight, and general. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Closed: (DS-150) Usage event (statistics) plugin hook for 1.5 - ID: 2025998
[ http://jira.dspace.org/jira/browse/DS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini closed DS-150. - Resolution: Fixed Fix Version/s: 1.5.2 Usage event (statistics) plugin hook for 1.5 - ID: 2025998 -- Key: DS-150 URL: http://jira.dspace.org/jira/browse/DS-150 Project: DSpace 1.x Issue Type: Improvement Reporter: Charles Kiplagat Assignee: Mark Wood Fix For: 1.5.2 Attachments: suei-1.5.patch Enable a pluggable usage event monitor class for e.g. collecting statistical data on community, collection, item, and bitstream views. The intent is to factor event capture out of some of the various statistical projects and just let them plug into a common event stream. This patch replaces parts of patches 1927351 and 1927360. Designed to be simple, lightweight, and general. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Closed: (DS-143) 'ant init_configs' copies wrong dspace.cfg - ID: 2620307
[
http://jira.dspace.org/jira/browse/DS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Bollini closed DS-143.
-
Resolution: Fixed
Fix Version/s: 1.5.2
'ant init_configs' copies wrong dspace.cfg - ID: 2620307
Key: DS-143
URL: http://jira.dspace.org/jira/browse/DS-143
Project: DSpace 1.x
Issue Type: Bug
Reporter: Charles Kiplagat
Assignee: Mark Wood
Fix For: 1.5.2
Attachments: build.patch
build.xml will use a supplied dspace.cfg path for its own operations, but
always copies
[DSpace-source]dspace/target/dspace-whatever/config/dspace.cfg into the
[DSpace]/config directory. When the two paths are not equal, the result is
surprising.
The problem is that init_configs first copies all of the source config
directory contents (including dspace.cfg from that location) to the target,
then copies ${config} to the target/dspace.cfg. The second copy is
skipped, because the first copy has placed a file in the target of equal
name and current date, which probably makes it newer than the specified
config. The cure is to omit copying the source dspace.cfg in the first
copy operation.
Note that, if there is *already* a newer dspace.cfg in the target location
when init_configs is run, the specified config is still not copied.
Attached patch is against 1_5_x -r3488
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Closed: (DS-4) Refactor LDAPServlet to use Stackable Authentication - ID: 2057231
[ http://jira.dspace.org/jira/browse/DS-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini closed DS-4. --- Resolution: Fixed Fix Version/s: 1.5.2 Refactor LDAPServlet to use Stackable Authentication - ID: 2057231 -- Key: DS-4 URL: http://jira.dspace.org/jira/browse/DS-4 Project: DSpace 1.x Issue Type: Improvement Reporter: Charles Kiplagat Assignee: Stuart Lewis Fix For: 1.5.2 At present LDAPServlet performs LDAP authentication within itself, rather than delegating it to the stackable authentication. This patch fixes that by stripping out all of the LDAP code, and replacing it with: int status = AuthenticationManager.authenticate(context, netid, password, null, request); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-4) Refactor LDAPServlet to use Stackable Authentication - ID: 2057231
[ http://jira.dspace.org/jira/browse/DS-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-4: - Added info about SVN commit: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3131 Refactor LDAPServlet to use Stackable Authentication - ID: 2057231 -- Key: DS-4 URL: http://jira.dspace.org/jira/browse/DS-4 Project: DSpace 1.x Issue Type: Improvement Reporter: Charles Kiplagat Assignee: Stuart Lewis Fix For: 1.5.2 At present LDAPServlet performs LDAP authentication within itself, rather than delegating it to the stackable authentication. This patch fixes that by stripping out all of the LDAP code, and replacing it with: int status = AuthenticationManager.authenticate(context, netid, password, null, request); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Commented: (DS-5) DSpace1.5.1(XML) problem with Login to restricted bitstreams - ID: 2164955
[ http://jira.dspace.org/jira/browse/DS-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=10211#action_10211 ] Andrea Bollini commented on DS-5: - SVN commit: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3316 DSpace1.5.1(XML) problem with Login to restricted bitstreams - ID: 2164955 -- Key: DS-5 URL: http://jira.dspace.org/jira/browse/DS-5 Project: DSpace 1.x Issue Type: Bug Components: XMLUI Affects Versions: 1.5.1 Environment: software Reporter: Charles Kiplagat Assignee: Stuart Lewis Fix For: 1.5.2 Software 1. JSP 1.5.1 is fine, no issue. 2. XML 1.5 is fine. It can redirect to This bitstream is restricted after login. 3. Have a very lightly customised XML 1.5.1, in style sheet only, but asked another colleague with an out of the box XML 1.5.1 version and similar behaviour is exhibited. Problem: We have bitstreams that are restricted to administrator or collection admins, if a user who does not have authorisation to that bitstream logs into the restricted item they continue to receive the login screen instead of getting a not authorised message or they loop around endlessly and hang the browser session. To Test this 1. You can create a new record or use an existing one 2. Make sure that the item has read access to metadata record and change the authorisation to either admin or a collection admin group. (we have tried both) 3. Logout of your account and clear the cache 4. Login with another account that has no access and you will continue to loop around in the login cycle after the second time you get an error message, odd browser behaviour or page not found. Here is the error message from log when the 2nd user without access logs in. 2008-10-09 17:31:34,258 INFO org.dspace.app.xmlui.utils.AuthenticationUtil @ leonie.ha...@gmail.com:session_id=222BFE9CA6411C87F2D 195BBBC7B1FFB:ip_addr=130.216.69.238:failed_login:email=, realm=null, result=4 2008-10-09 17:31:34,468 INFO org.dspace.authenticate.PasswordAuthentication @ leonie.ha...@gmail.com:session_id=222BFE9CA6411C87F2 D195BBBC7B1FFB:ip_addr=130.216.69.238:authenticate:attempting password auth of user= 2008-10-09 17:31:34,470 INFO org.dspace.app.xmlui.utils.AuthenticationUtil @ leonie.ha...@gmail.com:session_id=222BFE9CA6411C87F2D 195BBBC7B1FFB:ip_addr=130.216.69.238:failed_login:email=, realm=null, result=4 2008-10-09 17:31:34,590 INFO org.dspace.authenticate.PasswordAuthentication @ leonie.ha...@gmail.com:session_id=222BFE9CA6411C87F2 D195BBBC7B1FFB:ip_addr=130.216.69.238:authenticate:attempting password auth of user= 2008-10-09 17:31:34,592 INFO org.dspace.app.xmlui.utils.AuthenticationUtil @ leonie.ha...@gmail.com:session_id=222BFE9CA6411C87F2D 195BBBC7B1FFB:ip_addr=130.216.69.238:failed_login:email=, realm=null, result=4 2008-10-09 17:31:34,733 INFO org.dspace.authenticate.PasswordAuthentication @ leonie.ha...@gmail.com:session_id=222BFE9CA6411C87F2 D195BBBC7B1FFB:ip_addr=130.216.69.238:authenticate:attempting password auth of user= Leonie Hayes Research Repository Librarian http://www.library.auckland.ac.nz/contacts/?firstname=lastname=hayes http://researchspace.auckland.ac.nz -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Closed: (DS-6) XHTML Head Dissimination Crosswalk exposes provenance info - ID: 2343281
[ http://jira.dspace.org/jira/browse/DS-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini closed DS-6. --- Resolution: Fixed Fix Version/s: 1.5.2 XHTML Head Dissimination Crosswalk exposes provenance info - ID: 2343281 Key: DS-6 URL: http://jira.dspace.org/jira/browse/DS-6 Project: DSpace 1.x Issue Type: Bug Affects Versions: 1.5.0 Reporter: Charles Kiplagat Assignee: Stuart Lewis Fix For: 1.5.2 The xhtmlheaddisseminationcrosswalk exposes dc.description.provenance as dc.description in the head. The provenance information was available to admins or folk with item edit rights until know. IMO the behaviour should be consistent. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Commented: (DS-9) Restricted Items metadata exposed via OAI - ID: 1730606
[ http://jira.dspace.org/jira/browse/DS-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=10215#action_10215 ] Andrea Bollini commented on DS-9: - SVN commit: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3346 Restricted Items metadata exposed via OAI - ID: 1730606 --- Key: DS-9 URL: http://jira.dspace.org/jira/browse/DS-9 Project: DSpace 1.x Issue Type: Bug Affects Versions: 1.5.0 Reporter: Charles Kiplagat Assignee: Stuart Lewis Fix For: 1.5.2 Every item (including those with DEFAULT_ITEM_READ not set to anonymous) is exposed via OAI. Only items with DEFAULT_ITEM_READ == anonymous should be exposed via OAI. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-10) Implicit group for all registered users - ID: 1587270
[ http://jira.dspace.org/jira/browse/DS-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-10: -- Added SVN commit info: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3347 Implicit group for all registered users - ID: 1587270 - Key: DS-10 URL: http://jira.dspace.org/jira/browse/DS-10 Project: DSpace 1.x Issue Type: Bug Environment: authorization Reporter: Charles Kiplagat Assignee: Stuart Lewis Fix For: 1.5.2 It would be nice to have an implicit group that automatically included all registered users for situations where you want to grant a privilege to all registered users. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Closed: (DS-10) Implicit group for all registered users - ID: 1587270
[ http://jira.dspace.org/jira/browse/DS-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini closed DS-10. Resolution: Fixed Fix Version/s: 1.5.2 Implicit group for all registered users - ID: 1587270 - Key: DS-10 URL: http://jira.dspace.org/jira/browse/DS-10 Project: DSpace 1.x Issue Type: Bug Environment: authorization Reporter: Charles Kiplagat Assignee: Stuart Lewis Fix For: 1.5.2 It would be nice to have an implicit group that automatically included all registered users for situations where you want to grant a privilege to all registered users. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Commented: (DS-12) Exception handling for deleting a metadata field - ID: 1606439
[ http://jira.dspace.org/jira/browse/DS-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=10218#action_10218 ] Andrea Bollini commented on DS-12: -- SVN commit: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3373 Exception handling for deleting a metadata field - ID: 1606439 -- Key: DS-12 URL: http://jira.dspace.org/jira/browse/DS-12 Project: DSpace 1.x Issue Type: Bug Components: DSpace API Reporter: Charles Kiplagat Assignee: Stuart Lewis Fix For: 1.5.2 Trying to delete a metadatafield with associated values leads to an java.sql.SQLException: ERROR: update or delete on metadatafieldregistry violates foreign key constraint metadatavalue_metadata_field_id_fkey on metadatavalue error. This is indicated in the delete confirm page, but the error should be caught properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Closed: (DS-11) 'My Account' disappears following exports - ID: 2495728
[ http://jira.dspace.org/jira/browse/DS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini closed DS-11. Resolution: Fixed Fix Version/s: 1.5.2 Assignee: Stuart Lewis 'My Account' disappears following exports - ID: 2495728 --- Key: DS-11 URL: http://jira.dspace.org/jira/browse/DS-11 Project: DSpace 1.x Issue Type: Improvement Components: XMLUI Reporter: Charles Kiplagat Assignee: Stuart Lewis Fix For: 1.5.2 in the XMLUI the 'h3My Account/h3' heading disappears when using the default theme if the user has exports waiting to be downloaded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Assigned: (DS-153) Submission Forms don't preserve order of values - ID: 2541285
[ http://jira.dspace.org/jira/browse/DS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reassigned DS-153: - Assignee: Andrea Bollini (was: Tim Donohue) Submission Forms don't preserve order of values - ID: 2541285 - Key: DS-153 URL: http://jira.dspace.org/jira/browse/DS-153 Project: DSpace 1.x Issue Type: Bug Components: JSPUI Affects Versions: 1.5.1 Reporter: Charles Kiplagat Assignee: Andrea Bollini Attachments: org_dspace_submit_step_DescribeStep (1).patch This bug occurs in 1.5.x XMLUI and JSPUI. Essentially the Describe (metadata entry) page of the submission process doesn't preserve the order that values are entered in multi-valued fields. This is especially problematic for Author names. During a submission author names are reordered such that the *first* author listed is that *last* one that you enter during the submission process. This patch modifies the org.dspace.submit.step.DescribeStep class (the processing class) in the dspace-api module, so that it will preserve the order in which values are entered. This way the *first* author listed will always be the *first* author entered, etc. This patch works for both the XMLUI and JSPUI since both of these interfaces utilize this same backend prorcessing class to save all values entered during the Describe step. This patch was built off the latest code in the dspace-1_5_x branch of SVN (as of 2009-Jan-27). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Closed: (DS-18) DSpace 1.5.1(XMLUI) Wrong dir usage of StatisticsLoader - ID: 2137425
[
http://jira.dspace.org/jira/browse/DS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Bollini closed DS-18.
Resolution: Fixed
DSpace 1.5.1(XMLUI) Wrong dir usage of StatisticsLoader - ID: 2137425
-
Key: DS-18
URL: http://jira.dspace.org/jira/browse/DS-18
Project: DSpace 1.x
Issue Type: Bug
Components: XMLUI
Reporter: Charles Kiplagat
Assignee: Stuart Lewis
Fix For: 1.5.2
Statistics viewer for XMLUI, based on existing DStat view from the analysis
files (.dat)
Existing CreateStatReport ouput the (.dat) files under (log.dir) but
StatisticsLoader use (report.dir)
Line number 355
===
StatisticsLoader.java
private static File[] getAnalysisAndReportFileList()
{
File reportDir = new
File(ConfigurationManager.getProperty(report.dir));
Line number 131
===
CreateStatReport.java
outputLogDirectory = ConfigurationManager.getProperty(log.dir) +
File.separator;
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Updated: (DS-18) DSpace 1.5.1(XMLUI) Wrong dir usage of StatisticsLoader - ID: 2137425
[
http://jira.dspace.org/jira/browse/DS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Bollini updated DS-18:
-
Component/s: XMLUI
DSpace 1.5.1(XMLUI) Wrong dir usage of StatisticsLoader - ID: 2137425
-
Key: DS-18
URL: http://jira.dspace.org/jira/browse/DS-18
Project: DSpace 1.x
Issue Type: Bug
Components: XMLUI
Reporter: Charles Kiplagat
Assignee: Stuart Lewis
Fix For: 1.5.2
Statistics viewer for XMLUI, based on existing DStat view from the analysis
files (.dat)
Existing CreateStatReport ouput the (.dat) files under (log.dir) but
StatisticsLoader use (report.dir)
Line number 355
===
StatisticsLoader.java
private static File[] getAnalysisAndReportFileList()
{
File reportDir = new
File(ConfigurationManager.getProperty(report.dir));
Line number 131
===
CreateStatReport.java
outputLogDirectory = ConfigurationManager.getProperty(log.dir) +
File.separator;
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-18) DSpace 1.5.1(XMLUI) Wrong dir usage of StatisticsLoader - ID: 2137425
[
http://jira.dspace.org/jira/browse/DS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Bollini reopened DS-18:
--
Added SVN commit info:
http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3321
DSpace 1.5.1(XMLUI) Wrong dir usage of StatisticsLoader - ID: 2137425
-
Key: DS-18
URL: http://jira.dspace.org/jira/browse/DS-18
Project: DSpace 1.x
Issue Type: Bug
Components: XMLUI
Reporter: Charles Kiplagat
Assignee: Stuart Lewis
Fix For: 1.5.2
Statistics viewer for XMLUI, based on existing DStat view from the analysis
files (.dat)
Existing CreateStatReport ouput the (.dat) files under (log.dir) but
StatisticsLoader use (report.dir)
Line number 355
===
StatisticsLoader.java
private static File[] getAnalysisAndReportFileList()
{
File reportDir = new
File(ConfigurationManager.getProperty(report.dir));
Line number 131
===
CreateStatReport.java
outputLogDirectory = ConfigurationManager.getProperty(log.dir) +
File.separator;
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Closed: (DS-153) Submission Forms don't preserve order of values - ID: 2541285
[ http://jira.dspace.org/jira/browse/DS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini closed DS-153. - Resolution: Fixed Fix Version/s: 1.5.2 Submission Forms don't preserve order of values - ID: 2541285 - Key: DS-153 URL: http://jira.dspace.org/jira/browse/DS-153 Project: DSpace 1.x Issue Type: Bug Components: JSPUI Affects Versions: 1.5.1 Reporter: Charles Kiplagat Assignee: Tim Donohue Fix For: 1.5.2 Attachments: org_dspace_submit_step_DescribeStep (1).patch This bug occurs in 1.5.x XMLUI and JSPUI. Essentially the Describe (metadata entry) page of the submission process doesn't preserve the order that values are entered in multi-valued fields. This is especially problematic for Author names. During a submission author names are reordered such that the *first* author listed is that *last* one that you enter during the submission process. This patch modifies the org.dspace.submit.step.DescribeStep class (the processing class) in the dspace-api module, so that it will preserve the order in which values are entered. This way the *first* author listed will always be the *first* author entered, etc. This patch works for both the XMLUI and JSPUI since both of these interfaces utilize this same backend prorcessing class to save all values entered during the Describe step. This patch was built off the latest code in the dspace-1_5_x branch of SVN (as of 2009-Jan-27). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-153) Submission Forms don't preserve order of values - ID: 2541285
[ http://jira.dspace.org/jira/browse/DS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-153: --- Assignee: Tim Donohue (was: Andrea Bollini) Added SVN commit info: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3394 Submission Forms don't preserve order of values - ID: 2541285 - Key: DS-153 URL: http://jira.dspace.org/jira/browse/DS-153 Project: DSpace 1.x Issue Type: Bug Components: JSPUI Affects Versions: 1.5.1 Reporter: Charles Kiplagat Assignee: Tim Donohue Attachments: org_dspace_submit_step_DescribeStep (1).patch This bug occurs in 1.5.x XMLUI and JSPUI. Essentially the Describe (metadata entry) page of the submission process doesn't preserve the order that values are entered in multi-valued fields. This is especially problematic for Author names. During a submission author names are reordered such that the *first* author listed is that *last* one that you enter during the submission process. This patch modifies the org.dspace.submit.step.DescribeStep class (the processing class) in the dspace-api module, so that it will preserve the order in which values are entered. This way the *first* author listed will always be the *first* author entered, etc. This patch works for both the XMLUI and JSPUI since both of these interfaces utilize this same backend prorcessing class to save all values entered during the Describe step. This patch was built off the latest code in the dspace-1_5_x branch of SVN (as of 2009-Jan-27). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-152) Submission verify page handles dc.identifier.* incorrectly - ID: 2155479
[ http://jira.dspace.org/jira/browse/DS-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-152: --- Assignee: Tim Donohue Added SVN commit info: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3396 Submission verify page handles dc.identifier.* incorrectly - ID: 2155479 Key: DS-152 URL: http://jira.dspace.org/jira/browse/DS-152 Project: DSpace 1.x Issue Type: Bug Affects Versions: 1.5.1 Reporter: Charles Kiplagat Assignee: Tim Donohue Attachments: Fix_for_SF_bug_[2155479]_Submission_verify_page_handles_dc_identifier___incorrectly.patch, moz-screenshot-4.jpg On the submission verify page in XMLUI, the Identifiers line lists all identifiers, including dc.identifier.citation (which has a line to itself, above). I'm not completely sure what the 'null' at the beginning is, but it may be a placeholder for dc.identifier.uri, which also shouldn't be there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-151) XMLUI Submission forms display errors during add/remove - ID: 2543413
[ http://jira.dspace.org/jira/browse/DS-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-151: --- Added SVN commit info: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3398 XMLUI Submission forms display errors during add/remove - ID: 2543413 - Key: DS-151 URL: http://jira.dspace.org/jira/browse/DS-151 Project: DSpace 1.x Issue Type: Bug Reporter: Charles Kiplagat Assignee: Tim Donohue Attachments: dri2xhtml_structural_xsl.patch, org_dspace_submit_step_DescribeStep.patch This is not a major bug, but an annoying usability problem. When you are adding/removing values (via Add and Remove buttons) in multi-valued fields during the XMLUI submission process, you receive errors/warnings on empty required fields which you may not have even gotten to yet. During local usability testing, many users found it disconcerting that the interface displays validation errors next to fields before they even submit the entire form. I've found a fix to this issue which also works with the existing JSPUI. The patches are attached. Essentially, we add logic to only perform form validation when the Next button (or Progress Bar) is pressed. This ensures that users can click Add, Remove on fields (or step Back in the process) without receiving validation error messages. The attached patches are for the org.dspace.submit.step.DescribeStep class (which performs backend processing of both XMLUI and JSPUI), and the DRI2XHTML structural.xsl which builds the default XMLUI theme. Changes to the DescribeStep class were tested with both the XMLUI and JSPUI (despite the fact that this usability problem only exists on XMLUI). The patches were built based on the latest code in dspace-1_5_x branch (as of 2009-01-28). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Updated: (DS-152) Submission verify page handles dc.identifier.* incorrectly - ID: 2155479
[ http://jira.dspace.org/jira/browse/DS-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-152: -- Component/s: XMLUI Fix Version/s: 1.5.2 Submission verify page handles dc.identifier.* incorrectly - ID: 2155479 Key: DS-152 URL: http://jira.dspace.org/jira/browse/DS-152 Project: DSpace 1.x Issue Type: Bug Components: XMLUI Affects Versions: 1.5.1 Reporter: Charles Kiplagat Assignee: Tim Donohue Fix For: 1.5.2 Attachments: Fix_for_SF_bug_[2155479]_Submission_verify_page_handles_dc_identifier___incorrectly.patch, moz-screenshot-4.jpg On the submission verify page in XMLUI, the Identifiers line lists all identifiers, including dc.identifier.citation (which has a line to itself, above). I'm not completely sure what the 'null' at the beginning is, but it may be a placeholder for dc.identifier.uri, which also shouldn't be there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Closed: (DS-151) XMLUI Submission forms display errors during add/remove - ID: 2543413
[ http://jira.dspace.org/jira/browse/DS-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini closed DS-151. - Resolution: Fixed XMLUI Submission forms display errors during add/remove - ID: 2543413 - Key: DS-151 URL: http://jira.dspace.org/jira/browse/DS-151 Project: DSpace 1.x Issue Type: Bug Components: XMLUI Reporter: Charles Kiplagat Assignee: Tim Donohue Fix For: 1.5.2 Attachments: dri2xhtml_structural_xsl.patch, org_dspace_submit_step_DescribeStep.patch This is not a major bug, but an annoying usability problem. When you are adding/removing values (via Add and Remove buttons) in multi-valued fields during the XMLUI submission process, you receive errors/warnings on empty required fields which you may not have even gotten to yet. During local usability testing, many users found it disconcerting that the interface displays validation errors next to fields before they even submit the entire form. I've found a fix to this issue which also works with the existing JSPUI. The patches are attached. Essentially, we add logic to only perform form validation when the Next button (or Progress Bar) is pressed. This ensures that users can click Add, Remove on fields (or step Back in the process) without receiving validation error messages. The attached patches are for the org.dspace.submit.step.DescribeStep class (which performs backend processing of both XMLUI and JSPUI), and the DRI2XHTML structural.xsl which builds the default XMLUI theme. Changes to the DescribeStep class were tested with both the XMLUI and JSPUI (despite the fact that this usability problem only exists on XMLUI). The patches were built based on the latest code in dspace-1_5_x branch (as of 2009-01-28). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-149) Search with % causes NullPointer in XMLUI - ID: 2557654
[ http://jira.dspace.org/jira/browse/DS-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-149: --- Added SVN commit info: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3420 Search with % causes NullPointer in XMLUI - ID: 2557654 - Key: DS-149 URL: http://jira.dspace.org/jira/browse/DS-149 Project: DSpace 1.x Issue Type: Bug Components: XMLUI Reporter: Charles Kiplagat Assignee: Tim Donohue Attachments: AbstractDSpaceTransformer.patch In DSpace 1.5.x XMLUI, if your search includes the percent (%) character you receive a NullPointerException. I've attached a patch which first escapes the % character (i.e. replaces with %25), before decoding the string in AbstractDSpaceTransformer.URLDecode(). All other symbols seem to work fine (at least they don't throw errors). This seems to be the most appropriate fix, to ensure we aren't throwing a NullPointerException when this character is entered. Patch was created for latest code in 1.5.x branch (as of 2009-Feb-2). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-144) Patch for Feature Request 2609564 group delete confirm - ID: 2612341
[ http://jira.dspace.org/jira/browse/DS-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-144: --- Added SVN commit info: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3488 Patch for Feature Request 2609564 group delete confirm - ID: 2612341 Key: DS-144 URL: http://jira.dspace.org/jira/browse/DS-144 Project: DSpace 1.x Issue Type: Improvement Reporter: Charles Kiplagat Assignee: Claudia Jürgen Attachments: ConfirmGroupDeletionStep This patch adds a confirmation step to group deletion in the jspui. At the moment there is none, so one might easily by misclicking delete a group and thus it's associated resource policies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-138) Authors re-ordered when item edited - ID: 2655052
[ http://jira.dspace.org/jira/browse/DS-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-138: --- Added SVN commit info: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3520 Authors re-ordered when item edited - ID: 2655052 -- Key: DS-138 URL: http://jira.dspace.org/jira/browse/DS-138 Project: DSpace 1.x Issue Type: Bug Components: XMLUI Affects Versions: 1.5.1 Reporter: Charles Kiplagat Assignee: Stuart Lewis Fix submitted by Paulo Jobim. Patch attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Closed: (DS-138) Authors re-ordered when item edited - ID: 2655052
[ http://jira.dspace.org/jira/browse/DS-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini closed DS-138. - Resolution: Fixed Fix Version/s: 1.5.2 Authors re-ordered when item edited - ID: 2655052 -- Key: DS-138 URL: http://jira.dspace.org/jira/browse/DS-138 Project: DSpace 1.x Issue Type: Bug Components: XMLUI Affects Versions: 1.5.1 Reporter: Charles Kiplagat Assignee: Stuart Lewis Fix For: 1.5.2 Fix submitted by Paulo Jobim. Patch attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Updated: (DS-21) Fix for hardcoded metadata language qualifiers - ID: 2433387
[ http://jira.dspace.org/jira/browse/DS-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini updated DS-21: - Component/s: DSpace API Affects Version/s: 1.5.0 1.5.1 Fix Version/s: 1.5.2 Fix for hardcoded metadata language qualifiers - ID: 2433387 Key: DS-21 URL: http://jira.dspace.org/jira/browse/DS-21 Project: DSpace 1.x Issue Type: Improvement Components: DSpace API Affects Versions: 1.5.0, 1.5.1 Reporter: Charles Kiplagat Assignee: Claudia Jürgen Fix For: 1.5.2 With CSS the old bug of having the metadata language qualifier hardcoded instead of using the configuration parameter default.language has been reintroduced. It has been fixed in 1_5_x. This is just to make the patch available for those using 1.5.1 in an non en environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-21) Fix for hardcoded metadata language qualifiers - ID: 2433387
[ http://jira.dspace.org/jira/browse/DS-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-21: -- Assignee: Claudia Jürgen Added SVN commit info: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision= Fix for hardcoded metadata language qualifiers - ID: 2433387 Key: DS-21 URL: http://jira.dspace.org/jira/browse/DS-21 Project: DSpace 1.x Issue Type: Improvement Components: DSpace API Affects Versions: 1.5.0, 1.5.1 Reporter: Charles Kiplagat Assignee: Claudia Jürgen Fix For: 1.5.2 With CSS the old bug of having the metadata language qualifier hardcoded instead of using the configuration parameter default.language has been reintroduced. It has been fixed in 1_5_x. This is just to make the patch available for those using 1.5.1 in an non en environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Commented: (DS-22) News stored not language dependend - ID: 2125833
[ http://jira.dspace.org/jira/browse/DS-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=10234#action_10234 ] Andrea Bollini commented on DS-22: -- SVN commit: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3337 News stored not language dependend - ID: 2125833 Key: DS-22 URL: http://jira.dspace.org/jira/browse/DS-22 Project: DSpace 1.x Issue Type: Bug Affects Versions: 1.5.0 Reporter: Charles Kiplagat Fix For: 1.5.2 I just found a surprising bug while configuring the two News of the main page. We have a DSpace 1.5 (jspui) installation with English and German GUI. There are two possibilities to configure the News: 1. the news-side*.html and news-top*.html in the config directory, and 2. the administration area of the GUI. Now my case: I edited the German text from the GUI. Then I switched to the English GUI to set up the translation. The fields were already filled with the German texts (!). And after changing them, the German texts in the German GUI are gone. Looking in the config directory I saw that only the files news-side.html and news-top.html were affected and news-side_de.html and news-top_de.html were still old (= the original versions from the language pack). This means: Even when I edit the News from the German GUI, the English files are written (and displayed)! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-23) DSQuery invalid check for empty query string - ID: 2343849
[
http://jira.dspace.org/jira/browse/DS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Bollini reopened DS-23:
--
Added SVN commit info:
http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3336
DSQuery invalid check for empty query string - ID: 2343849
--
Key: DS-23
URL: http://jira.dspace.org/jira/browse/DS-23
Project: DSpace 1.x
Issue Type: Bug
Reporter: Charles Kiplagat
Fix For: 1.5.2
in org.dspace.search.DSQuery
the check for empty query Strings
static String checkEmptyQuery(String myquery)
{
if (myquery.equals())
{
myquery = empty_query_string;
}
return myquery;
}
does not catch empty query strings as these are ().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-19) Feature Request #1896717 Registration notification missin - ID: 2041754
[ http://jira.dspace.org/jira/browse/DS-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-19: -- Added SVN commit info: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3322 Feature Request #1896717 Registration notification missin - ID: 2041754 --- Key: DS-19 URL: http://jira.dspace.org/jira/browse/DS-19 Project: DSpace 1.x Issue Type: Improvement Reporter: Charles Kiplagat Assignee: Stuart Lewis This patch adds the DSpace name and url as defined in dspace.cfg dspace.name dspace.url to the registration notification email. Might be useful for people running multiple instances. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Assigned: (DS-25) SWORD Service Document fails if Collection is untitled - ID: 1968082
[ http://jira.dspace.org/jira/browse/DS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reassigned DS-25: Assignee: Stuart Lewis SWORD Service Document fails if Collection is untitled - ID: 1968082 Key: DS-25 URL: http://jira.dspace.org/jira/browse/DS-25 Project: DSpace 1.x Issue Type: Bug Reporter: Charles Kiplagat Assignee: Stuart Lewis Fix For: 1.5.2 If somehow you ended up with a Collection with no title in DSpace 1.5, SWORD will fail to generate a Service Document for anyone with submit access to that untitled Collection. Obviously, most DSpace Collections *should* have a title. However, it is possible to generate a Collection without a title. Either way, the DSpace SWORD Server should probably be smart enough to still generate a valid Service Document if it encounters a Collection without a title. The following error is generated when a collection without a title is encountered: SEVERE: Servlet.service() for servlet servicedocument threw exception java.lang.NullPointerException at org.purl.sword.base.Collection.marshall(Collection.java:367) at org.purl.sword.base.Workspace.marshall(Workspace.java:176) at org.purl.sword.base.Service.marshall(Service.java:299) at org.purl.sword.base.ServiceDocument.marshall(ServiceDocument.java:260) at org.purl.sword.server.ServiceDocumentServlet.doGet(ServiceDocumentServlet.j ava:86) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicatio nFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterC hain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.j ava:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.j ava:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:12 8) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:10 4) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.jav a:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697 ) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.jav a:889) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.ja va:686) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-26) Hardcoded Strings in DSQuery - ID: 2493794
[ http://jira.dspace.org/jira/browse/DS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-26: -- Assignee: Claudia Jürgen Added SVN commit info: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3363 Hardcoded Strings in DSQuery - ID: 2493794 -- Key: DS-26 URL: http://jira.dspace.org/jira/browse/DS-26 Project: DSpace 1.x Issue Type: Bug Components: DSpace API Affects Versions: 1.5.1 Reporter: Charles Kiplagat Assignee: Claudia Jürgen Fix For: 1.5.2 org.dspace.search.DSQuery doQuery(Context c, QueryArgs args) contains hardcoded Strings: ... qr.setErrorMsg(Number format exception); } ... qr.setErrorMsg(Invalid search string); ... qr.setErrorMsg(Your query was too broad. Try a narrower query.); These strings are used in the webui and not i18n displayed to the end user. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Closed: (DS-28) Itemmap-browse.jsp throws Exception on items without date - ID: 1745573
[ http://jira.dspace.org/jira/browse/DS-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini closed DS-28. Resolution: Fixed Itemmap-browse.jsp throws Exception on items without date - ID: 1745573 --- Key: DS-28 URL: http://jira.dspace.org/jira/browse/DS-28 Project: DSpace 1.x Issue Type: Bug Components: JSPUI Reporter: Charles Kiplagat Assignee: Claudia Jürgen Fix For: 1.5.2 Items without any date assigned make itemmap-browse.jsp to thrown an ArrayOutOfBoundsException when an item without a date results from the search (DSpace expects that every item has a date value?).. java.lang.ArrayIndexOutOfBoundsException: 0 at org.apache.jsp.tools.itemmap_002dbrowse_jsp._jspService(itemmap_002dbrowse_ jsp.java:344) BTW, patch [ 1739899 ] Implements Feature Request #1739416 Already solves this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-27) NullPointerException possible in review.jsp - ID: 1571645
[
http://jira.dspace.org/jira/browse/DS-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Bollini reopened DS-27:
--
Assignee: Claudia Jürgen
SVN commit:
http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3377
NullPointerException possible in review.jsp - ID: 1571645
-
Key: DS-27
URL: http://jira.dspace.org/jira/browse/DS-27
Project: DSpace 1.x
Issue Type: Bug
Components: JSPUI
Environment: submission/ ingest
Reporter: Charles Kiplagat
Assignee: Claudia Jürgen
Fix For: 1.5.2
In layoutSection, if inputType.equals(dropdown),
Utils.addEntities is passed the result of
DCInput.getDisplayString(). getDisplayString is
documented to return null if the input stored-value is
not matched, which will cause addEntities to throw a
NPE. The code should probably look more like the
qualdrop_value case below it, i.e. change:
row.append(Utils.addEntities(displayVal));
to:
if (displayVal != null)
{
row.append(Utils.addEntities(displayVal));
}
I am still working the problem report, but I believe
that I've seen this NPE thrown in practice. In any
case the code in review.jsp does not gracefully handle
a documented return value.
BTW the doc comments for getDisplayString (and
getStoredString) don't seem to match the code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Commented: (DS-34) Add File Format Descriptions to XMLUI 1.5.x - ID: 2433852
[ http://jira.dspace.org/jira/browse/DS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=10243#action_10243 ] Andrea Bollini commented on DS-34: -- SVN commit: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3334 Add File Format Descriptions to XMLUI 1.5.x - ID: 2433852 - Key: DS-34 URL: http://jira.dspace.org/jira/browse/DS-34 Project: DSpace 1.x Issue Type: Improvement Components: XMLUI Affects Versions: 1.5.1 Reporter: Charles Kiplagat Fix For: 1.5.2 This is a simple patch to replace the default MIME Types (e.g. application/pdf) in the DSpace 1.5.x XMLUI with File Format Descriptions (e.g. PDF). Although in past versions of DSpace these file format descriptions were resolved via the Bitstream Registry, access to this registry is constrained by the capabilities of METS. Therefore, this patch instead uses a mapping in your 'messages.xml' to resolve these file format descriptions. For example: message key=xmlui.dri2xhtml.mimetype.application/pdfPDF/message If the above mapping exists in your messages.xml, this would map the MIME Type application/pdf to the description PDF. If such a mapping doesn't exist in your messages.xml, then the MIME Type is displayed by default (making these changes backwards compatible with current XMLUI). Two patches are attached (made against latest version of SVN 1.5.x branch): * xmlui-format-General-Handler.patch (Patch for /themes/dri2xhtml/General-Handler.xsl) * xmlui-format-messages.patch (Patch for /i18n/messages.xml , English version) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Commented: (DS-33) checksum checker can not retrieve very large bitstream - ID: 2016130
[ http://jira.dspace.org/jira/browse/DS-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=10244#action_10244 ] Andrea Bollini commented on DS-33: -- SVN commit: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3332 checksum checker can not retrieve very large bitstream - ID: 2016130 Key: DS-33 URL: http://jira.dspace.org/jira/browse/DS-33 Project: DSpace 1.x Issue Type: Bug Components: DSpace API Reporter: Charles Kiplagat Fix For: 1.5.2 in the database there is a field for the size of a bitstream. it`s defined as a int8 value which is at java the datatype long. the query in the checksum checker reads this value in as a INT VALUE INSTEAD OF A LONG VALUE. if it`s realy a big file and the size doesn`t fit into the int, that`s causes an exception of course, which is catched as a SQLException and logged as Bitstream metadata could not be retrieved. the size of the bitstream is handled at the hole checksum classes as an int. that`s regarding the following classes: - Class: org.dspace.checker.BitstreamInfoDAO + Line 277: Method: findByBitstreamId - Class: org.dspace.checker.BitstreamInfo + Line 144: Constructor + Line 207/218: Methods: get/setSize - Class: org.dspace.checker.DSpaceBitstreamInfo + Line 137: Constructor + Line 202/213: Methods: get/setSize - Class: org.dspace.checker.DSpaceBitstreamInfo + Line 137: Constructor + Line 202/213: Methods: get/setSize -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-32) Export Item email hardcoded strings in sources - ID: 2411653
[ http://jira.dspace.org/jira/browse/DS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-32: -- Assignee: Claudia Jürgen SVN commit: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3385 Export Item email hardcoded strings in sources - ID: 2411653 Key: DS-32 URL: http://jira.dspace.org/jira/browse/DS-32 Project: DSpace 1.x Issue Type: Bug Components: DSpace API Reporter: Charles Kiplagat Assignee: Claudia Jürgen Fix For: 1.5.2 In org.dspace.app.itemexport.ItemExport emailSuccessMessage The texts for creating the export email are hardcoded to English. This should be internationalized. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-31) Bug 2512868 Double quote problem in some fields of JSPUI - ID: 2525942
[ http://jira.dspace.org/jira/browse/DS-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-31: -- Assignee: Claudia Jürgen SVN commit: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3384 Bug 2512868 Double quote problem in some fields of JSPUI - ID: 2525942 -- Key: DS-31 URL: http://jira.dspace.org/jira/browse/DS-31 Project: DSpace 1.x Issue Type: Improvement Components: JSPUI Reporter: Charles Kiplagat Assignee: Claudia Jürgen Fix For: 1.5.2 Fix for bug https://sourceforge.net/tracker2/?func=detailaid=2512868group_id=19984at id=119984 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Closed: (DS-31) Bug 2512868 Double quote problem in some fields of JSPUI - ID: 2525942
[ http://jira.dspace.org/jira/browse/DS-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini closed DS-31. Resolution: Fixed Bug 2512868 Double quote problem in some fields of JSPUI - ID: 2525942 -- Key: DS-31 URL: http://jira.dspace.org/jira/browse/DS-31 Project: DSpace 1.x Issue Type: Improvement Components: JSPUI Reporter: Charles Kiplagat Assignee: Claudia Jürgen Fix For: 1.5.2 Fix for bug https://sourceforge.net/tracker2/?func=detailaid=2512868group_id=19984at id=119984 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Reopened: (DS-30) Hardcoded String in jspui browse - ID: 2526153
[ http://jira.dspace.org/jira/browse/DS-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Bollini reopened DS-30: -- SVN commit: http://dspace.svn.sourceforge.net/viewvc/dspace?view=revrevision=3383 Hardcoded String in jspui browse - ID: 2526153 -- Key: DS-30 URL: http://jira.dspace.org/jira/browse/DS-30 Project: DSpace 1.x Issue Type: Improvement Reporter: Charles Kiplagat Fix For: 1.5.1 In browse/full.jsp and browse/single.jsp the label for the submit button is hardcoded, see: input type=submit name=submit_browse value=Update/ This small patch adds a tag to Messages.properties and replaces the string Update with the fmt tag. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
