[Dspace-devel] [DSJ] Commented: (DS-332) Localization aspect for DSpace 1.5.2
[ http://jira.dspace.org/jira/browse/DS-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=11795#action_11795 ] Tonny Hjelmberg Laursen commented on DS-332: Please add this to version 1.7. It's very needed and much more user-friendly than the current. Localization aspect for DSpace 1.5.2 Key: DS-332 URL: http://jira.dspace.org/jira/browse/DS-332 Project: DSpace 1.x Issue Type: New Feature Components: XMLUI Affects Versions: 1.5.2 Reporter: Andreas Schwander Priority: Minor Attachments: localization.patch, LocalizationAspect.zip, readme.txt The aspect overwrites the DSpaceLocaleAction.class so that the current locale gets stored in the active session. Additionally it adds all languages configured by xmlui.supportedLocales to the pageMeta section of the xml file. Finally this information will be provided examplarily on top of the navigation bar by the locales.xsl. Please read the readme.txt for more information on how to install and use this aspect. Fixed issues: DS331 This is just an unfinished version of all the files as I developed them for our local repository. If this function is favoured by the community i will consider the ContributionGuidelines again and add documentation and stuff. -- 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 -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSJ] Commented: (DS-79) Pluggable storage / S3 - ID: 2561561
[ http://jira.dspace.org/jira/browse/DS-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=11796#action_11796 ] Razan Abbass commented on DS-79: [cheap flights|http://getflightsto.com] [baby names|http://childcareforums.com] Pluggable storage / S3 - ID: 2561561 Key: DS-79 URL: http://jira.dspace.org/jira/browse/DS-79 Project: DSpace 1.x Issue Type: Improvement Reporter: Charles Kiplagat Marked as 'prototype only, not read for production'; not against current code base. -- 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 -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSJ] Created: (DS-703) Making the OAI max amount of records configurable
Making the OAI max amount of records configurable - Key: DS-703 URL: http://jira.dspace.org/jira/browse/DS-703 Project: DSpace 1.x Issue Type: Improvement Components: OAI-PMH Affects Versions: 1.7.0 Reporter: Ben Bosman Assignee: Ben Bosman Priority: Minor The maximum amount of records is currently fixed to 100. This should be configurable in order to ensure compatibility with some OAI harvesters. -- 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 -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSJ] Commented: (DS-703) Making the OAI max amount of records configurable
[ http://jira.dspace.org/jira/browse/DS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=11797#action_11797 ] Ben Bosman commented on DS-703: --- A parameter oai.response.max-records has been included. This parameter is not required, and has a default value of 100 which implies there are no changes to the behavior unless the user alters this parameter. The description of this parameter is as follows: # DSpace by default uses 100 records as the limit for the oai responses. # This can be altered by enabling the oai.response.max-records parameter # and setting the desired amount of results. oai.response.max-records = 100 Making the OAI max amount of records configurable - Key: DS-703 URL: http://jira.dspace.org/jira/browse/DS-703 Project: DSpace 1.x Issue Type: Improvement Components: OAI-PMH Affects Versions: 1.7.0 Reporter: Ben Bosman Assignee: Ben Bosman Priority: Minor The maximum amount of records is currently fixed to 100. This should be configurable in order to ensure compatibility with some OAI harvesters. -- 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 -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] Command Line Harvester
I've been working on the harvest scheduler and I've made some good progress and I'm almost ready to say it's done and finish up with some more testing. However I've discovered a problem with running the OAI-PMH harvester. I've been using the XMLUI interface to run the harvester so far and it's been running fine. However I then tried running the harvester using the command 'dspace harvest -S'. It says it's starting the harvest loop and returns me to a command prompt. However neither XMLUI or JSPUI seem to show any harvesting and I've read through the log files (and I've added more log.info statements to try and narrow down the problem) and it seems like it's jamming at the line: TableRow row = tri.next(); I've made sure that there is a row in the table (harvested_collection) before running the query so I don't think that's the issue. The really odd thing is that when you run the harvester from the XMLUI control panel this same code runs perfectly. Has anyone else encountered problems when working with the command line interface for the DSpace OAI-PMH harvester? Thank you in advance, - Paul Brindley *** Visit the National Library of Scotland online at www.nls.uk *** Please consider the environment before printing this e-mail. This communication is intended for the addressee(s) only. If you are not the intended recipient, please notify the Information Systems Helpdesk on +44 131 623 3789 or is.helpd...@nls.uk and delete this e-mail. The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the National Library of Scotland. The National Library of Scotland is a registered Scottish charity. Scottish Charity No. SC011086. This message is subject to the Data Protection Act 1998 and Freedom of Information (Scotland) Act 2002 and has been scanned by Webroot. *** Follow us on Twitter for twice-weekly updates. Become our fan on Facebook and keep up-to-date that way too. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] NOTICE: JIRA Migration Complete!
All, The JIRA Migration is now complete! All DSpace projects are now available in the DuraSpace JIRA (alongside Fedora Duracloud projects): http://jira.duraspace.org/ Previous http://jira.dspace.org/; URLs should also now redirect you to the new location. *Special Notice for DSpace Developers Users* You can now use the *same username and password* to access both the Wiki and JIRA. As previously mentioned, some DSpace Developers or Users may find you will need to reset your password before you will be able to login (this should only occur if you didn't previously have a Wiki password setup). If you find you need to reset your password, please visit the following page to reset it: https://wiki.duraspace.org/forgotuserpassword.action (Again, the above page will reset your password for *both* the Wiki and JIRA.) Once you have reset your password (if necessary), you should find that you have the same permissions as before within JIRA for all DSpace Projects. If you encounter any issues or problems with accessing your account, you can email us at sysad...@duraspace.org for help, or contact me directly (tdono...@duraspace.org). Thanks, Tim On 10/12/2010 10:39 AM, Tim Donohue wrote: All, This Thursday morning (Oct 14th from 9:30am-11:30am ET), DuraSpace will be merging the JIRA instance for the DSpace Project (http://jira.dspace.org) into the central DuraSpace JIRA (http://jira.duraspace.org), used by Fedora-Commons and DuraCloud. This migration will make it easier for cross-project development to occur, while also providing a much needed JIRA upgrade to the DSpace Developer community. Each of our developer communities can expect the following: === For DSpace Developers / Users === * On Thursday, during the migration, the DSpace JIRA (http://jira.dspace.org) will be continue to be available but will be READ-ONLY. * After the migration completes, you will be automatically redirected to the new JIRA location. All previously saved links/bookmarks to issues should redirect automatically to their new location. (However, saved JIRA searches or filters may no longer work and may need to be recreated.) * Your JIRA Login information: ** If you have an existing Wiki Account (http://wiki.dspace.org), after the migration completes you will use that same account password to access JIRA. (If you have forgotten your password, you can also request to reset it. More information about resetting your password will be sent after the migration has completed.) ** If you do not already have a Wiki account, your existing JIRA username will be auto-migrated to the new system. However, your password will NOT be migrated automatically. *AFTER THE MIGRATION, YOU WILL NEED TO RESET YOUR PASSWORD.* More information about resetting your password will be sent after the migration has completed. === For Fedora or DuraCloud Developers / Users === This migration will only minimally affect your access to the DuraSpace JIRA system (http://jira.duraspace.org). The DuraSpace JIRA will be restarted briefly at the start of the migration (around 9:30 AM ET) to perform a full system backup. After that, you will be able to access DuraSpace JIRA as normal. However, during the migration itself, JIRA may be slow to respond at times. Please let me know if you should have any questions or concerns. Thanks, - Tim -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-618) Recommended versions of prerequisites becoming outdated
I'm told that I managed to file a JIRA comment before the automatic email to the devel list was re-engaged, so here it is (attached). -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Balance your desire for bells and whistles with the reality that only a little more than 2 percent of world population has broadband. -- Ledford and Tyler, _Google Analytics 2.0_ ---BeginMessage--- [ https://jira.duraspace.org/browse/DS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=17768#action_17768 ] Mark H. Wood commented on DS-618: - From 13-Oct-2010 IRC meeting, concerning Oracle versions to recommend: (17:07:01) HardyPottinger: word from our DBA is: I would recommend nothing less than 10g, and preferably 11g. 9i support will soon be deprecated, and if they can support 11 it would be best to do that as the lifespan will be the longest I will suggest that we recommend: Oracle: 10g minimum, suggest 11. Recommended versions of prerequisites becoming outdated --- Key: DS-618 URL: https://jira.duraspace.org/browse/DS-618 Project: DSpace 1.x Issue Type: Task Components: Documentation Reporter: Mark H. Wood Assignee: Mark H. Wood Fix For: 1.7.0 We still recommend at least PostgreSQL 7.3 or 7.4. 7.4 is now seven years old and losing maintainer support next month (or so). By December only 8.2 and up will be supported. Sun Java 5 SE reaches its End Of Service Life in October 2010. Maven 2.2 is current. We might recommend at least 2.0.11 (the current older release) rather than 2.0.8. Tomcat 4 is positively ancient and definitely unsupported by its maintainers. Even 5.0 is too old for help. 5.5 should be our minimum recommendation. Please discuss. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---End Message--- pgpKkvyvtUtfM.pgp Description: PGP signature -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Subscription: DSpace JIRA Issues Needing Review
Issue Subscription Filter: DSpace JIRA Issues Needing Review (25 issues) The following issues have not been reviewed. If you have time, please review them. If the issue can be reproduced or seems valid, please move it into the Open status (which signifies that it has been reviewed by someone). Please double check all issue metadata (especially the version/components of DSpace that this issue affects) and, if possible, assign it to someone. Subscriber: tdonohue Key Summary DSB-62 DSpace remote log viewer. https://jira.duraspace.org/browse/DSB-62 DS-641 Page does not exist https://jira.duraspace.org/browse/DS-641 DS-645 Enhanced embargo functionality https://jira.duraspace.org/browse/DS-645 DS-651 DSpace Intermediate Metadataformat DIM - include handle or ID https://jira.duraspace.org/browse/DS-651 DS-652 Wrong behaviour of special groups at login. Use only special groups of the authetication that DID authenticate the user. https://jira.duraspace.org/browse/DS-652 DS-655 MetadataExposure hides fields except for System Admins - this should extend to Community and Collection Admins https://jira.duraspace.org/browse/DS-655 DS-658 Provide a nonAnon attribute to XMLUI theme https://jira.duraspace.org/browse/DS-658 DS-659 Collection.findAll performance issue - offset and limit improvement https://jira.duraspace.org/browse/DS-659 DS-667 Add a remote log viewer to DSpace. https://jira.duraspace.org/browse/DS-667 DS-669 icons of restricted bitstreams https://jira.duraspace.org/browse/DS-669 DS-671 One item of my dspace is a pdf file ( from a scanner ) = 240 Mb when i try to download it from my dspace i get a pdf file 87Mb and unusable https://jira.duraspace.org/browse/DS-671 DS-672 Nullpointer exception when bogus information is entered in the Embargo date field during submission https://jira.duraspace.org/browse/DS-672 DS-673 My Archived Submissions https://jira.duraspace.org/browse/DS-673 DS-674 Add and Remove Selected actions on individual metadata fields have an effect on the whole form https://jira.duraspace.org/browse/DS-674 DS-675 XMLUI doesn't start if the error level in the log4j.properties is set to DEBUG https://jira.duraspace.org/browse/DS-675 DS-677 xmlui BitstreamReader holds database connections open while large files download, exhausting connection pool https://jira.duraspace.org/browse/DS-677 DS-678 Community Admin unable to create new bundle type for items https://jira.duraspace.org/browse/DS-678 DS-680 invalid input syntax for type timestamp in db query for stat-initial utility https://jira.duraspace.org/browse/DS-680 DS-681 Updating groups performs badly with a large number of groups. https://jira.duraspace.org/browse/DS-681 DS-682 The Select Collection step performs badly with a large number of collections. https://jira.duraspace.org/browse/DS-682 DS-683 Incorporate Security / Quality recommendations from AppScan report https://jira.duraspace.org/browse/DS-683 DS-670 Relax performance tests in org.dspace.content.CommunityCollectionIntegrationTest. https://jira.duraspace.org/browse/DS-670 DS-685 Remove sensitive information from HTML comments https://jira.duraspace.org/browse/DS-685 DS-700 Bulk Metadata Editing: defining formats for export/re-import of selected fields https://jira.duraspace.org/browse/DS-700 DS-679 Modifying dspace oai code to offer harvesting through collection : harvest any item with a request on metadatavalue https://jira.duraspace.org/browse/DS-679 -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] Where to document API changes?
Where would be the proper place(s) to document API changes? I have a patch (DS-494) which would affect others who have locally made use of SQL that returns NUMERIC or DECIMAL results (typically from an SQL built-in function). They need to know that (a) a wider range of values is available, and (b) they need to use getLong() on those results, because getInt() will now throw an exception on them. I don't recall seeing a release-notes section for internals. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Balance your desire for bells and whistles with the reality that only a little more than 2 percent of world population has broadband. -- Ledford and Tyler, _Google Analytics 2.0_ pgpN0M30HtHkG.pgp Description: PGP signature -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-494) DatabaseManager.process() unnecessarily limits range of DECIMAL or NUMERIC
[ https://jira.duraspace.org/browse/DS-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark H. Wood updated DS-494: Attachment: DS-494.patch Updated patch, adding the corresponding change to execute(). DatabaseManager.process() unnecessarily limits range of DECIMAL or NUMERIC -- Key: DS-494 URL: https://jira.duraspace.org/browse/DS-494 Project: DSpace 1.x Issue Type: Bug Components: DSpace API Affects Versions: 1.5.2, 1.6.0 Environment: PostgreSQL Reporter: Mark H. Wood Assignee: Mark H. Wood Fix For: 1.7.0 Attachments: DatabaseManager.patch, DS-494.patch INTEGER, DECIMAL, and NUMERIC are lumped together. In the case we are using Oracle, the code will set the column to an int or a long depending on the size of the value. (I would like to know why we bother.) Otherwise the value is assumed to be within the range of int. But DECIMAL and NUMERIC can be far larger than int, and are returned by e.g. sum(BIGINT). The attached patch widens the result, in the non-Oracle case, to long for all three SQL datatypes. Strictly speaking, DECIMAL and NUMERIC should be mapped to java.math.BigDecimal, but that requires the introduction of new methods to TableRow as well. Widening from int to long probably covers most of the real-world cases. The patch is against 1.5.2 but also applies to 1.6.0-rc2. I would appreciate comments on how this widening may affect other code. The patch is in test on a live system, but in a locally-developed webapp rather than any of the main DSpace UIs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-79) Pluggable storage / S3 - ID: 2561561
[ https://jira.duraspace.org/browse/DS-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-79: -- Comment: was deleted (was: [cheap flights|http://getflightsto.com] [baby names|http://childcareforums.com] ) Pluggable storage / S3 - ID: 2561561 Key: DS-79 URL: https://jira.duraspace.org/browse/DS-79 Project: DSpace Issue Type: Improvement Reporter: Charles Kiplagat Priority: Major Marked as 'prototype only, not read for production'; not against current code base. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-631) Wrong Parameter Name in web.xml comment
[ https://jira.duraspace.org/browse/DS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=17773#action_17773 ] Mark Diggory commented on DS-631: - Hi Mark, Unfortunately, with the current level of activity on devel its hard for me to catch relevant emails. I saw this one however... We should actually look at the version of solr we are using in 1.7 stats and discovery and work on slightly cleaning it up. I'm tempted to suggest going for a straight to the 1.4.1 solr release now that it is out. We pulled back using some of the customizations we had to solr in the recent updates to discovery. So I'm pretty comfortable with doing this now. http://lucene.apache.org/solr/#25+June+2010+-+Solr+1.4.1+Released I'll also add that we are working on a more mature restriction approach, but understand, it is necessary to have restriction on the solr instance because the data that is inside can be considered sensitive. Mark Wrong Parameter Name in web.xml comment --- Key: DS-631 URL: https://jira.duraspace.org/browse/DS-631 Project: DSpace Issue Type: Bug Components: Solr Affects Versions: 1.6.2 Reporter: Andy Smith Assignee: Mark H. Wood Fix For: 1.7.0 Attachments: solr.patch There is a comment in web.xml for solr in modules/tags/dspace-solr-1.3.0.2 (which is currently pulled into 1.6.2) for turning off the LocalHostRestrictionFilter. The comment has cut and paste code for turning off the filter by placing it in a Tomcat context file. However, the wrong parameter name is given. Instead of LocalHostRestrictionFilter.enabled, it should be LocalHostRestrictionFilter.localhost as is required for the filter code. We had to disable this filter in order to get SOLR working for a rather complex setup where localhost would not work in the solr.log.server configuration value. To restrict access we implemented RemoteAddrValve in the same context file that the altered code resides. The patch attached is to go against modules/tags/dspace-solr-1.3.0.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Patching dspace-solr: which one?
Hi Mark, See my JIRA comment... Mark On Wed, Oct 13, 2010 at 10:29 AM, Mark H. Wood mw...@iupui.edu wrote: Regarding DS-631, I'm wondering where to apply the patch. If I patch a tagged revision, the patch creates a new revision and thus won't be reflected in the tagged revision. dspace-solr trunk doesn't seem to contain the problematic parameter, so maybe the problem is already fixed? But dspace trunk still depends on the 1.3.0.2 tag. Will a new revision of dspace-solr be tagged for dspace 1.7 (and the dependency updated), and from where? -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Balance your desire for bells and whistles with the reality that only a little more than 2 percent of world population has broadband. -- Ledford and Tyler, _Google Analytics 2.0_ -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Mark R. Diggory Head of U.S. Operations - @mire, Inc. http://www.atmire.com - Institutional Repository Solutions -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-521) Port JSPUI Currently Active Workflows list to XMLUI
[ https://jira.duraspace.org/browse/DS-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Shepherd updated DS-521: Due Date: (was: 25/Mar/10) Fix Version/s: (was: 1.7.0) Updated Fix Versions to Unknown, this will not be completed in time for 1.7 feature freeze Port JSPUI Currently Active Workflows list to XMLUI - Key: DS-521 URL: https://jira.duraspace.org/browse/DS-521 Project: DSpace Issue Type: New Feature Components: XMLUI Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0 Environment: DSpace 1.6 and previous, XMLUI, any server environment Reporter: Kim Shepherd Assignee: Kim Shepherd Priority: Major Port the useful list of all active workflows / workflow tasks to XMLUI administrative aspect, based on the JSPUI version (workflow-list.jsp) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-632) Batch Metadata Import needs to validate metadata fields specified in CSVs
[ https://jira.duraspace.org/browse/DS-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-632: Attachment: (was: [DS-632]_Batch_Metadata_Import_needs_to_validate_metadata_fields_specified_in_CSVs.patch) Batch Metadata Import needs to validate metadata fields specified in CSVs - Key: DS-632 URL: https://jira.duraspace.org/browse/DS-632 Project: DSpace Issue Type: Bug Components: DSpace API Affects Versions: 1.6.0, 1.6.1, 1.6.2 Environment: All Reporter: Kim Shepherd Assignee: Stuart Lewis Priority: Major Fix For: 1.7.0 Attachments: [DS-632]_Batch_Metadata_Import_needs_to_validate_metadata_fields_specified_in_CSVs.patch Batch metadata importer does not properly validate metadata fields specified in the uploaded CSV. If a user uploads a CSV with a non-existent metadata field name, changes will be displayed as though the CSV were valid, then when the user confirms, they will be told No changes detected, 0 processed. However, the items get ingested as completely empty items containing no metadata, without being deleted from the uploader's workspace. As a result, the administrator/uploader can not delete the item from the collection (as there is an fkey reference to workspace_items) and can not remove the item from the workspace, as there is a reference to collection2item. Manual SQL queries must be run to completely remove the object. Proposed solution: Quick validation against metadata registries before displaying confirmation of changes, and display an error if a field does not exist or is invalid in some other way (formatting, rights, etc.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-632) Batch Metadata Import needs to validate metadata fields specified in CSVs
[ https://jira.duraspace.org/browse/DS-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-632: Attachment: [DS-632]_Batch_Metadata_Import_needs_to_validate_metadata_fields_specified_in_CSVs.patch Updated patch. XMLUI and JSPUI now display meaningful i18n'd messages Batch Metadata Import needs to validate metadata fields specified in CSVs - Key: DS-632 URL: https://jira.duraspace.org/browse/DS-632 Project: DSpace Issue Type: Bug Components: DSpace API Affects Versions: 1.6.0, 1.6.1, 1.6.2 Environment: All Reporter: Kim Shepherd Assignee: Stuart Lewis Priority: Major Fix For: 1.7.0 Attachments: [DS-632]_Batch_Metadata_Import_needs_to_validate_metadata_fields_specified_in_CSVs.patch Batch metadata importer does not properly validate metadata fields specified in the uploaded CSV. If a user uploads a CSV with a non-existent metadata field name, changes will be displayed as though the CSV were valid, then when the user confirms, they will be told No changes detected, 0 processed. However, the items get ingested as completely empty items containing no metadata, without being deleted from the uploader's workspace. As a result, the administrator/uploader can not delete the item from the collection (as there is an fkey reference to workspace_items) and can not remove the item from the workspace, as there is a reference to collection2item. Manual SQL queries must be run to completely remove the object. Proposed solution: Quick validation against metadata registries before displaying confirmation of changes, and display an error if a field does not exist or is invalid in some other way (formatting, rights, etc.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-632) Batch Metadata Import needs to validate metadata fields specified in CSVs
[ https://jira.duraspace.org/browse/DS-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis resolved DS-632. - Resolution: Fixed Author: stuartlewis Date: Fri Oct 15 02:53:20 2010 New Revision: 5429 Log: [DS-632] Batch Metadata Import needs to validate metadata fields specified in CSVs Batch Metadata Import needs to validate metadata fields specified in CSVs - Key: DS-632 URL: https://jira.duraspace.org/browse/DS-632 Project: DSpace Issue Type: Bug Components: DSpace API Affects Versions: 1.6.0, 1.6.1, 1.6.2 Environment: All Reporter: Kim Shepherd Assignee: Stuart Lewis Priority: Major Fix For: 1.7.0 Attachments: [DS-632]_Batch_Metadata_Import_needs_to_validate_metadata_fields_specified_in_CSVs.patch Batch metadata importer does not properly validate metadata fields specified in the uploaded CSV. If a user uploads a CSV with a non-existent metadata field name, changes will be displayed as though the CSV were valid, then when the user confirms, they will be told No changes detected, 0 processed. However, the items get ingested as completely empty items containing no metadata, without being deleted from the uploader's workspace. As a result, the administrator/uploader can not delete the item from the collection (as there is an fkey reference to workspace_items) and can not remove the item from the workspace, as there is a reference to collection2item. Manual SQL queries must be run to completely remove the object. Proposed solution: Quick validation against metadata registries before displaying confirmation of changes, and display an error if a field does not exist or is invalid in some other way (formatting, rights, etc.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Assigned: (DS-646) Remove /bin scripts (replaced by 'dspace' commmand)
[ https://jira.duraspace.org/browse/DS-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reassigned DS-646: --- Assignee: Jeffrey Trimble (was: Stuart Lewis) Changes made to DSpace bin's directory. Now to check all the documentation. Remove /bin scripts (replaced by 'dspace' commmand) --- Key: DS-646 URL: https://jira.duraspace.org/browse/DS-646 Project: DSpace Issue Type: Task Components: DSpace API Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2 Reporter: Stuart Lewis Assignee: Jeffrey Trimble Fix For: 1.7.0 Must also check documentation to ensure all references have been removed. [08:52am] stuartlewis: Can I raise a quick question? In 1.6.1 we sort-of deprecated the /bin scripts. Can we vote to remove them in 1.7? [08:53am] stuartlewis: (just leave 'dspace', and any non-java scripts) [08:53am] mhwood: If it's been announced already, and we make some more noise as release approaches, I think we should do that. [08:54am] bollini: I agree too [08:54am] tdonohue: hi stuartlewis -- sure, we can vote on that... I'd be +1 [08:54am] kgerbeitson: +1, definitely with noise [08:54am] kshepherd: yep, +1 to removal and to more noise/documentation [08:54am] richardrodgers: stuartlewis: can we replace them with clones that say 'use dpsace'? [08:55am] kshepherd: richardrodgers: hmm.. that's a good idea for people who forget about old cronjobs, etc. [08:55am] richardrodgers: (just to be a little friendlier about pulling the rug out) [08:55am] stuartlewis: richardrodgers: Maybe, but we've got to deprecate them sometime, so it might just confuse people more? Maybe a clean cut is better? Especially if people run these via cron, they might not see the warning message. [08:55am] richardrodgers: true - it might get lost [08:55am] kshepherd: it it's stderr output, cron should email it [08:55am] mhwood: If they don't see the message from a cron job, will they see the job fail? [08:56am] PeterDietz: also, are we changed the header code license to be a bit more abbreviated [08:56am] stuartlewis: So we're plus four (incl me) for dropping the scripts. Any other votes? [08:56am] tdonohue: I'd like to see us actually cut things off that we 'deprecate', and just document/announce it broadly (we've been notoriously bad about this in the past -- we've been releasing with a deprecated DCValue class for years now) [08:57am] richardrodgers: +1 ok with me [08:57am] stuartlewis: Thanks - will get that done. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] Removal of [dspace]/bin/ scripts
Hi all, Today I have completed the work for https://jira.duraspace.org/browse/DS-646 by removing all the [dspace]/bin scripts. The only ones left are special (related to the handle server) or for the 'dspace' launcher itself. We now need to check the documentation to edit all references to the scripts, or to dsrun (which is now [dspace]/bin/dspace dsrun ...). This is quite a major change, so apologies if anything has broken as a result! All the scripts I've tested seem to work OK though, and we can get this tested on demo.dspace.org with its handle. One question though - there are a few perl / shell scripts left over that aren't really actively mainained or used, such as dspace-info.pl and dspace_migrate. Should we consider removing these, or putting them in a directory called 'unsupported'? Now that there aren't so many files in the bin directory, they look a bit more obvious now. Cheers, Stuart Lewis IT Innovations Analyst and Developer 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 -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
