[Dspace-devel] [DuraSpace JIRA] Updated: (DS-871) XMLUI caches community / collection page which doesn't show a recently submitted item immediately
[ https://jira.duraspace.org/browse/DS-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-871: --- Attachment: DS-871-invalidate-cache-on-recycle.diff I have what seems to be a solution to this bug. When CommunityRecentSubmissions.java and CollectionRecentSubmissions.java were refactored from CommunityViewer/CollectionViewer, it appears that they forgot to nullify their validity. This patch invalidates when the object is recycled. Which fixes recent submissions. To see this commit in context: https://github.com/peterdietz/DSpace/commit/f24e34fa8dc8aafcd5e4544e73e44fccc3246f0b > XMLUI caches community / collection page which doesn't show a recently > submitted item immediately > - > > Key: DS-871 > URL: https://jira.duraspace.org/browse/DS-871 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.7.0, 1.7.1 >Reporter: Peter Dietz > Attachments: DS-871-invalidate-cache-on-recycle.diff > > > With discovery disabled in xmlui, a recently submitted item does not show on > the recently submitted items list for the collection or community page, until > the page cache expires. This may be by design, but it is a route that a user > may be expecting to find their recently submitted item. > Perhaps on submission, the cache for the parent container pages can be > invalidated so that the next page view of it will get the recently submitted > item in the list. > To reproduce, in xmlui (tested with discovery off), view a collection page, > then submit a new item to that collection, and go back to that collection > page after submission. Continuously refreshing the page will not show the new > item, unless a user tries to hard-clear the xmlui cache. Such as appending > junk to the url as a parameter. i.e. > servername.com/handle/123456789/1234?random-text -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-898) Caching error in browse, search and discovery results
[ https://jira.duraspace.org/browse/DS-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20334#action_20334 ] Peter Dietz commented on DS-898: @Hardy, See the commit to trunk/1.8 for your patch: Pretty: https://github.com/DSpace/DSpace/commit/9a907b0f5ebabb7686d982f3213443a659a7a359 Diff/patch: https://github.com/DSpace/DSpace/commit/9a907b0f5ebabb7686d982f3213443a659a7a359.diff @Mark and @Tim, I think we'll stick with our decision to keep 1.7.2 limited to things broken _by_ the 1.7.x work. Since this appears to have affected previous versions (1.6.x) as well, then the general fix can come in 1.8.0. > Caching error in browse, search and discovery results > - > > Key: DS-898 > URL: https://jira.duraspace.org/browse/DS-898 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.6.0, 1.6.1, 1.6.2, 1.7.0, 1.7.1 >Reporter: Ben Bosman >Assignee: Ben Bosman >Priority: Major > Fix For: 1.8.0 > > > The results page for browse, search and discovery uses caching based on the > validity. This validity takes the listed items into account. It doesn't take > the amount of results into account however. > The total amount of results is incorrect if the page was rendered before, and > the same list of items is returned, but some items are added or removed which > are not displayed on the current page -- 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 -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Closed: (DS-871) XMLUI caches community / collection page which doesn't show a recently submitted item immediately
[ https://jira.duraspace.org/browse/DS-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz closed DS-871. -- Resolution: Fixed Fix Version/s: 1.8.0 Assignee: Peter Dietz Committed the proposed patch to 1.7.x (to make it into 1.7.2), and to trunk to make it into 1.8 > XMLUI caches community / collection page which doesn't show a recently > submitted item immediately > - > > Key: DS-871 > URL: https://jira.duraspace.org/browse/DS-871 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.7.0, 1.7.1 >Reporter: Peter Dietz >Assignee: Peter Dietz > Fix For: 1.7.2, 1.8.0 > > Attachments: DS-871-invalidate-cache-on-recycle.diff > > > With discovery disabled in xmlui, a recently submitted item does not show on > the recently submitted items list for the collection or community page, until > the page cache expires. This may be by design, but it is a route that a user > may be expecting to find their recently submitted item. > Perhaps on submission, the cache for the parent container pages can be > invalidated so that the next page view of it will get the recently submitted > item in the list. > To reproduce, in xmlui (tested with discovery off), view a collection page, > then submit a new item to that collection, and go back to that collection > page after submission. Continuously refreshing the page will not show the new > item, unless a user tries to hard-clear the xmlui cache. Such as appending > junk to the url as a parameter. i.e. > servername.com/handle/123456789/1234?random-text -- 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 -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-904) Non consistant naming of Creative Commons license bundle
Non consistant naming of Creative Commons license bundle Key: DS-904 URL: https://jira.duraspace.org/browse/DS-904 Project: DSpace Issue Type: Bug Components: XMLUI Affects Versions: 1.7.1, 1.7.0, 1.6.2, 1.6.1, 1.6.0, 1.5.2, 1.5.1, 1.5.0 Environment: xmlui Reporter: Peter Dietz Assignee: Peter Dietz Fix For: 1.8.0 The creative commons license bundle is typically called CC-LICENSE, however, XMLUI's Edit Item page for uploading bitstreams directly to an item allows you to upload bitstreams to a bundle called CC_LICENSE. The bundle names are different by an underscore. By default Creative Commons is not used, but if it is used, then the potential for this problem exists. In addition to just changing the value to be the correct one (CC-LICENSE), we should also use a constant for the bundle name of creative commons (and all other should-be constants). -- 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 -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-904) Non consistant naming of Creative Commons license bundle
[ https://jira.duraspace.org/browse/DS-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-904: --- Attachment: DS-904-fix-xmlui-cclicense-bundle.patch Attached patch that changes xmlui's edit item, upload bitstream to use CC-LICENSE, instead of CC_LICENSE. > Non consistant naming of Creative Commons license bundle > > > Key: DS-904 > URL: https://jira.duraspace.org/browse/DS-904 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0, 1.7.1 > Environment: xmlui >Reporter: Peter Dietz >Assignee: Peter Dietz > Fix For: 1.8.0 > > Attachments: DS-904-fix-xmlui-cclicense-bundle.patch > > > The creative commons license bundle is typically called CC-LICENSE, however, > XMLUI's Edit Item page for uploading bitstreams directly to an item allows > you to upload bitstreams to a bundle called CC_LICENSE. The bundle names are > different by an underscore. > By default Creative Commons is not used, but if it is used, then the > potential for this problem exists. In addition to just changing the value to > be the correct one (CC-LICENSE), we should also use a constant for the bundle > name of creative commons (and all other should-be constants). -- 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 -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-841) 'IllegalArgumentException: No such column rnum' error in DSpace 1.7.x XMLUI admin eperson (with Oracle backend)
[ https://jira.duraspace.org/browse/DS-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz resolved DS-841. Documentation Status: Not Required (was: Needed) Resolution: Fixed Assignee: Peter Dietz Committed to 1.7.x branch for 1.7.2, and to trunk for 1.8 > 'IllegalArgumentException: No such column rnum' error in DSpace 1.7.x XMLUI > admin eperson (with Oracle backend) > --- > > Key: DS-841 > URL: https://jira.duraspace.org/browse/DS-841 > Project: DSpace > Issue Type: Bug >Affects Versions: 1.7.0, 1.7.1 > Environment: RHEL5, with Oracle on the back end >Reporter: Hardy Pottinger >Assignee: Peter Dietz > Fix For: 1.7.2 > > Attachments: DS-841-fix-Oracle-compatibility-for-ePerson.patch > > > In using the 1.7.x branch for testing with Oracle. Everything installed fine, > and I've got a bare-bones repository up and running. However, in the XMLUI, > when I click on the admin ePeople link, I get the following error: > java.lang.IllegalArgumentException: No such column rnum > Here are the first few lines of the stack trace: > java.lang.IllegalArgumentException: No such column rnum > at > org.dspace.storage.rdbms.TableRow.canonicalizeAndCheck(TableRow.java:581) > at org.dspace.storage.rdbms.TableRow.setColumn(TableRow.java:433) > at > org.dspace.storage.rdbms.DatabaseManager.process(DatabaseManager.java:) > at > org.dspace.storage.rdbms.TableRowIterator.next(TableRowIterator.java:151) > at > org.dspace.storage.rdbms.TableRowIterator.toList(TableRowIterator.java:204) > at org.dspace.eperson.EPerson.search(EPerson.java:358) > at > org.dspace.app.xmlui.aspect.administrative.eperson.ManageEPeopleMain.addBody(ManageEPeopleMain.java:121) > at > org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:223) > at sun.reflect.GeneratedMethodAccessor213.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71) > at $Proxy66.startElement(Unknown Source) > at > org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87) > at > org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94) > at > org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:240) > at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71) > at $Proxy49.startElement(Unknown Source) > No such error is thrown when using the JSPUI. > > org.dspace.storage.rdbms.TableRow.canonicalizeAndCheck(TableRow.java:581 > Looking more closely at the stack trace, the problem appears to be that the > canonicalizeAndCheck method in TableRow is failing when it attempts to verify > the rnum column, which is created back in org.dspace.eperson.EPerson.search. -- 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 -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-914) Allowing Metadata editors to remove/change files during the workflow
[ https://jira.duraspace.org/browse/DS-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-914: --- Component/s: XMLUI Affects Version/s: 1.6.0 1.6.1 1.6.2 1.7.0 1.7.1 I believe this is just a shortcoming of XMLUI, as my librarians report that they could do this with JSPUI. (This feature was just never implemented in XMLUI). Its on our list of "eventual" things we'd like to do at Ohio State. So count this as another vote from OSU. > Allowing Metadata editors to remove/change files during the workflow > > > Key: DS-914 > URL: https://jira.duraspace.org/browse/DS-914 > Project: DSpace > Issue Type: Improvement > Components: XMLUI >Affects Versions: 1.6.0, 1.6.1, 1.6.2, 1.7.0, 1.7.1 >Reporter: Bram Luyten (@mire) > > Currently, metadata editors can not alter the files during the workflow > operations. The only options are to reject submissions, allowing the > submitter to change the files, or approving them and doing the edits after > approval. > Editors should be able to change the files. Alternatively, there could be a > config option to determine whether they should be able to do this. > I've heard this request from a few people in the meanwhile and hope they will > chime in here. In terms of development work this should take close to no time > to implement. -- 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 -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-708) Deprecate & Remove old 'org.dspace.app.mets.METSExport' class, as it is obsolete
[ https://jira.duraspace.org/browse/DS-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21036#action_21036 ] Peter Dietz commented on DS-708: Would it be too much to ask by saying we should follow the agnostic convention of: metadata.hide.SCHEMA.ELEMENT.QUALIFIER = true https://wiki.duraspace.org/display/DSDOC/Configuration#Configuration-HidingMetadata > Deprecate & Remove old 'org.dspace.app.mets.METSExport' class, as it is > obsolete > > > Key: DS-708 > URL: https://jira.duraspace.org/browse/DS-708 > Project: DSpace > Issue Type: Code Task > Components: DSpace API, OAI-PMH >Affects Versions: 1.7.0 >Reporter: Tim Donohue >Assignee: Tim Donohue > Fix For: 1.8.0 > > Attachments: DS-708-dspace-api.patch, DS-708-dspace-oai-api.patch, > sample-mods-properties.patch > > > With the improvements that have happened to the METS Ingest and Dissemination > packager classes in DSpace 1.7.0 (see DS-466), we should deprecate & remove > the old 'org.dspace.app.mets.METSExport' class, as it is now considered > obsolete. > This older METSExport class is currently used in the following places: > * OAI-PMH interface (by the org.dspace.app.oai.METSCrosswalk class) > My proposal is to deprecate this class in DSpace 1.7.0, and then work to > remove & replace its usage within the OAI-PMH interface in the next major > version of DSpace (1.8.0). > The replacement for METSExport is the following classes: > * org.dspace.content.packager.DSpaceMETSDisseminator > * org.dspace.content.packager.DSpaceMETSIngester -- 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 -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-528) RSS feeds to support richer features, such as iTunes Podcast or Media RSS
[ https://jira.duraspace.org/browse/DS-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21085#action_21085 ] Peter Dietz commented on DS-528: I have published my latest code needed to support iTunes Podcast on my GitHub: https://github.com/peterdietz/DSpace/commit/0a87ba181c149bba1af97ed95a861b59a0ed3dc0 The patch is available at: https://github.com/peterdietz/DSpace/commit/0a87ba181c149bba1af97ed95a861b59a0ed3dc0.diff To see an example of this patch (iTunes Podcast) in a production environment see: DSpace Collection: https://kb.osu.edu/dspace/handle/1811/45183 RSS Feed: https://kb.osu.edu/dspace/feed/rss_2.0/1811/45183 Our feed has since been published to our University's iTunes U manager, and it is available in iTunes U: http://itunes.apple.com/us/itunes-u/writers-talk/id389543070 > RSS feeds to support richer features, such as iTunes Podcast or Media RSS > - > > Key: DS-528 > URL: https://jira.duraspace.org/browse/DS-528 > Project: DSpace > Issue Type: New Feature > Components: DSpace API >Reporter: Peter Dietz >Assignee: Peter Dietz > Attachments: chat transcript.txt, RSSwithitunes152.patch, > RSSwithitunes16trunk.patch > > > Feeds standardizing dissemination of media exists, and can enable a > collection's feed to support something such as Media RSS or iTunes podcast > RSS. > Included to get the discussion moving is a patch to add iTunes Podcast > support to RSS feeds. -- 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 -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Assigned: (DS-847) Items without title or author display incorrectly in browse lists
[ https://jira.duraspace.org/browse/DS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz reassigned DS-847: -- Assignee: Peter Dietz > Items without title or author display incorrectly in browse lists > - > > Key: DS-847 > URL: https://jira.duraspace.org/browse/DS-847 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Reporter: stuart yeates >Assignee: Peter Dietz > Attachments: First_Result_No_Author_Or_Title.png > > > We accidentally created an item without author or title. Fixing the problem > was challenging because all the browse indexes use the author and title for > the link text and web browsers don't allow users to easily browse to links > with empty link text. > When the skins are creating links, they thus need to be careful to ensure > that all links have some characters in them. I'm not sure whether > non-breaking space will work, but including a hyphen should. -- 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 -- 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks & Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-904) Non consistant naming of Creative Commons license bundle
[ https://jira.duraspace.org/browse/DS-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-904: --- Documentation Status: Not Required (was: Needed) Status: Open (was: Received) > Non consistant naming of Creative Commons license bundle > > > Key: DS-904 > URL: https://jira.duraspace.org/browse/DS-904 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0, 1.7.1 > Environment: xmlui >Reporter: Peter Dietz >Assignee: Peter Dietz > Fix For: 1.8.0 > > Attachments: DS-904-fix-xmlui-cclicense-bundle.patch > > > The creative commons license bundle is typically called CC-LICENSE, however, > XMLUI's Edit Item page for uploading bitstreams directly to an item allows > you to upload bitstreams to a bundle called CC_LICENSE. The bundle names are > different by an underscore. > By default Creative Commons is not used, but if it is used, then the > potential for this problem exists. In addition to just changing the value to > be the correct one (CC-LICENSE), we should also use a constant for the bundle > name of creative commons (and all other should-be constants). -- 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 -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-904) Non consistant naming of Creative Commons license bundle
[ https://jira.duraspace.org/browse/DS-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz resolved DS-904. Resolution: Fixed Committed to trunk. The correct name of the bundle is: CC-LICENSE > Non consistant naming of Creative Commons license bundle > > > Key: DS-904 > URL: https://jira.duraspace.org/browse/DS-904 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0, 1.7.1 > Environment: xmlui >Reporter: Peter Dietz >Assignee: Peter Dietz > Fix For: 1.8.0 > > Attachments: DS-904-fix-xmlui-cclicense-bundle.patch > > > The creative commons license bundle is typically called CC-LICENSE, however, > XMLUI's Edit Item page for uploading bitstreams directly to an item allows > you to upload bitstreams to a bundle called CC_LICENSE. The bundle names are > different by an underscore. > By default Creative Commons is not used, but if it is used, then the > potential for this problem exists. In addition to just changing the value to > be the correct one (CC-LICENSE), we should also use a constant for the bundle > name of creative commons (and all other should-be constants). -- 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 -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-984) Provide links to RSS Feeds
Provide links to RSS Feeds -- Key: DS-984 URL: https://jira.duraspace.org/browse/DS-984 Project: DSpace Issue Type: New Feature Components: XMLUI Reporter: Peter Dietz Assignee: Peter Dietz Fix For: 1.8.0 The RSS feeds in xmlui are added to the page metadata, but are not exposed by the UI. There should be links to view the RSS feed for the current area, when possible. Code to accomplish this has been passed along in the mailing lists a few times. https://gist.github.com/866640 -- 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 -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-528) RSS feeds to support richer features, such as iTunes Podcast or Media RSS
[ https://jira.duraspace.org/browse/DS-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21456#action_21456 ] Peter Dietz commented on DS-528: Added iTunes podcast support to trunk in time for 1.8 > RSS feeds to support richer features, such as iTunes Podcast or Media RSS > - > > Key: DS-528 > URL: https://jira.duraspace.org/browse/DS-528 > Project: DSpace > Issue Type: New Feature > Components: DSpace API >Reporter: Peter Dietz >Assignee: Peter Dietz > Attachments: chat transcript.txt, RSSwithitunes152.patch, > RSSwithitunes16trunk.patch > > > Feeds standardizing dissemination of media exists, and can enable a > collection's feed to support something such as Media RSS or iTunes podcast > RSS. > Included to get the discussion moving is a patch to add iTunes Podcast > support to RSS feeds. -- 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 -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1241) Statistics implementation in Elastic Search
Peter Dietz created DS-1241: --- Summary: Statistics implementation in Elastic Search Key: DS-1241 URL: https://jira.duraspace.org/browse/DS-1241 Project: DSpace Issue Type: New Feature Reporter: Peter Dietz Assignee: Peter Dietz Fix For: 3.0 Work at Ohio State University Libraries for the Knowledge Bank, has had us demanding more out of statistics. We have worked building a statistics dashboard in SOLR, but ran into performance issues. We have since started from the ground up (to a degree), and built an implementation of storing UsageEvent statistics into Elastic Search. I can't really speak about comparing SOLR to Elastic Search, but that we (OSU) prefers Elastic Search, and that this is our implementation that we'd like to contribute. This contribution will include the ElasticSearch UsageEvent listener, a standalone ElasticSearch client, and some modifications to XMLUI to view a statistics portal that has statistics from this solution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1241) Statistics implementation in Elastic Search
[ https://jira.duraspace.org/browse/DS-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-1241: Attachment: Screen Shot 2012-08-10 at 5.10.52 PM.png > Statistics implementation in Elastic Search > --- > > Key: DS-1241 > URL: https://jira.duraspace.org/browse/DS-1241 > Project: DSpace > Issue Type: New Feature >Reporter: Peter Dietz >Assignee: Peter Dietz > Fix For: 3.0 > > Attachments: Screen Shot 2012-08-10 at 5.10.52 PM.png > > > Work at Ohio State University Libraries for the Knowledge Bank, has had us > demanding more out of statistics. We have worked building a statistics > dashboard in SOLR, but ran into performance issues. We have since started > from the ground up (to a degree), and built an implementation of storing > UsageEvent statistics into Elastic Search. I can't really speak about > comparing SOLR to Elastic Search, but that we (OSU) prefers Elastic Search, > and that this is our implementation that we'd like to contribute. > This contribution will include the ElasticSearch UsageEvent listener, a > standalone ElasticSearch client, and some modifications to XMLUI to view a > statistics portal that has statistics from this solution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1241) Statistics implementation in Elastic Search
[ https://jira.duraspace.org/browse/DS-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25727#comment-25727 ] Peter Dietz commented on DS-1241: - Cleaned up implementation sitting in repository at: https://github.com/peterdietz/DSpace/commits/elastic-search-stats/ Will create pull request after building a tool to ease import of data from SOLR / dspace.log > Statistics implementation in Elastic Search > --- > > Key: DS-1241 > URL: https://jira.duraspace.org/browse/DS-1241 > Project: DSpace > Issue Type: New Feature >Reporter: Peter Dietz >Assignee: Peter Dietz > Fix For: 3.0 > > Attachments: Screen Shot 2012-08-10 at 5.10.52 PM.png > > > Work at Ohio State University Libraries for the Knowledge Bank, has had us > demanding more out of statistics. We have worked building a statistics > dashboard in SOLR, but ran into performance issues. We have since started > from the ground up (to a degree), and built an implementation of storing > UsageEvent statistics into Elastic Search. I can't really speak about > comparing SOLR to Elastic Search, but that we (OSU) prefers Elastic Search, > and that this is our implementation that we'd like to contribute. > This contribution will include the ElasticSearch UsageEvent listener, a > standalone ElasticSearch client, and some modifications to XMLUI to view a > statistics portal that has statistics from this solution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1241) Statistics implementation in Elastic Search
[ https://jira.duraspace.org/browse/DS-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25728#comment-25728 ] Peter Dietz commented on DS-1241: - once you've rebuilt, with this. The elastic-search stats is visible from path /stats i.e. http://localhost:8080/dspace/handle/123456789/1/stats > Statistics implementation in Elastic Search > --- > > Key: DS-1241 > URL: https://jira.duraspace.org/browse/DS-1241 > Project: DSpace > Issue Type: New Feature >Reporter: Peter Dietz >Assignee: Peter Dietz > Fix For: 3.0 > > Attachments: Screen Shot 2012-08-10 at 5.10.52 PM.png > > > Work at Ohio State University Libraries for the Knowledge Bank, has had us > demanding more out of statistics. We have worked building a statistics > dashboard in SOLR, but ran into performance issues. We have since started > from the ground up (to a degree), and built an implementation of storing > UsageEvent statistics into Elastic Search. I can't really speak about > comparing SOLR to Elastic Search, but that we (OSU) prefers Elastic Search, > and that this is our implementation that we'd like to contribute. > This contribution will include the ElasticSearch UsageEvent listener, a > standalone ElasticSearch client, and some modifications to XMLUI to view a > statistics portal that has statistics from this solution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-421) Setting solr.metadata.item.X property to an unqualified field generates exception in SolrLogger.post on item view and prevents Solr from logging the event
[ https://jira.duraspace.org/browse/DS-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25875#comment-25875 ] Peter Dietz commented on DS-421: While looking through SolrLogger, I've noticed that the code to support stuffing metadata into Solr stats is still possible. https://github.com/DSpace/DSpace/blob/deb732e3cb2f36325cfda8aa28989695bfbd4cab/dspace-stats/src/main/java/org/dspace/statistics/SolrLogger.java#L137 Even though its been removed from dspace.cfg. I would recommend removing all traces of metadataStorageInfo, IDEA says this would affect a number of files. > Setting solr.metadata.item.X property to an unqualified field generates > exception in SolrLogger.post on item view and prevents Solr from logging the > event > -- > > Key: DS-421 > URL: https://jira.duraspace.org/browse/DS-421 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.6.0 >Reporter: Scott Hanrath >Assignee: Mark Diggory > Fix For: 1.6.0 > > > Setting a solr.metadata.item.X property to an unqualified field (e.g., > dc.title rather then dc.title.alternative) generates an exception in > SolrLogger.post on item view. The ArrayIndexOutOfBoundsException appear to > prevent Solr from logging the event. > The stacktrace from the logs is: > java.lang.ArrayIndexOutOfBoundsException: 2 > at org.dspace.statistics.SolrLogger.post(SolrLogger.java:216) > at > org.dspace.statistics.SolrLoggerUsageEventListener.receiveEvent(SolrLoggerUsageEventListener.java:48) > at > org.dspace.services.events.SystemEventService.fireLocalEvent(SystemEventService.java:154) > at > org.dspace.services.events.SystemEventService.fireEvent(SystemEventService.java:97) > at > org.dspace.app.xmlui.cocoon.UsageLoggerAction.logDspaceObject(UsageLoggerAction.java:61) >[...] > This is similar to DS-419 in that a metadata field like 'schema.element' is > being split into an array and the methods is then trying to access > non-existent 3rd element of the array (i.e., array[2], representing the > qualifier) without checking the array length first. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-956) Skip from Item page to next Item in Browse results without having to return to Browse results page
[ https://jira.duraspace.org/browse/DS-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-956: --- Attachment: Screen Shot 2012-10-11 at 2.31.36 PM.png I've implemented a very basic form of this feature request, which does allow paging from one item to the next. I haven't taken into account any sort of state or scope (i.e. search results or browse-by-title). But it iterates through the collection. You can see the diff which accomplishes this on our OSU repository. (This won't apply to DSpace:DSpace, but to our local instance) https://github.com/osulibraries/DSpace/compare/osulibraries:osukb...osulibraries:item-paging > Skip from Item page to next Item in Browse results without having to return > to Browse results page > -- > > Key: DS-956 > URL: https://jira.duraspace.org/browse/DS-956 > Project: DSpace > Issue Type: New Feature > Components: JSPUI >Reporter: Sue Walker-Thornton >Priority: Major > Attachments: Screen Shot 2012-10-11 at 2.31.36 PM.png > > > We would like to see a new feature in DSpace where a User could "skip" from > the Item short (or long) listing to the next Item in either Browse or Search > results without having to return to the Browse or Search results page. Let's > say I do a search from the DSpace home page on "rocket". I get a list of all > Items in DSpace that contain the word rocket, either in the metadata or in a > filtered bitstream. Say I click on the first Item in the list and the Item > short-listing page is displayed. We would like to be able to review that > Item, then "skip" to the next Item that was returned in the Browse or Search > results, WITHOUT HAVING TO GO BACK TO THE BROWSE OR SEARCH RESULTS PAGE. > Optimally, I'd like to see an icon or button that says "Next Item" or > something like that. Once I've scrolled to the next item, then there should > be a "Previous Item" and a "Next Item" icon or button, if applicable. This > would be SOO cool! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1400) Elastic Search implementation of Statistics has no documentation around how to use, enable or disable.
[ https://jira.duraspace.org/browse/DS-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz resolved DS-1400. - Resolution: Fixed Documentation for this feature is available at: https://wiki.duraspace.org/display/DSDOC3x/Elastic+Search+Usage+Statistics > Elastic Search implementation of Statistics has no documentation around how > to use, enable or disable. > -- > > Key: DS-1400 > URL: https://jira.duraspace.org/browse/DS-1400 > Project: DSpace > Issue Type: Documentation > Components: Documentation, Statistics >Affects Versions: 3.0 >Reporter: Tim Donohue >Assignee: Peter Dietz > Fix For: 3.1 > > > The Elastic Search implementation of DSpace Statistics (DS-1241) has no > documentation. The code is available, but it is unclear how to do any of the > following: > * enable / disable it > * customize (if possible / necessary) > * use it in general -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1416) NPE when removing roles from Collection workflow steps
[
https://jira.duraspace.org/browse/DS-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Dietz updated DS-1416:
Status: Open (was: Received)
I can confirm this bug, it affects 1.8, and 3.0.
When using the "Original Workflow", leaving the new "XML Workflow" disabled,
this breaks. It looks like the code to processDeleteCollectionRole in
FlowContainerUtils is hard-coded to trigger the XML-Workflow code, as opposed
to the Original Workflow code.
> NPE when removing roles from Collection workflow steps
> --
>
> Key: DS-1416
> URL: https://jira.duraspace.org/browse/DS-1416
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API, XMLUI
>Affects Versions: 3.0
>Reporter: Ian Boston
>
> In the XMLUI
> If I edit a collection
> Add a role to a workflow step clicking create.
> Add a user to that role.
> save
> then delete the role from the workflow step.
> I get the following NPE:
> java.lang.NullPointerException
> at
> org.dspace.xmlworkflow.WorkflowUtils.deleteRoleGroup(WorkflowUtils.java:215)
> at
> org.dspace.app.xmlui.aspect.administrative.FlowContainerUtils.processDeleteCollectionRole(FlowContainerUtils.java:538)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:155)
> at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:243)
> at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3237)
> The method is:
> public static void deleteRoleGroup(Context context, Collection collection,
> String roleID) throws SQLException, IOException,
> WorkflowConfigurationException {
> Workflow workflow = WorkflowFactory.getWorkflow(collection);
> Role role = workflow.getRoles().get(roleID);
> Line: 215>>> NPE on roleif(role.getScope() ==
> Role.Scope.COLLECTION){
> CollectionRole ass = CollectionRole.find(context,
> collection.getID(), roleID);
> ass.delete();
> }
> }
> You could do
> if ( role != null && role.getScope() ...
> but role should not be null ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1416) NPE when removing roles from Collection workflow steps
[
https://jira.duraspace.org/browse/DS-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27359#comment-27359
]
Peter Dietz commented on DS-1416:
-
I've made a dummy collection on the Demo instance:
http://demo.dspace.org/xmlui/admin/collection?collectionID=51 to see this bug
in action, try to go to Assign Roles, and delete the Workflow Step.
Below, the code that hard-codes XML-Workflow.
{code}
else{
WorkflowUtils.deleteRoleGroup(context, collectionID, roleName);
}
// else if (ROLE_WF_STEP1.equals(roleName))
// {
// collection.setWorkflowGroup(1, null);
// }
// else if (ROLE_WF_STEP2.equals(roleName))
// {
// collection.setWorkflowGroup(2, null);
// }
// else if (ROLE_WF_STEP3.equals(roleName))
// {
// collection.setWorkflowGroup(3, null);
//
// }
{code}
Commit at:
https://github.com/DSpace/DSpace/commit/65f5786e9e13336122a71aa9f8ec51898901e541#L46R528
> NPE when removing roles from Collection workflow steps
> --
>
> Key: DS-1416
> URL: https://jira.duraspace.org/browse/DS-1416
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API, XMLUI
>Affects Versions: 3.0
>Reporter: Ian Boston
>
> In the XMLUI
> If I edit a collection
> Add a role to a workflow step clicking create.
> Add a user to that role.
> save
> then delete the role from the workflow step.
> I get the following NPE:
> java.lang.NullPointerException
> at
> org.dspace.xmlworkflow.WorkflowUtils.deleteRoleGroup(WorkflowUtils.java:215)
> at
> org.dspace.app.xmlui.aspect.administrative.FlowContainerUtils.processDeleteCollectionRole(FlowContainerUtils.java:538)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:155)
> at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:243)
> at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3237)
> The method is:
> public static void deleteRoleGroup(Context context, Collection collection,
> String roleID) throws SQLException, IOException,
> WorkflowConfigurationException {
> Workflow workflow = WorkflowFactory.getWorkflow(collection);
> Role role = workflow.getRoles().get(roleID);
> Line: 215>>> NPE on roleif(role.getScope() ==
> Role.Scope.COLLECTION){
> CollectionRole ass = CollectionRole.find(context,
> collection.getID(), roleID);
> ass.delete();
> }
> }
> You could do
> if ( role != null && role.getScope() ...
> but role should not be null ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1416) NPE when removing roles from Collection workflow steps
[
https://jira.duraspace.org/browse/DS-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27360#comment-27360
]
Peter Dietz commented on DS-1416:
-
Not as clean as a pull-request, but I've corrected this for my local repository
with:
https://github.com/osulibraries/DSpace/commit/d813c11dd3329dc862d5f2b6840551565638fd5c
I'll work on a PR when I get the time.
> NPE when removing roles from Collection workflow steps
> --
>
> Key: DS-1416
> URL: https://jira.duraspace.org/browse/DS-1416
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API, XMLUI
>Affects Versions: 3.0
>Reporter: Ian Boston
>
> In the XMLUI
> If I edit a collection
> Add a role to a workflow step clicking create.
> Add a user to that role.
> save
> then delete the role from the workflow step.
> I get the following NPE:
> java.lang.NullPointerException
> at
> org.dspace.xmlworkflow.WorkflowUtils.deleteRoleGroup(WorkflowUtils.java:215)
> at
> org.dspace.app.xmlui.aspect.administrative.FlowContainerUtils.processDeleteCollectionRole(FlowContainerUtils.java:538)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:155)
> at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:243)
> at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3237)
> The method is:
> public static void deleteRoleGroup(Context context, Collection collection,
> String roleID) throws SQLException, IOException,
> WorkflowConfigurationException {
> Workflow workflow = WorkflowFactory.getWorkflow(collection);
> Role role = workflow.getRoles().get(roleID);
> Line: 215>>> NPE on roleif(role.getScope() ==
> Role.Scope.COLLECTION){
> CollectionRole ass = CollectionRole.find(context,
> collection.getID(), roleID);
> ass.delete();
> }
> }
> You could do
> if ( role != null && role.getScope() ...
> but role should not be null ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-358) Discuss implications of HTML5 for DSpace
[
https://jira.duraspace.org/browse/DS-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27961#comment-27961
]
Peter Dietz commented on DS-358:
A DSpace JIRA Review on April 17th, 2013 had us add some notes to this.
I've noticed that I've had trouble getting cocoon to spit out the proper HTML5
doctype.
{code}
{code}
DSpace/XMLUI is currently spitting out something like:
{code}
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
http://www.w3.org/1999/xhtml"; class="no-js">
{code}
You are somewhat dependent on cocoon for serializing to HTML. What we've got is
an HTML4 serializer, and I don't think there is any such thing as a HTML5
serializer for cocoon 2.
More cocoon discussion can be found at:
http://mail-archives.apache.org/mod_mbox/cocoon-dev/201201.mbox/%3c78b923726e7d59429936580cf127e943a1f4e61...@eu1rdcrdc1wx032.exi.nxp.com%3E
Non-the-less, Ohio State's DSpace instance the Knowledge Bank http://kb.osu.edu
has customized the existing HTMLserializer to give out a more trimmed doctype.
In dspace-xmlui/dspace-xmlui-api/src/main/webapp/sitemap.xmap, OSU has
customized this to be:
{code}
UTF-8
yes
{code}
And the doctype that we spit out is:
{code}
http://www.w3.org/1999/xhtml";>
{code}
Which should be fair enough. We haven't completely re-done the XMLUI layout to
be written in HTML5 by scratch, but since OSU KB is using twitter bootstrap for
much of the UI, which probably makes use of HTML5 elements, we are getting
there.
(Apologies if the formatting of this comment is butchered, I'm used to JIRA's
code macro for formatting code.)
> Discuss implications of HTML5 for DSpace
>
>
> Key: DS-358
> URL: https://jira.duraspace.org/browse/DS-358
> Project: DSpace
> Issue Type: Task
> Components: JSPUI, XMLUI
>Reporter: Stuart Lewis
>
> The possible implications of HTML5 on DSpace need to be discussed. Please use
> this JIRA ticket to add comments and discussion.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-635) Rendering MathML code in abstracts
[ https://jira.duraspace.org/browse/DS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz reassigned DS-635: -- Assignee: Peter Dietz > Rendering MathML code in abstracts > -- > > Key: DS-635 > URL: https://jira.duraspace.org/browse/DS-635 > Project: DSpace > Issue Type: Improvement > Components: JSPUI, XMLUI > Environment: Ubuntu Server 9.04 >Reporter: George Simeonov >Assignee: Peter Dietz >Priority: Major > > I tried to include ( MathML / HTML ) code in descriptions (abstracts) JSPUI, > but in browsers is displayed only plain text. MathML is natively supported by > Firefox and Opera browser. I have a lot of articles with complex math > formulas in the abstracts. I think that MathML is more important than HTML5 > for example. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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
[Dspace-devel] [DuraSpace JIRA] (DS-635) Rendering MathML code in abstracts
[
https://jira.duraspace.org/browse/DS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28136#comment-28136
]
Peter Dietz commented on DS-635:
Some of Items in our repository have scientific formulas in the metadata. We
have been exploring how to render this. For instance in the metadata, it looks
like:
The positions of about 5000 spectral lines of $^{12}C_{16}O_{2}$ have been
accurately measured with a multispectrum nonlinear least squares fitting
$technique^{a}$.
The dollar-signs on the edge of a formula get rendered. Our local solution is
to render Item titles, Item Display simple, but not Item Display full (and
instead show the unrendered source).
I'm currently looking at what to do about Metadata that contains dollar signs,
but isn't formulas. i.e. FDA approval of $0.03 pills vs $1.23 pills. In which
case the dollar signs could accidentally get picked up and interpreted.
> Rendering MathML code in abstracts
> --
>
> Key: DS-635
> URL: https://jira.duraspace.org/browse/DS-635
> Project: DSpace
> Issue Type: Improvement
> Components: JSPUI, XMLUI
> Environment: Ubuntu Server 9.04
>Reporter: George Simeonov
>Assignee: Peter Dietz
>Priority: Major
>
> I tried to include ( MathML / HTML ) code in descriptions (abstracts) JSPUI,
> but in browsers is displayed only plain text. MathML is natively supported by
> Firefox and Opera browser. I have a lot of articles with complex math
> formulas in the abstracts. I think that MathML is more important than HTML5
> for example.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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
[Dspace-devel] [DuraSpace JIRA] (DS-790) SOLR - Spider detection to match on hostname or useragent
[ https://jira.duraspace.org/browse/DS-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28426#comment-28426 ] Peter Dietz commented on DS-790: Hey [~bram], are you aware of any such lists that detect users based on DNS/hostname? I'm thinking that UserAgent is a great way, and I'm working on adding support for this (for ElasticSearch stats). But I would need some patterns to match against for hostnames. I guess IP addresses would work too, but less preferred. > SOLR - Spider detection to match on hostname or useragent > - > > Key: DS-790 > URL: https://jira.duraspace.org/browse/DS-790 > Project: DSpace > Issue Type: Improvement > Components: Solr >Affects Versions: 1.6.0, 1.6.1, 1.6.2, 1.7.0 > Environment: solr >Reporter: Peter Dietz >Assignee: Mark H. Wood > Labels: has-pull-request > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Spiders are currently detected by matching their IP address to one listed in > the /dspace/config/spiders/ip-list-X.txt, however as spiders change IP > addresses, or the ip-list is unmaintained, then many spiders can slip > through, however they will usually keep their user agent or hostname intact. > I've noticed a sore point in my solr data, where msnbot is completely > unfiltered by solr. They have an additional ip list: > http://www.iplists.com/nw/msn.txt however it is very old, and with additional > bingbots on the horizon, it would be easier to detect, and filter them out of > the logs by user-agent, then to maintain all of the IP address ranges. The > code to do this in SOLR is unimplemented, and this ticket is a place holder > to encourage this work to filter out based on user agent / dns-hostname to be > finished. > To see all of the hits from msnbot that are unfiltered, look at: > http://localhost:8080/solr/statistics/select?q=dns:msnbot*&facet=true&facet.field=dns&facet.mincount=1&facet.limit=5000 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1657) Adopt/Create an official DSpace REST API
Peter Dietz commented on DS-1657 Adopt/Create an official DSpace REST API I have submitted a Pull Request for a JERSEY based implementation at: https://github.com/DSpace/DSpace/pull/323 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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=60134071&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1475) Improvement of Collection Dropdown
Peter Dietz commented on DS-1475 Improvement of Collection Dropdown Not sure where to leave a review.. But I'm thinking that instead of having dividers within the text, you have the UI render it more meaningfully, such as with HTML optgroup. http://www.w3schools.com/tags/tag_optgroup.asp (My understanding of) PR#324's way: - German Cars - Audi - German Cars - Mercedes - Swedish Cars - Saab - Swedish Cars - Volvo OPTGROUP way: German Cars - Audi - Mercedes Swedish Cars - Saab - Volvo (In the example, country is community, and manufacturer is the collection). (This might be a new Jira ticket), but lastly, I have made some performance improvements for loading that list, the gist of which can be seen at: https://github.com/osulibraries/DSpace/commit/61039c5572f29283127bc6e4fa1d1f729440d63d#diff-1 Current implementation is to get all collections in the site, and then one-by-one compare the current user to see if they have submit powers. My algorithm, says, get all permissions for submit that the user has, and then add those collections to a list. If you have *A LOT* of collections like my site 2000 collections, the speed up takes you from 30 second load to 1 second load. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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=60134071&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1475) Improvement of Collection Dropdown
Peter Dietz assigned DS-1475 to Peter Dietz Improvement of Collection Dropdown Change By: Peter Dietz (08/Oct/13 12:05 PM) Assignee: Ivan Masár Peter Dietz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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=60134071&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-552) Servlet to deliver repository size statistics
Title: Message Title Peter Dietz commented on an issue Re: Servlet to deliver repository size statistics I've implemented this on Ohio State's instance. I've divided the bytes by (1024*1024*1024) to work around the too-big for int problem. Our code is at: https://github.com/osulibraries/DSpace/blob/osukb/dspace-xmlui/dspace-xmlui-api/src/main/java/org/dspace/app/xmlui/aspect/dashboard/ContentStatistics.java Example use in production: https://kb.osu.edu/dspace/content-statistics (Its slow loading). 189 1475 54188 118424 111867 86495 8907 mhwood and I were discussing this in #dspace, and we determined that stuffing this in REST might not be a bad idea, and we found this advice: https://blog.apigee.com/detail/restful_api_design_what_about_counts -- Say, you want a count of all of some resource (scoped based on whatever the requester has access to). -- /dogs/count -- In this way, you think about "count" as a reserved word. Thus, this might fit into REST at endpoints: /communities/count, /collections/count, /items/count, /bitstreams/count, /bitstreams/size?unit=GB, /bitstreams/count?mimetype=image*, /bitstreams/size?unit=GB&mimetype=image* The DB logic couldn't reside in rest though, it would have to move to dspace-api. Add Comment DSpace / DS-552 Servlet to deliver repository size statistics A tiny servlet to return counts of bitstreams, items, collections, and communities, and the amount of storage occupied. The attached patch also maps it into both JSPUI and XMLUI at /content-statistics. The returned "page" is an XML document. For now, see the package.html changes in the patch. I'll update the end-user documentation presently. We u...
[Dspace-devel] [DuraSpace JIRA] (DS-1719) JERSEY based REST does not report statistics
Title: Message Title Peter Dietz closed an issue as Fixed Anja added the improvements, and I merged it in. https://github.com/DSpace/DSpace/commit/eb1902ae7faaa23a7d1eb5cca6d836dd1a250f8c DSpace / DS-1719 JERSEY based REST does not report statistics Change By: Peter Dietz Resolution: Fixed Status: Accepted Closed Add Comment This message was sent by Atlassian JIRA (v6.1.1#6155-sha1:7188aee) -- 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=65839951&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1748) Add a config option to "dspace.cfg" to enable the "Elastic Search" event listener, similar to enabling the "Discovery" listener.
Title: Message Title Peter Dietz commented on an issue Re: Add a config option to "dspace.cfg" to enable the "Elastic Search" event listener, similar to enabling the "Discovery" listener. Hi Hilton, I think that due to the way Spring works, each web-app has to define which Event Listeners are active. Thus, the documentation states that to enable Elastic Search Usage-Event-Listener, uncomment the ElasticSearch bean in dspace-xmlui/.../applicationContext.xml I'm not familiar with Spring-Magic enough to somehow globally enable an event listener. Add Comment DSpace / DS-1748 Add a config option to "dspace.cfg" to enable the "Elastic Search" event listener, similar to enabling the "Discovery" listener. Add a config option to "dspace.cfg" to enable the "Elastic Search" event listener, similar to enabling the "Discovery" listener. This message was sent by Atlassian JIRA (v6.1.1#6155-sha1:7188aee) -- 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 secu
[Dspace-devel] [DuraSpace JIRA] (DS-1731) Add config option to "Elastic Search" to define which group has statistics viewing privleges
Title: Message Title Peter Dietz commented on an issue Re: Add config option to "Elastic Search" to define which group has statistics viewing privleges Hi Hilton, Not being able to configure the group-name for the limited-access to viewing ES statistics (i.e. statistics_viewer) was an oversight of mine. https://github.com/DSpace/DSpace/blob/c43c224eda972dc8d356ef844dcaa9ebf4c38653/dspace-xmlui/src/main/java/org/dspace/app/xmlui/aspect/statisticsElasticSearch/SpecifiedGroupAuthenticatedSelector.java#L28 private String SPECIFIED_GROUP = "statistics_viewer"; Add Comment DSpace / DS-1731 Add config option to "Elastic Search" to define which group has statistics viewing privleges Add an option in "Elastic Search" config to define which group has statistics viewing privileges. This message was sent by Atlassian JIRA (v6.1.1#6155-sha1:7188aee) -- 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.
[Dspace-devel] [DuraSpace JIRA] (DS-1657) Adopt/Create an official DSpace REST API
Title: Message Title Peter Dietz commented on an issue Re: Adopt/Create an official DSpace REST API For the record. DS-1696 (JERSEY), has received positive approval by committers, and the 4.0 Release Team, and was merged in. Documentation for the DSpace 4.0 REST API can be found at: https://wiki.duraspace.org/display/DSDOC4x/REST+API There is still some work to do to improve the JERSEY API overall, but it brings a good foundation, and meets the requirements laid out in this ticket (READ-ONLY access to public (non-restricted) information in your DSpace instance. Add Comment DSpace / DS-1657 Adopt/Create an official DSpace REST API As has been discussed many times, DSpace needs a REST API. Based on discussions in the Developer Meeting on Sept 18, 2013 (http://irclogs.duraspace.org/index.php?date=2013-09-18 ), the DSpace Committers have come up with a loose set of requirements around what we need out of a REST API. Requirements for REST API inclusion: 1. A read-only API is acc... This message was sent by Atlassian JIRA (v6.1.1#6155-sha1:7188aee) ---
[Dspace-devel] [DuraSpace JIRA] (DS-1696) DSpace REST API built in JERSEY
Title: Message Title Peter Dietz commented on an issue Re: DSpace REST API built in JERSEY Documentation for DSpace 4.0 REST API can be found at: https://wiki.duraspace.org/display/DSDOC4x/REST+API Add Comment DSpace / DS-1696 DSpace REST API built in JERSEY Pull request https://github.com/DSpace/DSpace/pull/323 This message was sent by Atlassian JIRA (v6.1.1#6155-sha1:7188aee) -- 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=65839951&iu=/4140/ostg.clktrk___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1884) REST API output for text/html
Title: Message Title Peter Dietz commented on an issue Re: REST API output for text/html Hi [~helix84], the html display was added at one point, and they currently are mostly useless. Instead of fixing them to make them more useful, I would be in favor of removing output serialization to HTML, its unnecessary, you would otherwise get json or xml, depending on your browsers preferred accept header. If you want to make HTML from the API, it would be better to use a client application, where you can put in your own business logic. One issue with just adding stylesheets is that we'll eventually support authN/authZ in the API, which means the client will need to send secrets in the call, which the stylesheets aren't going to help with. Add Comment DSpace / DS-1884 REST API output for text/html REST API currently responds to requests for text/html, application/xml and application/json. The text/html output: * is very simple, does not correspond to any formal HTML standard * is not created systematically, only by concatenating strings * doesn't contain all the information returned by the other types, therefore it's nearly useless * is the onl... This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d)
[Dspace-devel] [DuraSpace JIRA] (DS-1978) "Private Items" are misnamed, as permissions/privacy is not really changed
Title: Message Title Peter Dietz commented on an issue Re: "Private Items" are misnamed, as permissions/privacy is not really changed org.dspace.content.Item.isDiscoverable is the relevant attribute for determining if these Items are to be shown in Item Lists or not. Not that we should have YouTube govern how we proceed with the naming of features in our repository, I imagine that they have gone through plenty of discussion, and settled upon three classifications: - Public (anyone can search for an view) - Unlisted (only those with the link can view) - Private (can only be seen by you and the users you select) Therefore, I'd be happy to call this feature "Unlisted" Items. When I hear the word discoverable, I think it has something to do with a faceted search and browse interface... I'm currently working on making an ItemService method for determining if an Item is able to be shown in an Item list for a user. It has to check for READ permission, and if isDiscoverable=true. The method name in my draft is: isItemListedForUser(context, item), already I have this ready and tested for the REST API, and it should be suitable for the other affected components of DSpace that have to get fixed for unlisted/"private". Add Comment DSpace / DS-1978 "Private Items" are misnamed, as permissions/privacy is not really changed "Private" items are misnamed in DSpace. When you make an item private, it does not change the privacy settings (permissions). Instead, it's really just changing its discoverability settings (ability to find it via Browse/Search). See the definition at: https://wiki.duraspace.org/display/DSDOC4x/DSpace+Item+State+Definitions Private items should li...
[Dspace-devel] [DuraSpace JIRA] (DS-1986) REST API holds on to context for too long, should use DB pool
Title: Message Title Peter Dietz created an issue DSpace / DS-1986 REST API holds on to context for too long, should use DB pool Issue Type: Bug Affects Versions: 4.1, 4.0 Assignee: Peter Dietz Components: REST API Created: 27/Apr/14 4:07 AM Priority: Minor Reporter: Peter Dietz REST API (Jersey), grabs a context, and never frees/returns/releases it. I don't know exactly what is going on, but it causes the REST API to not be able to reflect real-time updates to content. To repeat. Load a DSpace-REST result for some endpoint. Edit the title/name of the first object returned in that result. Reload the REST endpoint. For me, the REST response didn't have the updated title/name. Since the typical use-case of DSpace is content that rarely/never changes, this isn't a big deal, but it needs to be resolved. I believe this bug got in during the performance stress-testing process, where after hitting DSpace REST with millions of requests to Communities, Collections, Items, Bitstream over the span of an hour, I had added changes to help REST spend less time dealing with database connections, and instead keep a connection. The better route would be to grab a database connection from the pool, and return the connection back to the pool once the request is complete. I think I/we need to take a look at database connection pool best practices.
[Dspace-devel] [DuraSpace JIRA] (DS-1986) REST API holds on to context for too long, should use DB pool
Title: Message Title Peter Dietz commented on an issue Re: REST API holds on to context for too long, should use DB pool Fixing the unlisted/"private item" bug for REST, helped me to find this context / db connection bug in REST. Add Comment DSpace / DS-1986 REST API holds on to context for too long, should use DB pool REST API (Jersey), grabs a context, and never frees/returns/releases it. I don't know exactly what is going on, but it causes the REST API to not be able to reflect real-time updates to content. To repeat. Load a DSpace-REST result for some endpoint. Edit the title/name of the first object returned in that result. Reload the REST endpoint. For me, the... This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d) -- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform___ Dspace-devel mailing list Ds
[Dspace-devel] [DuraSpace JIRA] (DS-1976) "Private" items appear in REST API under their parent collection
Title: Message Title Peter Dietz commented on an issue Re: "Private" items appear in REST API under their parent collection Confirmed, the REST API has not respected the unlisted Item flag (isDiscoverable). I actually wasn't aware of the unlisted/"private" Item feature until just recently. I'm working on the fix for this for the REST API, and along the way I've made an org.dspace.content.service.ItemService method isItemListedForUser, that can be used to do the business logic of the check. Add Comment DSpace / DS-1976 "Private" items appear in REST API under their parent collection If you mark an item as "private" in the Submission UI or the Admin UI, it is still visible in the browse functions of the REST API. By definition, a "private" item should be hidden from all browse/search interfaces (including REST API). Private items are still potentially accessible via direct URL, but should not be discoverable through REST API, excep... This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d) -- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet
[Dspace-devel] [DuraSpace JIRA] (DS-1976) "Private" items appear in REST API under their parent collection
Title: Message Title Peter Dietz updated an issue DSpace / DS-1976 "Private" items appear in REST API under their parent collection Change By: Peter Dietz Assignee: Peter Dietz Status: Received Accepted Add Comment This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d) -- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1976) "Private" items appear in REST API under their parent collection
Title: Message Title Peter Dietz updated an issue DSpace / DS-1976 "Private" items appear in REST API under their parent collection Change By: Peter Dietz Labels: has-pull-request Add Comment This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d) -- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1976) "Private" items appear in REST API under their parent collection
Title: Message Title Peter Dietz commented on an issue Re: "Private" items appear in REST API under their parent collection Has PR: https://github.com/DSpace/DSpace/pull/527 Add Comment DSpace / DS-1976 "Private" items appear in REST API under their parent collection If you mark an item as "private" in the Submission UI or the Admin UI, it is still visible in the browse functions of the REST API. By definition, a "private" item should be hidden from all browse/search interfaces (including REST API). Private items are still potentially accessible via direct URL, but should not be discoverable through REST API, excep... This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d) -- Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourc
[Dspace-devel] [DuraSpace JIRA] (DS-1945) Allow override so helpdesk can receive all Request Copy emails instead of submitter
Title: Message Title Peter Dietz commented on an issue Re: Allow override so helpdesk can receive all Request Copy emails instead of submitter I have played off of [~ottenhoffs]'s Pull Request, and made it use Spring DI for the HelpdeskStrategy. I then cleaned up the UI's to use the DI instead. PR: https://github.com/DSpace/DSpace/pull/530 Add Comment DSpace / DS-1945 Allow override so helpdesk can receive all Request Copy emails instead of submitter Some institutions want the DSpace admininistrator or DSpace helpdesk to receive all Request Copy emails instead of the emails going to the original submitter. The Request copy has two config options right now: request.item.type = all mail.helpdesk = dsp...@myu.eduThis pull request will add a new config option to allow the override. This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d) -- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Not
[Dspace-devel] [DuraSpace JIRA] (DS-1986) REST API holds on to context for too long, should use DB pool
Title: Message Title Peter Dietz commented on an issue Re: REST API holds on to context for too long, should use DB pool So I have solved this by removing the static portion, however I can't commit it because it causes severe performance issues, ie 90% error on jmeter due to db pool/connection mismanagement. I'll sadly stick with stale data for the time being, until I can address db pool performance. Add Comment DSpace / DS-1986 REST API holds on to context for too long, should use DB pool REST API (Jersey), grabs a context, and never frees/returns/releases it. I don't know exactly what is going on, but it causes the REST API to not be able to reflect real-time updates to content. To repeat. Load a DSpace-REST result for some endpoint. Edit the title/name of the first object returned in that result. Reload the REST endpoint. For me, the... This message was sent by Atlassian JIRA (v6.1.7#6163-sha1:94d557d) -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert t
[Dspace-devel] [DuraSpace JIRA] (DS-740) Allow media filter to set non-default permissions on derivative bitstreams
Title: Message Title Peter Dietz commented on DS-740 Re: Allow media filter to set non-default permissions on derivative bitstreams I have made a Pull Request to implement this behavior. https://github.com/DSpace/DSpace/pull/543 Basically, I add a config where you whitelist the specific MediaFilter names that you want to make public content. Not listed, inherit parent's policy (i.e. restricted), if you are listed, then get public read. Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) -- Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-740) Allow media filter to set non-default permissions on derivative bitstreams
Title: Message Title Peter Dietz assigned an issue to Peter Dietz DSpace / DS-740 Allow media filter to set non-default permissions on derivative bitstreams Change By: Peter Dietz Assignee: Peter Dietz Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) -- Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-740) Allow media filter to set non-default permissions on derivative bitstreams
Title: Message Title Peter Dietz updated an issue DSpace / DS-740 Allow media filter to set non-default permissions on derivative bitstreams Change By: Peter Dietz Status: Volunteer Needed Accepted Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) -- Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1215) Display a default thumbnail if the user does not have permissions to view instead of 301 redirecting the image to a login screen
Title: Message Title Peter Dietz commented on DS-1215 Re: Display a default thumbnail if the user does not have permissions to view instead of 301 redirecting the image to a login screen DS-740 can generate a thumbnail of restricted content that is publicly available, which solves half of the problem. The unsolved half would be if the site chose not to make public thumbnails of restricted content. Then we would have to not attempt to show the restricted thumbnail in XMLUI. Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) -- Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1986) REST API holds on to context for too long, should use DB pool
Title: Message Title Peter Dietz commented on DS-1986 Re: REST API holds on to context for too long, should use DB pool Adding a Pull-Request to fix the context with REST. https://github.com/DSpace/DSpace/pull/561 The solution: Close the context in the finally after each request, and get a new context in each request. Cheers to [~rrodgers] for this tip during OR2014. Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1986) REST API holds on to context for too long, should use DB pool
Title: Message Title Peter Dietz updated an issue DSpace / DS-1986 REST API holds on to context for too long, should use DB pool Change By: Peter Dietz Labels: has-pull-request Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1986) REST API holds on to context for too long, should use DB pool
Title: Message Title Peter Dietz updated an issue DSpace / DS-1986 REST API holds on to context for too long, should use DB pool Change By: Peter Dietz Fix Version/s: 4.2 Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-2052) Mirage 2 Responsive theme for the XMLUI
Title: Message Title Peter Dietz commented on DS-2052 Re: Mirage 2 Responsive theme for the XMLUI I was thinking the cleanest/neatest approach to this would be for it to live in dspace-xmlui/src/main/webapps/themes/mirage2, where all of the other themes live. Instead of DSpace/maven managing all of the dependencies for this theme (bower/sass/etc), it becomes the end-developer to have all of that on their machine. Also, I can see the source and compiled version of this theme living together. i.e. Have mirage2/scripts/(file1.scss, file2.scss, file3.scss) all get compiled to mirage2/scripts/_styles.css, and you version control all of them. With your compiled version of mirage2 living in dspace-xmlui/src/main/webapps/themes/mirage2, the existing deploy process will continue to work fine. Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) -- 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
[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] Resolved: (DS-192) Bitstreams should be returned ordered
[ https://jira.duraspace.org/browse/DS-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz resolved DS-192. Resolution: Fixed > Bitstreams should be returned ordered > - > > Key: DS-192 > URL: https://jira.duraspace.org/browse/DS-192 > Project: DSpace > Issue Type: Improvement > Components: DSpace API >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0 >Reporter: Flávio Botelho >Assignee: Peter Dietz > Fix For: 1.7.0 > > Attachments: DS-192-configurable.patch, DS-192v2.patch, > ordering_bitstreams.patch > > > There exists a sequence_id for bitstreams, but it is not being used to return > the bitstreams ordered. > Important for items with lots of bitstreams, usually you want ensure some > order to them. > The patch goes with DESC ordering because it seemed to fit more what ordering > would usually happen in practice, but maybe should be changed to ASC; -- 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 -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-192) Bitstreams should be returned ordered
[ https://jira.duraspace.org/browse/DS-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-192: --- Documentation Status: In Attachment(s) Implemented and commit to trunk in a basic way that sets default value of sequence_id ASC as the default sorting of bitstreams. One who wishes to see a more feature rich way that has a display_index modifiable from the UI can propose a patch with functionality, and we can see about adding the database field. I didn't feel it was worth adding an unused db field, when there is no advanced implementation ready. > Bitstreams should be returned ordered > - > > Key: DS-192 > URL: https://jira.duraspace.org/browse/DS-192 > Project: DSpace > Issue Type: Improvement > Components: DSpace API >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0 >Reporter: Flávio Botelho >Assignee: Peter Dietz > Fix For: 1.7.0 > > Attachments: DS-192-configurable.patch, DS-192v2.patch, > ordering_bitstreams.patch > > > There exists a sequence_id for bitstreams, but it is not being used to return > the bitstreams ordered. > Important for items with lots of bitstreams, usually you want ensure some > order to them. > The patch goes with DESC ordering because it seemed to fit more what ordering > would usually happen in practice, but maybe should be changed to ASC; -- 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 -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Issue Comment Edited: (DS-192) Bitstreams should be returned ordered
[ https://jira.duraspace.org/browse/DS-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864#action_17864 ] Peter Dietz edited comment on DS-192 at 10/22/10 11:19 PM: --- Implemented and commit to trunk in a basic way that sets default value of sequence_id ASC as the default sorting of bitstreams. One who wishes to see a more feature rich way that has a display_index modifiable from the UI can propose a patch with functionality, and we can see about adding the database field. I didn't feel it was worth adding an unused db field, when there is no advanced implementation ready. [EDIT]: Also, the UI would need to not alter the sorting for this to be visible. I removed xmlui's title sorting, and custom themes may not take that into account. So both jspui and xmlui are on par out-of-the-box with regard to this feature. was (Author: peterdietz): Implemented and commit to trunk in a basic way that sets default value of sequence_id ASC as the default sorting of bitstreams. One who wishes to see a more feature rich way that has a display_index modifiable from the UI can propose a patch with functionality, and we can see about adding the database field. I didn't feel it was worth adding an unused db field, when there is no advanced implementation ready. > Bitstreams should be returned ordered > - > > Key: DS-192 > URL: https://jira.duraspace.org/browse/DS-192 > Project: DSpace > Issue Type: Improvement > Components: DSpace API >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0 >Reporter: Flávio Botelho >Assignee: Peter Dietz > Fix For: 1.7.0 > > Attachments: DS-192-configurable.patch, DS-192v2.patch, > ordering_bitstreams.patch > > > There exists a sequence_id for bitstreams, but it is not being used to return > the bitstreams ordered. > Important for items with lots of bitstreams, usually you want ensure some > order to them. > The patch goes with DESC ordering because it seemed to fit more what ordering > would usually happen in practice, but maybe should be changed to ASC; -- 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 -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Reopened: (DS-615) Ability to perform maintenance on SOLR with solr.optimize
[ https://jira.duraspace.org/browse/DS-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz reopened DS-615: Discovery adds another core to solr, search, which I don't believe gets optimized when the statistics optimize is called. This should be available as an argument for update-discovery-index -o, and would need to be added to IndexClient, and SolrServiceImpl. I recommend adding this performance fix in to 1.7, especially if instances are going to use discovery. > Ability to perform maintenance on SOLR with solr.optimize > - > > Key: DS-615 > URL: https://jira.duraspace.org/browse/DS-615 > Project: DSpace > Issue Type: Improvement > Components: Solr > Environment: solr >Reporter: Peter Dietz >Assignee: Peter Dietz > Fix For: 1.7.0 > > Attachments: solr-optimize.patch, SolrOptimizeAndAutoCommit.patch > > > By adding all historical log data to a SOLR index, as well as the constant > addition of new records, it might be good for the efficient performance of a > SOLR index to periodically run solr.optimize. > Therefore I've created a patch which allows you to run solr.optimize on your > solr instance from the command line. This could allow you to add a cron task > that runs this periodic maintenance. It also spits out the amount of time > taken to run the optimize task. > Once you patch your instance. You can execute this with > /dspace/bin/dspace stats-util --optimize > or > /dspace/bin/dspace stats-util -o > Output looks like: > SOLR Optimize -- Process Started:1277486321673 > SOLR Optimize -- Process Finished:1277486321738 > SOLR Optimize -- Total time taken:65 (ms). > It would be useful to profile the amount of time taken for solr operations > add/update/query before running this optimize task, and then afterwards. -- 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 -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-396) Provide metatags used by Google Scholar for enhanced indexing
[ https://jira.duraspace.org/browse/DS-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-396: --- Attachment: google-scholar-impl-quickndirty.patch Added a simple patch which provides for basic implementation of the required changes. It will display a citation_pdf_url in the case where there is only one public content bitstream and its mimetype is PDF. We should have something committed to improve the vast majority of instances in Scholar for 1.7 (This is not the work that MIT has been working on, but a quick and dirty implementation to move forward on this). > Provide metatags used by Google Scholar for enhanced indexing > - > > Key: DS-396 > URL: https://jira.duraspace.org/browse/DS-396 > Project: DSpace > Issue Type: New Feature >Reporter: Sarah Shreeves >Assignee: Sands Fish >Priority: Major > Fix For: 1.7.0 > > Attachments: google-scholar-impl-quickndirty.patch > > > In August 2009 I posted a query to the DSpace general list about whether or > not anyone else had seen strange indexing of items in DSpace (see > http://mailman.mit.edu/pipermail/dspace-general/2009-August/002996.html) and > MacKenzie Smith posted a follow up that stated she had seen the same things > (http://mailman.mit.edu/pipermail/dspace-general/2009-August/002998.html). > MacKenzie followed up with Anurag Acharya at Google Scholar to inquire about > this and he indicated that better support for the Google metatags schema > would help mitigate this problem. It looks like the metatags are (though we'd > want to confirm this with the Google Scholar team). > > > > > > > > > > content="http://www.publishername.org/10/1/1.pdf";> > content="http://www.publishername.org/cgi/content/abstract/10/1/1";> > content="http://www.publishername.org/cgi/content/full/10/1/1";> > > > > > > I realize that supporting this level of granularity puts pressure on how we > structure metadata but I believe as a repository manager that it's critical > that we get this kind of support for Google Scholar into DSpace out of the > box - and hopefully will help minimize the problems that IDEALS has seen. -- 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 -- Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-615) Ability to perform maintenance on SOLR with solr.optimize
[ https://jira.duraspace.org/browse/DS-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-615: --- Attachment: screenshot_079.png Attaching a quick-and-dirty solution for performing solr.optimize on the search/discovery core. Not recommending this method as the way we do it, but it gets the job done. Also, I'd like to note that the initial update-discovery-index should switch to using autocommit, I've done this to my local install, and got a 10x speedup. So instead of needing a few hours, the indexing could be done in about 20 minutes. Other things like updating an existing record, or deleting a record should still use a hard solr.commit. > Ability to perform maintenance on SOLR with solr.optimize > - > > Key: DS-615 > URL: https://jira.duraspace.org/browse/DS-615 > Project: DSpace > Issue Type: Improvement > Components: Solr > Environment: solr >Reporter: Peter Dietz >Assignee: Ben Bosman > Fix For: 1.7.0 > > Attachments: screenshot_079.png, solr-optimize.patch, > SolrOptimizeAndAutoCommit.patch > > > By adding all historical log data to a SOLR index, as well as the constant > addition of new records, it might be good for the efficient performance of a > SOLR index to periodically run solr.optimize. > Therefore I've created a patch which allows you to run solr.optimize on your > solr instance from the command line. This could allow you to add a cron task > that runs this periodic maintenance. It also spits out the amount of time > taken to run the optimize task. > Once you patch your instance. You can execute this with > /dspace/bin/dspace stats-util --optimize > or > /dspace/bin/dspace stats-util -o > Output looks like: > SOLR Optimize -- Process Started:1277486321673 > SOLR Optimize -- Process Finished:1277486321738 > SOLR Optimize -- Total time taken:65 (ms). > It would be useful to profile the amount of time taken for solr operations > add/update/query before running this optimize task, and then afterwards. -- 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 -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-615) Ability to perform maintenance on SOLR with solr.optimize
[ https://jira.duraspace.org/browse/DS-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-615: --- Attachment: screenshot_079.png > Ability to perform maintenance on SOLR with solr.optimize > - > > Key: DS-615 > URL: https://jira.duraspace.org/browse/DS-615 > Project: DSpace > Issue Type: Improvement > Components: Solr > Environment: solr >Reporter: Peter Dietz >Assignee: Ben Bosman > Fix For: 1.7.0 > > Attachments: screenshot_079.png, screenshot_079.png, > solr-optimize.patch, SolrOptimizeAndAutoCommit.patch > > > By adding all historical log data to a SOLR index, as well as the constant > addition of new records, it might be good for the efficient performance of a > SOLR index to periodically run solr.optimize. > Therefore I've created a patch which allows you to run solr.optimize on your > solr instance from the command line. This could allow you to add a cron task > that runs this periodic maintenance. It also spits out the amount of time > taken to run the optimize task. > Once you patch your instance. You can execute this with > /dspace/bin/dspace stats-util --optimize > or > /dspace/bin/dspace stats-util -o > Output looks like: > SOLR Optimize -- Process Started:1277486321673 > SOLR Optimize -- Process Finished:1277486321738 > SOLR Optimize -- Total time taken:65 (ms). > It would be useful to profile the amount of time taken for solr operations > add/update/query before running this optimize task, and then afterwards. -- 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 -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Issue Comment Edited: (DS-615) Ability to perform maintenance on SOLR with solr.optimize
[ https://jira.duraspace.org/browse/DS-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17982#action_17982 ] Peter Dietz edited comment on DS-615 at 11/3/10 9:59 PM: - Attaching a quick-and-dirty solution for performing solr.optimize on the search/discovery core. Not recommending this method as the way we do it, but it gets the job done. The patch can be run by running ./dspace update-discovery-index -o Also, I'd like to note that the initial update-discovery-index should switch to using autocommit, I've done this to my local install, and got a 10x speedup. So instead of needing a few hours, the indexing could be done in about 20 minutes. Other things like updating an existing record, or deleting a record should still use a hard solr.commit. was (Author: peterdietz): Attaching a quick-and-dirty solution for performing solr.optimize on the search/discovery core. Not recommending this method as the way we do it, but it gets the job done. Also, I'd like to note that the initial update-discovery-index should switch to using autocommit, I've done this to my local install, and got a 10x speedup. So instead of needing a few hours, the indexing could be done in about 20 minutes. Other things like updating an existing record, or deleting a record should still use a hard solr.commit. > Ability to perform maintenance on SOLR with solr.optimize > - > > Key: DS-615 > URL: https://jira.duraspace.org/browse/DS-615 > Project: DSpace > Issue Type: Improvement > Components: Solr > Environment: solr >Reporter: Peter Dietz >Assignee: Ben Bosman > Fix For: 1.7.0 > > Attachments: screenshot_079.png, screenshot_079.png, > solr-optimize.patch, SolrOptimizeAndAutoCommit.patch > > > By adding all historical log data to a SOLR index, as well as the constant > addition of new records, it might be good for the efficient performance of a > SOLR index to periodically run solr.optimize. > Therefore I've created a patch which allows you to run solr.optimize on your > solr instance from the command line. This could allow you to add a cron task > that runs this periodic maintenance. It also spits out the amount of time > taken to run the optimize task. > Once you patch your instance. You can execute this with > /dspace/bin/dspace stats-util --optimize > or > /dspace/bin/dspace stats-util -o > Output looks like: > SOLR Optimize -- Process Started:1277486321673 > SOLR Optimize -- Process Finished:1277486321738 > SOLR Optimize -- Total time taken:65 (ms). > It would be useful to profile the amount of time taken for solr operations > add/update/query before running this optimize task, and then afterwards. -- 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 -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-615) Ability to perform maintenance on SOLR with solr.optimize
[ https://jira.duraspace.org/browse/DS-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-615: --- Attachment: (was: screenshot_079.png) > Ability to perform maintenance on SOLR with solr.optimize > - > > Key: DS-615 > URL: https://jira.duraspace.org/browse/DS-615 > Project: DSpace > Issue Type: Improvement > Components: Solr > Environment: solr >Reporter: Peter Dietz >Assignee: Ben Bosman > Fix For: 1.7.0 > > Attachments: search-solr-optimize-quick-and-dirty.patch, > solr-optimize.patch, SolrOptimizeAndAutoCommit.patch > > > By adding all historical log data to a SOLR index, as well as the constant > addition of new records, it might be good for the efficient performance of a > SOLR index to periodically run solr.optimize. > Therefore I've created a patch which allows you to run solr.optimize on your > solr instance from the command line. This could allow you to add a cron task > that runs this periodic maintenance. It also spits out the amount of time > taken to run the optimize task. > Once you patch your instance. You can execute this with > /dspace/bin/dspace stats-util --optimize > or > /dspace/bin/dspace stats-util -o > Output looks like: > SOLR Optimize -- Process Started:1277486321673 > SOLR Optimize -- Process Finished:1277486321738 > SOLR Optimize -- Total time taken:65 (ms). > It would be useful to profile the amount of time taken for solr operations > add/update/query before running this optimize task, and then afterwards. -- 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 -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-615) Ability to perform maintenance on SOLR with solr.optimize
[ https://jira.duraspace.org/browse/DS-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-615: --- Attachment: search-solr-optimize-quick-and-dirty.patch > Ability to perform maintenance on SOLR with solr.optimize > - > > Key: DS-615 > URL: https://jira.duraspace.org/browse/DS-615 > Project: DSpace > Issue Type: Improvement > Components: Solr > Environment: solr >Reporter: Peter Dietz >Assignee: Ben Bosman > Fix For: 1.7.0 > > Attachments: search-solr-optimize-quick-and-dirty.patch, > solr-optimize.patch, SolrOptimizeAndAutoCommit.patch > > > By adding all historical log data to a SOLR index, as well as the constant > addition of new records, it might be good for the efficient performance of a > SOLR index to periodically run solr.optimize. > Therefore I've created a patch which allows you to run solr.optimize on your > solr instance from the command line. This could allow you to add a cron task > that runs this periodic maintenance. It also spits out the amount of time > taken to run the optimize task. > Once you patch your instance. You can execute this with > /dspace/bin/dspace stats-util --optimize > or > /dspace/bin/dspace stats-util -o > Output looks like: > SOLR Optimize -- Process Started:1277486321673 > SOLR Optimize -- Process Finished:1277486321738 > SOLR Optimize -- Total time taken:65 (ms). > It would be useful to profile the amount of time taken for solr operations > add/update/query before running this optimize task, and then afterwards. -- 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 -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-615) Ability to perform maintenance on SOLR with solr.optimize
[ https://jira.duraspace.org/browse/DS-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-615: --- Attachment: (was: screenshot_079.png) > Ability to perform maintenance on SOLR with solr.optimize > - > > Key: DS-615 > URL: https://jira.duraspace.org/browse/DS-615 > Project: DSpace > Issue Type: Improvement > Components: Solr > Environment: solr >Reporter: Peter Dietz >Assignee: Ben Bosman > Fix For: 1.7.0 > > Attachments: search-solr-optimize-quick-and-dirty.patch, > solr-optimize.patch, SolrOptimizeAndAutoCommit.patch > > > By adding all historical log data to a SOLR index, as well as the constant > addition of new records, it might be good for the efficient performance of a > SOLR index to periodically run solr.optimize. > Therefore I've created a patch which allows you to run solr.optimize on your > solr instance from the command line. This could allow you to add a cron task > that runs this periodic maintenance. It also spits out the amount of time > taken to run the optimize task. > Once you patch your instance. You can execute this with > /dspace/bin/dspace stats-util --optimize > or > /dspace/bin/dspace stats-util -o > Output looks like: > SOLR Optimize -- Process Started:1277486321673 > SOLR Optimize -- Process Finished:1277486321738 > SOLR Optimize -- Total time taken:65 (ms). > It would be useful to profile the amount of time taken for solr operations > add/update/query before running this optimize task, and then afterwards. -- 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 -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-760) Broken authority-control icons in Mirage theme
Broken authority-control icons in Mirage theme -- Key: DS-760 URL: https://jira.duraspace.org/browse/DS-760 Project: DSpace Issue Type: Bug Components: XMLUI Affects Versions: 1.7.0 Reporter: Peter Dietz Assignee: Peter Dietz Fix For: 1.7.0 -- Originally Reported in UserVoice during Testathon 1.7 -- Mirage theme is missing an invisible image During item submission, one of the metadata field had no authority for it, so instead of having a green thumb, the theme wants themes/Mirage/images/invisible.gif but it doesn't exist. Either remove the call for invisible from the theme, or add an image called invisible.gif It turns out that all images for authority-control are not working. Perhaps someone moved the images to images/authority_control without updating the code. -- 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/msIE9-sfdev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-760) Broken authority-control icons in Mirage theme
[ https://jira.duraspace.org/browse/DS-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-760: --- Status: Open (was: Received) > Broken authority-control icons in Mirage theme > -- > > Key: DS-760 > URL: https://jira.duraspace.org/browse/DS-760 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.7.0 >Reporter: Peter Dietz >Assignee: Peter Dietz > Fix For: 1.7.0 > > > -- Originally Reported in UserVoice during Testathon 1.7 -- > Mirage theme is missing an invisible image > During item submission, one of the metadata field had no authority for it, so > instead of having a green thumb, the theme wants > themes/Mirage/images/invisible.gif but it doesn't exist. > Either remove the call for invisible from the theme, or add an image called > invisible.gif > It turns out that all images for authority-control are not working. Perhaps > someone moved the images to images/authority_control without updating the > code. -- 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/msIE9-sfdev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-760) Broken authority-control icons in Mirage theme
[ https://jira.duraspace.org/browse/DS-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz resolved DS-760. Resolution: Fixed > Broken authority-control icons in Mirage theme > -- > > Key: DS-760 > URL: https://jira.duraspace.org/browse/DS-760 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.7.0 >Reporter: Peter Dietz >Assignee: Peter Dietz > Fix For: 1.7.0 > > > -- Originally Reported in UserVoice during Testathon 1.7 -- > Mirage theme is missing an invisible image > During item submission, one of the metadata field had no authority for it, so > instead of having a green thumb, the theme wants > themes/Mirage/images/invisible.gif but it doesn't exist. > Either remove the call for invisible from the theme, or add an image called > invisible.gif > It turns out that all images for authority-control are not working. Perhaps > someone moved the images to images/authority_control without updating the > code. -- 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/msIE9-sfdev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Assigned: (DS-570) Redirect users to current page on login
[ https://jira.duraspace.org/browse/DS-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz reassigned DS-570: -- Assignee: (was: Peter Dietz) Unassigning myself, as I'm not the last to work on it, and the expected outcome is unclear. > Redirect users to current page on login > --- > > Key: DS-570 > URL: https://jira.duraspace.org/browse/DS-570 > Project: DSpace > Issue Type: New Feature > Components: JSPUI, XMLUI >Reporter: Caryn N. > Fix For: 1.7.0 > > Attachments: DS-570-JSPUI.patch, xmlui.patch > > > I would like to be able to direct a user to the "current" page after login. > For example, if a user is not logged in, and they are looking at an item > page, when they click login, I would like to be able to send them back to the > item page. > As it functions now, a user who has found an item they want, then clicked log > in, will be authenticated and sent either home or to the profile (this option > is set in dspace.cfg file). This means they will need to find the item they > wanted again, which is not the most user-friendly. -- 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/msIE9-sfdev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-464) Item type based submission
[ https://jira.duraspace.org/browse/DS-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18218#action_18218 ] Peter Dietz commented on DS-464: Has there been progress on this feature? I remember at OR10 hearing that this feature was much improved. Its too late to squeeze any features into 1.7 at this point, but I think many people were interested in this feature, hopefully there is something available for review? > Item type based submission > -- > > Key: DS-464 > URL: https://jira.duraspace.org/browse/DS-464 > Project: DSpace > Issue Type: New Feature > Components: DSpace API, XMLUI >Affects Versions: 1.5.2 >Reporter: Robin Taylor >Assignee: Richard Rodgers > Fix For: 1.7.0 > > Attachments: Item-based-Submission.zip > > > This code adds a new screen to the submission process that allows the user to > select an item type from a list of types defined in the input-forms.xml file. > The subsequent metadata collection screen(s) are then built based on the > selected type. The code was developed as an XMLUI Maven module and is > included in the attached zip file along with a README with installation > instructions. > For the techies amongst you :- > The existing input-forms.xml allows for different forms based on collection > name or handle, in fact its already more generic than that. The file and > reader class just expect a string as input so the file can be reformatted > based on item type. The module comprises a new screen plus some minor changes > to existing classes to get/set the item type and persist it in the database > whilst the item is in submission/workflow. > I haven't included code for a JSPUI screen although if the screen is not > defined in item-submission.xml then the code will revert to the collection > based forms. I could provide a JSPUI alternative if there were interest. > This has been tested at 1.5.2 but I suspect it would work without alteration > for 1.6. Again, I can test this if there is interest. -- 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/msIE9-sfdev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-522) Script to convert Apache accesslog data into solr stats records
[
https://jira.duraspace.org/browse/DS-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Dietz resolved DS-522.
Resolution: Won't Fix
Fix Version/s: (was: 1.7.0)
I'm not sure if there is much interest in this feature, and I no longer need
the functionality, so I'm closing this as Won't Fix.
> Script to convert Apache accesslog data into solr stats records
> ---
>
> Key: DS-522
> URL: https://jira.duraspace.org/browse/DS-522
> Project: DSpace
> Issue Type: New Feature
> Components: Solr
>Affects Versions: 1.6.0, 1.6.1
>Reporter: Peter Dietz
>Assignee: Peter Dietz
> Attachments: DS-ApacheLogConverter-1.patch,
> DS-ApacheLogConverter-1b.patch
>
>
> Patch added that allows Apache's access log data to be used to possible
> supplant dspace.log data.
> Before running clean up your access log with an awk command.
> awk '{print $4,$5,",",$7,",","DB",",","anonymous",",",$1}'
> /path/to/access_log > /path/out/access_log_intermediate
> Then this command can be invoked with dspace.
> [dspace/bin/] ./dspace stats-apachelog-converter -i
> /path/out/access_log_intermediate -o /path/solr/solrready
> Currently, it skips "/dspace/retrieve/40199/1990-RA-01.jpg.jpg" entries.
> Check it out, and helpful find some bugs in it for me to fix. The rationale
> for wanting to add this is because our dspace.log files got rolled over into
> dspace.log.0 -- dspace.log.500, thus we have some missing data that this
> converter could fill the void for.
--
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
--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-771) Installed version of DSpace display
[ https://jira.duraspace.org/browse/DS-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18268#action_18268 ] Peter Dietz commented on DS-771: In the HTML "View Source" of each page of DSpace is a meta tag that tells the version. See: view-source:http://demo.dspace.org/xmlui > Installed version of DSpace display > --- > > Key: DS-771 > URL: https://jira.duraspace.org/browse/DS-771 > Project: DSpace > Issue Type: Improvement > Components: XMLUI >Affects Versions: 1.6.2 >Reporter: Tim Ribaric >Priority: Trivial > > It would be great if the DSpace platform displayed the currently running > DSpace version in a simple to find way. For example while in the XMLUI it it > could be placed in the Control Panel under the DSpace Configuration tab. -- 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 -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Assigned: (DS-502) java.lang.NullPointerException on main page in xmlui without trailing slash
[ https://jira.duraspace.org/browse/DS-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz reassigned DS-502: -- Assignee: (was: Peter Dietz) > java.lang.NullPointerException on main page in xmlui without trailing slash > --- > > Key: DS-502 > URL: https://jira.duraspace.org/browse/DS-502 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.5.2, 1.6.0 > Environment: Resin 3.2.1 > Sun Java 1.6.0_17 > DSpace 1.5.2, or 1.6.0-rc2 > Gentoo Linux 10.0, Linux 2.6.30 i686 >Reporter: Alexander Smith > Attachments: cocoon.log.2010-04-14, dspace.log.2010-04-14 > > > Right after an install of DSpace 1.5.2, accessing the main XMLUI at > "http://localhost:8080/xmlui"; returns the following error: > java.lang.NullPointerException > at > org.apache.cocoon.servletservice.DynamicProxyRequestHandler.invoke(DynamicProxyRequestHandler.java:86) > at $Proxy20.getPathInfo(Unknown Source) > at > org.apache.cocoon.servletservice.spring.ServletFactoryBean$ServiceInterceptor.invoke(ServletFactoryBean.java:262) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at $Proxy19.service(Unknown Source) > at > org.apache.cocoon.servletservice.DispatcherServlet.service(DispatcherServlet.java:106) > at javax.servlet.http.HttpServlet.service(Unknown Source) > at com.caucho.server.dispatch.ServletFilterChain.doFilter(Unknown > Source) > at > org.dspace.app.xmlui.cocoon.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:142) > at com.caucho.server.dispatch.FilterFilterChain.doFilter(Unknown Source) > at > org.dspace.app.xmlui.cocoon.DSpaceCocoonServletFilter.doFilter(DSpaceCocoonServletFilter.java:244) > at com.caucho.server.dispatch.FilterFilterChain.doFilter(Unknown Source) > at > org.apache.cocoon.servlet.multipart.MultipartFilter.doFilter(MultipartFilter.java:131) > at com.caucho.server.dispatch.FilterFilterChain.doFilter(Unknown Source) > at com.caucho.server.webapp.WebAppFilterChain.doFilter(Unknown Source) > at com.caucho.server.dispatch.ServletInvocation.service(Unknown Source) > at com.caucho.server.http.HttpRequest.handleRequest(Unknown Source) > at com.caucho.server.port.TcpConnection.handleRequests(Unknown Source) > at com.caucho.server.port.TcpConnection$AcceptTask.doAccept(Unknown > Source) > at com.caucho.server.port.TcpConnection$AcceptTask.run(Unknown Source) > at com.caucho.util.ThreadPool$Item.runTasks(Unknown Source) > at com.caucho.util.ThreadPool$Item.run(Unknown Source) > at java.lang.Thread.run(Thread.java:619) > However, if I use a trailing slash: "http://localhost:8080/xmlui/"; it works. > On DSpace 1.6.0, instead of a backtrace I just get a blank page. This only > happens with the xmlui, not the jspui. A workaround would be to include the > trailing slash; however, many of the internal links in DSpace return to the > "homepage" without a slash. > Note that I'm using Resin, not Tomcat. I don't know if that makes a > difference. -- 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 -- Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-790) SOLR - Spider detection to match on hostname or useragent
SOLR - Spider detection to match on hostname or useragent - Key: DS-790 URL: https://jira.duraspace.org/browse/DS-790 Project: DSpace Issue Type: Improvement Components: Solr Affects Versions: 1.7.0, 1.6.2, 1.6.1, 1.6.0 Environment: solr Reporter: Peter Dietz Spiders are currently detected by matching their IP address to one listed in the /dspace/config/spiders/ip-list-X.txt, however as spiders change IP addresses, or the ip-list is unmaintained, then many spiders can slip through, however they will usually keep their user agent or hostname intact. I've noticed a sore point in my solr data, where msnbot is completely unfiltered by solr. They have an additional ip list: http://www.iplists.com/nw/msn.txt however it is very old, and with additional bingbots on the horizon, it would be easier to detect, and filter them out of the logs by user-agent, then to maintain all of the IP address ranges. The code to do this in SOLR is unimplemented, and this ticket is a place holder to encourage this work to filter out based on user agent / dns-hostname to be finished. To see all of the hits from msnbot that are unfiltered, look at: http://localhost:8080/solr/statistics/select?q=dns:msnbot*&facet=true&facet.field=dns&facet.mincount=1&facet.limit=5000 -- 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 -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-816) Order of search types in XMLUI Advanced Search is arbitrary
Order of search types in XMLUI Advanced Search is arbitrary --- Key: DS-816 URL: https://jira.duraspace.org/browse/DS-816 Project: DSpace Issue Type: Bug Components: XMLUI Affects Versions: 1.7.0, 1.6.2, 1.6.1, 1.6.0, 1.5.2, 1.5.1, 1.5.0 Reporter: Peter Dietz Assignee: Peter Dietz Fix For: 1.7.1, 1.8.0 The ordering of search types on the advanced-search page is completely arbitrary in XMLUI. The expected order of search types should follow what is listed in dspace.cfg's search.index., as is how JSPUI functions. However the current behavior of xmlui's order of search types is arbitrary and is the result of the implementation of Java's map object. -- 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 -- 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
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-816) Order of search types in XMLUI Advanced Search is arbitrary
[ https://jira.duraspace.org/browse/DS-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-816: --- Attachment: xmlui-advanced-search-search-type-order.diff Patch to chance implementation to ArrayList instead of map, so that the order would match the search.index to first occurence of one of its type. Instead of building the object of search-types with N objects, and then pulling out the K uniques, within the checking of the N objects from the config we use them immediately, and add the used search types to a list that we excluded ourselves from adding more like it. > Order of search types in XMLUI Advanced Search is arbitrary > --- > > Key: DS-816 > URL: https://jira.duraspace.org/browse/DS-816 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0 >Reporter: Peter Dietz >Assignee: Peter Dietz > Fix For: 1.7.1, 1.8.0 > > Attachments: xmlui-advanced-search-search-type-order.diff > > > The ordering of search types on the advanced-search page is completely > arbitrary in XMLUI. > The expected order of search types should follow what is listed in > dspace.cfg's search.index., as is how JSPUI functions. > However the current behavior of xmlui's order of search types is arbitrary > and is the result of the implementation of Java's map object. -- 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 -- 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
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-296) DspaceFeedGenerator not serializable?!
[ https://jira.duraspace.org/browse/DS-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18828#action_18828 ] Peter Dietz commented on DS-296: We just switched our production instance to XMLUI, and we're seeing this error frequently. Anyone with experience with cocoon serialization / DSpaceFeedGenerator care to weigh in? I may consider Wendy's fix, but I'm thinking I would first want to throw lots of log.debug()'s in the code to trace down what's going on where. > DspaceFeedGenerator not serializable?! > -- > > Key: DS-296 > URL: https://jira.duraspace.org/browse/DS-296 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.5.2, 1.6.0 >Reporter: Flávio Botelho > > For some reason, the code wants to serialize > org.dspace.app.xmlui.cocoon.DSpaceFeedGenerator, should it? > If so than it needs to implement serializable. > Else somewhere there is a pointer to such an object that shouldn't be. > tor--8594061610370491601_T-i18n-context://i18n/?pt_BR__S-xml-;encoding=UTF-8;indent=yes'. > Initial cause was org.dspace.app.xmlui.cocoon.DSpaceFeedGenerator > java.io.NotSerializableException: > org.dspace.app.xmlui.cocoon.DSpaceFeedGenerator > at > java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) > at > java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) > at > java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) > at > java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) > at > java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) > at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1251) > at > java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075) > at > java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) > at > java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) > at > java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) > at > java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) > at > java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) > at > java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) > at > java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) > at > java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) > at net.sf.ehcache.store.DiskStore.serializeEntry(DiskStore.java:739) > at net.sf.ehcache.store.DiskStore.writeElement(DiskStore.java:678) > at > net.sf.ehcache.store.DiskStore.writeOrReplaceEntry(DiskStore.java:667) > at net.sf.ehcache.store.DiskStore.flushSpool(DiskStore.java:639) > at > net.sf.ehcache.store.DiskStore.throwableSafeFlushSpoolIfRequired(DiskStore.java:615) > at > net.sf.ehcache.store.DiskStore.spoolAndExpiryThreadMain(DiskStore.java:583) > at net.sf.ehcache.store.DiskStore.access$800(DiskStore.java:65) > at > net.sf.ehcache.store.DiskStore$SpoolAndExpiryThread.run(DiskStore.java:1057) -- 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 -- 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
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-692) Clean up invalid HTML in collection and community metadata
[ https://jira.duraspace.org/browse/DS-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-692: --- Attachment: CDATA-wrapping-collection-attributes.patch Added a patch that allows one to wrap the collection/community attributes into a CDATA tag. Thus allowing the page to render fine without having to fix their invalid markup. (patch is made with git, and against code in 1.6.1) > Clean up invalid HTML in collection and community metadata > -- > > Key: DS-692 > URL: https://jira.duraspace.org/browse/DS-692 > Project: DSpace > Issue Type: New Feature > Components: DSpace API >Affects Versions: 1.6.2 > Environment: xmlui >Reporter: Peter Dietz >Assignee: Peter Dietz > Attachments: CDATA-wrapping-collection-attributes.patch, > jtidy-comm-coll.patch, xmlui-report-invalid-coll-comm.patch > > > In JSPUI the system was forgiving with an instance with plain-old-HTML that > users entered into the metadata values for fields. In XMLUI, it requires > valid XHTML, otherwise it junks the whole text and displays the html in the > page, as opposed to rendering them. This solves local needs, and had been a > deal breaker before migrating between systems. > Therefore, I've implemented jTidy in DSpace to clean up collection and > community metadata fields. It runs from the command line. > == To Install the JTidy JAR == > Download the jar: > http://sourceforge.net/projects/jtidy/files/JTidy/r938/jtidy-r938.jar/download > mvn install:install-file > -Dfile=/home/dspace/Downloads/jtidy-r938/jtidy-r938.jar -DgroupId=jtidy > -DartifactId=jtidy -Dversion=938 -Dpackaging=jar > Then it can be run from the command line: > /dspace/bin/dspace dsrun org.dspace.content.service.TidyService -- 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 -- What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-776) Collection admin cannot add bitstreams unless there is at least one bundle
[ https://jira.duraspace.org/browse/DS-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz resolved DS-776. Documentation Status: Not Required (was: Needed) Resolution: Fixed passed the authorization check on to authorization manager, which allows user to add bundle when they have submit rights to the item. > Collection admin cannot add bitstreams unless there is at least one bundle > -- > > Key: DS-776 > URL: https://jira.duraspace.org/browse/DS-776 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.6.2 >Reporter: Eija Airio >Assignee: Peter Dietz >Priority: Major > Fix For: 1.7.1 > > Attachments: AddBitstreamForm.java.patch > > > Collection admin should have all privileges to all the items in the > collection if granted in the configuration file. But she does not: if the > collection admin tries to add a bitstream into an item with no bundles, she > gets an error message: "You need the ADD & WRITE privilege on at least one > bundle to be able to upload new bitstreams". > And really, in AddBitstreamForm.java there is a comment: >// If the bundle does not exist then you have to be > supper admin to be able > // to upload to this bundle because at upload time > the bundle will be created but > // there is no way anyone but super admin could have > access to add to the bundle. > Why is this so? Couldn't we only check whether the user is an item admin and > if she is, give permission to add a bitstream? -- 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 -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-559) Statistics column and row labels not i18n
[ https://jira.duraspace.org/browse/DS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19368#action_19368 ] Peter Dietz commented on DS-559: I'm checking that this still affects us, and when I change my site language to non-English (German), the solr-statistics page has months, country-names, city-names in English, but all the other parts (page title, headings, hits/Zugriffe) are in German. So, if this still is affecting things, either copy and paste the mixed language content as a comment, or upload a screenshot would be very helpful. > Statistics column and row labels not i18n > - > > Key: DS-559 > URL: https://jira.duraspace.org/browse/DS-559 > Project: DSpace > Issue Type: Bug > Components: JSPUI >Affects Versions: 1.6.0 >Reporter: Claudia Jürgen >Assignee: Peter Dietz > Fix For: 1.7.1 > > > The column and row labels used in the SOLR based statistic tables are not > internationalized but English per default. -- 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 -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-620) Exceed maximum while uploading files got the user stuck should lead to a friendly error page
[ https://jira.duraspace.org/browse/DS-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz resolved DS-620. Documentation Status: Not Required Resolution: Fixed Fix Version/s: 1.8.0 Connected exception FileSizeLimitExceededException to FileUploadRequest, and all using methods, so that a friendly error page is the destination when actua-upload-size is greater than upload.max. Committed to trunk: #6151 > Exceed maximum while uploading files got the user stuck should lead to a > friendly error page > > > Key: DS-620 > URL: https://jira.duraspace.org/browse/DS-620 > Project: DSpace > Issue Type: Bug > Components: JSPUI >Affects Versions: 1.6.2 >Reporter: Claudia Jürgen >Assignee: Peter Dietz >Priority: Major > Fix For: 1.8.0 > > > Uploading a file > the configured upload.max (config parameter for jspui) > will get the user stuck without an indication why the action was not > possible. There should be a graceful error page indicating the restriction > and the usual contact admin reference. > Apart from the submission itself, the same can occur on resuming a workspace > submission, workflow tasks, edit item, create/edit a community/collection > (upload logo). -- 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 -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-620) Exceed maximum while uploading files got the user stuck should lead to a friendly error page
[ https://jira.duraspace.org/browse/DS-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-620: --- Fix Version/s: 1.7.1 Also committed to dspace-1_7_x to make it into dspace.1.7.1 #6158 > Exceed maximum while uploading files got the user stuck should lead to a > friendly error page > > > Key: DS-620 > URL: https://jira.duraspace.org/browse/DS-620 > Project: DSpace > Issue Type: Bug > Components: JSPUI >Affects Versions: 1.6.2 >Reporter: Claudia Jürgen >Assignee: Peter Dietz >Priority: Major > Fix For: 1.7.1, 1.8.0 > > > Uploading a file > the configured upload.max (config parameter for jspui) > will get the user stuck without an indication why the action was not > possible. There should be a graceful error page indicating the restriction > and the usual contact admin reference. > Apart from the submission itself, the same can occur on resuming a workspace > submission, workflow tasks, edit item, create/edit a community/collection > (upload logo). -- 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 -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Assigned: (DS-641) Page does not exist
[
https://jira.duraspace.org/browse/DS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Dietz reassigned DS-641:
--
Assignee: Peter Dietz
> Page does not exist
> ---
>
> Key: DS-641
> URL: https://jira.duraspace.org/browse/DS-641
> Project: DSpace
> Issue Type: Bug
> Components: Documentation, JSPUI
>Affects Versions: 1.5.2, 1.6.0, 1.6.1, 1.6.2
>Reporter: Hardik Mishra
>Assignee: Peter Dietz
>Priority: Major
> Fix For: 1.7.1
>
> Attachments: DS-641-fix-path-to-error-jsp.patch
>
>
> org.dspace.app.webui.servlet/BrowserServlet.java
> /**
> * Display the error page
> *
> * @param context
> * @param request
> * @param response
> * @throws ServletException
> * @throws IOException
> * @throws SQLException
> * @throws AuthorizeException
> */
> protected void showError(Context context, HttpServletRequest request,
> HttpServletResponse response)
> throws ServletException, IOException, SQLException,
> AuthorizeException
> {
> JSPManager.showJSP(request, response, "/browse/error.jsp");
> }
> There is no error.jsp under jspui/browse/
--
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
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-641) Page does not exist
[
https://jira.duraspace.org/browse/DS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Dietz resolved DS-641.
Resolution: Fixed
Fix Version/s: 1.8.0
Patched trunk and dspace-1_7_x to showInternalError instead of referencing old
missing error file.
> Page does not exist
> ---
>
> Key: DS-641
> URL: https://jira.duraspace.org/browse/DS-641
> Project: DSpace
> Issue Type: Bug
> Components: Documentation, JSPUI
>Affects Versions: 1.5.2, 1.6.0, 1.6.1, 1.6.2
>Reporter: Hardik Mishra
>Assignee: Peter Dietz
>Priority: Major
> Fix For: 1.7.1, 1.8.0
>
> Attachments: DS-641-fix-path-to-error-jsp.patch
>
>
> org.dspace.app.webui.servlet/BrowserServlet.java
> /**
> * Display the error page
> *
> * @param context
> * @param request
> * @param response
> * @throws ServletException
> * @throws IOException
> * @throws SQLException
> * @throws AuthorizeException
> */
> protected void showError(Context context, HttpServletRequest request,
> HttpServletResponse response)
> throws ServletException, IOException, SQLException,
> AuthorizeException
> {
> JSPManager.showJSP(request, response, "/browse/error.jsp");
> }
> There is no error.jsp under jspui/browse/
--
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
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-559) Statistics column and row labels not i18n
[ https://jira.duraspace.org/browse/DS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19398#action_19398 ] Peter Dietz commented on DS-559: The part that is not i18n is the: dates (i.e. default/always October instead of Oktober for germans) country names(i.e. default/always Germany instead of Deutschland for germans) Digging into the problem created DS-844 [ https://jira.duraspace.org/browse/DS-559 ] - [#DS-559] Statistics column and row labels not i18n - DuraSpace JIRA PeterDietz: hmm I would count having months, country names only in English on a non-en page still a mixed content city names are a different matter, the could be regarded as proper names ClaudiaJuergen: ok, dates can, and should be fixed, just a (hopefully) simple matter of passing the Locale to SolrLogger and dates should be Oktober, instead of October fixing cities/countries might be a mess, see: http://scm.dspace.org/svn/repo/dspace/trunk/dspace-stats/src/main/java/org/dspace/statistics/util/LocationUtils.java * Mapping between Country codes, English Country names, * Continent Codes, and English Continent names ok, thanks for your help so far. This clears up where the problem is. I was looking at things like "Statistics" and "Top 5 Downloads" and they all looked like they were translated this is messie, are the lists based on any standards? the countries, associated continents maybe along with the locale should be in an xml config file Don't a few countries have multiple locales? (Thinking: Canada, Switzerland) Those long parallel lists are trouble in the making. Tracking down the exact spot to add the continent for whatever southern Sudan turns into will be tricky work. * mhwood wonders why we don't use e.g. java.util.Locale.getDisplayCountry(session's Locale) mhwood -- good suggestion. not sure why we aren't using that. maybe you could add a JIRA issue to suggest that change? Will do. https://jira.duraspace.org/browse/DS-844 [ [#DS-844] Simplify, internationalize org.dspace.statistics.util.LocationUtils - DuraSpace JIRA ] - https://jira.duraspace.org [ https://jira.duraspace.org/browse/DS-844 ] - [#DS-844] Simplify, internationalize org.dspace.statistics.util.LocationUtils - DuraSpace JIRA > Statistics column and row labels not i18n > - > > Key: DS-559 > URL: https://jira.duraspace.org/browse/DS-559 > Project: DSpace > Issue Type: Bug > Components: JSPUI >Affects Versions: 1.6.0 >Reporter: Claudia Jürgen >Assignee: Peter Dietz > Fix For: 1.7.1 > > > The column and row labels used in the SOLR based statistic tables are not > internationalized but English per default. -- 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 -- Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-854) Licenses on non-DSpace files have been replaced by DSpace boilerplate license
Licenses on non-DSpace files have been replaced by DSpace boilerplate license - Key: DS-854 URL: https://jira.duraspace.org/browse/DS-854 Project: DSpace Issue Type: Task Components: XMLUI Affects Versions: 1.7.0 Reporter: Peter Dietz Fix For: 1.7.1, 1.8.0 PeterDietz> ...crap, just noticed we stole licensing from jquery+other JS's == http://demo.dspace.org/xmlui/static/js/jquery-1.4.2.min.js Ah, you mean the magic maven license plugin didn't know to keep its hands off jquery et al. pom wants some more s, like **/jquery*.js? **/scriptaculous/* Others? yep, I think so, otherwise we'll relicense them again.. scriptaculous/*.js, choise-support.js, Mirage / ... / modernizr.*.js iirc, there's also some duplication in jquery a static version and a google CDN version (in Mirage, at least) Who will tell JIRA? * kshepherd doesn't quite follow the licensing thing.. where are these stolen licenses? License plugin replaced the owners' license text with DSpace's boilerplate. ohhh, eek -- 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 -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-858) Multicore SOLR needs prevent remote access to solr cores
Multicore SOLR needs prevent remote access to solr cores Key: DS-858 URL: https://jira.duraspace.org/browse/DS-858 Project: DSpace Issue Type: Bug Components: Solr Affects Versions: 1.7.0 Reporter: Peter Dietz Assignee: Mark Diggory Priority: Major Fix For: 1.7.1, 1.8.0 Attachments: diff-modules_dspace-solr_trunk_webapp_src_main_webapp_WEB-INF_web.xml-from-r5524-to-r6235.diff Kim Shepherd has noticed that a default installation of DSpace 1.7.0 with no further security hardening through configuration of Tomcat and Apache HTTPD will allow remote access to SOLR. This problem was created when Solr went multicore on DSpace. The security vulnerabilities are that a remote user could view data in solr (non anonymised usage data, private metadata) that is typically restricted from remote users. Additionally a malicious user could alter or delete data in Solr. The fix for this is included in 1.7.1. Current users of DSpace 1.7.0 can either upgrade to 1.7.1 as soon as possible, or patch their [dspace]/webapps/solr/WEB-INF/web.xml with the change made in r6161 https://fisheye3.atlassian.com/browse/dspace/modules/dspace-solr/trunk/webapp/src/main/webapp/WEB-INF/web.xml?r2=6161&r1=5524 which moves the filter-mapping for LocalHostRestrictionFilter above SolrRequestFilter After patching or upgrading your system, those using Discovery should reindex their content. [dspace]/bin/dspace update-discovery-index -f -- 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 -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-858) Multicore SOLR needs prevent remote access to solr cores
[ https://jira.duraspace.org/browse/DS-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz resolved DS-858. Resolution: Fixed > Multicore SOLR needs prevent remote access to solr cores > > > Key: DS-858 > URL: https://jira.duraspace.org/browse/DS-858 > Project: DSpace > Issue Type: Bug > Components: Solr >Affects Versions: 1.7.0 >Reporter: Peter Dietz >Assignee: Mark Diggory >Priority: Major > Fix For: 1.7.1, 1.8.0 > > Attachments: > diff-modules_dspace-solr_trunk_webapp_src_main_webapp_WEB-INF_web.xml-from-r5524-to-r6235.diff > > > Kim Shepherd has noticed that a default installation of DSpace 1.7.0 with no > further security hardening through configuration of Tomcat and Apache HTTPD > will allow remote access to SOLR. This problem was created when Solr went > multicore on DSpace. The security vulnerabilities are that a remote user > could view data in solr (non anonymised usage data, private metadata) that is > typically restricted from remote users. Additionally a malicious user could > alter or delete data in Solr. > The fix for this is included in 1.7.1. Current users of DSpace 1.7.0 can > either upgrade to 1.7.1 as soon as possible, or patch their > [dspace]/webapps/solr/WEB-INF/web.xml with the change made in r6161 > https://fisheye3.atlassian.com/browse/dspace/modules/dspace-solr/trunk/webapp/src/main/webapp/WEB-INF/web.xml?r2=6161&r1=5524 > which moves the filter-mapping for LocalHostRestrictionFilter above > SolrRequestFilter > After patching or upgrading your system, those using Discovery should reindex > their content. > [dspace]/bin/dspace update-discovery-index -f -- 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 -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-858) Multicore SOLR needs prevent remote access to solr cores
[ https://jira.duraspace.org/browse/DS-858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19558#action_19558 ] Peter Dietz commented on DS-858: The easiest way to fix an affected 1.7.0 instance is to: Replace [dspace]/webapps/solr/WEB-INF/web.xml with http://scm.dspace.org/svn/repo/modules/dspace-solr/tags/dspace-solr-parent-1.4.1.1/webapp/src/main/webapp/WEB-INF/web.xml Restart tomcat. For good measure, if you are using Discovery, also be sure to then reindex discovery: [dspace]/bin/dspace update-discovery-index -f > Multicore SOLR needs prevent remote access to solr cores > > > Key: DS-858 > URL: https://jira.duraspace.org/browse/DS-858 > Project: DSpace > Issue Type: Bug > Components: Solr >Affects Versions: 1.7.0 >Reporter: Kim Shepherd >Assignee: Mark Diggory >Priority: Major > Fix For: 1.7.1, 1.8.0 > > Attachments: > diff-modules_dspace-solr_trunk_webapp_src_main_webapp_WEB-INF_web.xml-from-r5524-to-r6235.diff > > > Kim Shepherd has noticed that a default installation of DSpace 1.7.0 with no > further security hardening through configuration of Tomcat and Apache HTTPD > will allow remote access to SOLR. This problem was created when Solr went > multicore on DSpace. The security vulnerabilities are that a remote user > could view data in solr (non anonymised usage data, private metadata) that is > typically restricted from remote users. Additionally a malicious user could > alter or delete data in Solr. > The fix for this is included in 1.7.1. Current users of DSpace 1.7.0 can > either upgrade to 1.7.1 as soon as possible, or patch their > [dspace]/webapps/solr/WEB-INF/web.xml with the change made in r6161 > https://fisheye3.atlassian.com/browse/dspace/modules/dspace-solr/trunk/webapp/src/main/webapp/WEB-INF/web.xml?r2=6161&r1=5524 > which moves the filter-mapping for LocalHostRestrictionFilter above > SolrRequestFilter > After patching or upgrading your system, those using Discovery should reindex > their content. > [dspace]/bin/dspace update-discovery-index -f -- 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 -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-841) 'IllegalArgumentException: No such column rnum' error in DSpace 1.7.x XMLUI admin eperson (with Oracle backend)
[ https://jira.duraspace.org/browse/DS-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Dietz updated DS-841: --- Affects Version/s: 1.7.0 Hardy additionally says: DS-841, which is another Oracle bug with DSpace 1.7.x and Trunk--you can't edit or add ePeople in XMLUI if you're using Oracle. > 'IllegalArgumentException: No such column rnum' error in DSpace 1.7.x XMLUI > admin eperson (with Oracle backend) > --- > > Key: DS-841 > URL: https://jira.duraspace.org/browse/DS-841 > Project: DSpace > Issue Type: Bug >Affects Versions: 1.7.0, 1.7.1 > Environment: RHEL5, with Oracle on the back end >Reporter: Hardy Pottinger > Attachments: DS-841-fix-Oracle-compatibility-for-ePerson.patch > > > In using the 1.7.x branch for testing with Oracle. Everything installed fine, > and I've got a bare-bones repository up and running. However, in the XMLUI, > when I click on the admin ePeople link, I get the following error: > java.lang.IllegalArgumentException: No such column rnum > Here are the first few lines of the stack trace: > java.lang.IllegalArgumentException: No such column rnum > at > org.dspace.storage.rdbms.TableRow.canonicalizeAndCheck(TableRow.java:581) > at org.dspace.storage.rdbms.TableRow.setColumn(TableRow.java:433) > at > org.dspace.storage.rdbms.DatabaseManager.process(DatabaseManager.java:) > at > org.dspace.storage.rdbms.TableRowIterator.next(TableRowIterator.java:151) > at > org.dspace.storage.rdbms.TableRowIterator.toList(TableRowIterator.java:204) > at org.dspace.eperson.EPerson.search(EPerson.java:358) > at > org.dspace.app.xmlui.aspect.administrative.eperson.ManageEPeopleMain.addBody(ManageEPeopleMain.java:121) > at > org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:223) > at sun.reflect.GeneratedMethodAccessor213.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71) > at $Proxy66.startElement(Unknown Source) > at > org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87) > at > org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94) > at > org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:240) > at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71) > at $Proxy49.startElement(Unknown Source) > No such error is thrown when using the JSPUI. > > org.dspace.storage.rdbms.TableRow.canonicalizeAndCheck(TableRow.java:581 > Looking more closely at the stack trace, the problem appears to be that the > canonicalizeAndCheck method in TableRow is failing when it attempts to verify > the rnum column, which is created back in org.dspace.eperson.EPerson.search. -- 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 -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-864) Fix/cleanup code to ensure it is well documented
Fix/cleanup code to ensure it is well documented Key: DS-864 URL: https://jira.duraspace.org/browse/DS-864 Project: DSpace Issue Type: Documentation Components: DSpace API, JSPUI, LNI, OAI-PMH, REST API (experimental), Solr, SWORD, XMLUI Reporter: Peter Dietz Fix For: 1.8.0 Some classes in DSpace code are undocumented, some have little documentation, and other sections have misleading documentation. This on occasion requires the programmer who is using a class as a client to "Go To Source" to find out how something is implemented so understand what it is expecting for valid input. There are other sections of code, particularly portions of code This ticket is a placeholder for improvements that improve the Javadoc comment blocks that are read by intelli-sense IDE's, or perhaps documenting areas of code frequented by user interface customizations. -- 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 -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-869) Community/Collection admin cannot perform curation tasks on individual items.
Community/Collection admin cannot perform curation tasks on individual items. -- Key: DS-869 URL: https://jira.duraspace.org/browse/DS-869 Project: DSpace Issue Type: Bug Components: XMLUI Affects Versions: 1.7.1, 1.7.0 Reporter: Peter Dietz A community or collection admin can run curation tasks against containers (collections and/or communities), however, they cannot run curation tasks directly on items. When a collection admin tries to Peform a curation task on an item, they are redirected to a "Insufficient Privileges" page. 1) It seems odd that the community admin would not be able to curate an item inside of their community. 2) If the community admin was not supposed to be able to run curation tasks against items, then they shouldn't see the curation tab on the item edit page. Personally, I think it makes sense for community admin to be able to curate items inside of their community, same goes for collection admin. -- 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 -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-869) Community/Collection admin cannot perform curation tasks on individual items.
[ https://jira.duraspace.org/browse/DS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19776#action_19776 ] Peter Dietz commented on DS-869: A quick example for testing this, would be to log in as the community admin user, and try to curate the item: http://demo.dspace.org/xmlui/handle/10673/9360 Curating the parent community works fine. > Community/Collection admin cannot perform curation tasks on individual items. > -- > > Key: DS-869 > URL: https://jira.duraspace.org/browse/DS-869 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.7.0, 1.7.1 >Reporter: Peter Dietz > > A community or collection admin can run curation tasks against containers > (collections and/or communities), however, they cannot run curation tasks > directly on items. When a collection admin tries to Peform a curation task on > an item, they are redirected to a "Insufficient Privileges" page. > 1) It seems odd that the community admin would not be able to curate an item > inside of their community. > 2) If the community admin was not supposed to be able to run curation tasks > against items, then they shouldn't see the curation tab on the item edit page. > Personally, I think it makes sense for community admin to be able to curate > items inside of their community, same goes for collection admin. -- 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 -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-871) XMLUI caches community / collection page which doesn't show a recently submitted item immediately
XMLUI caches community / collection page which doesn't show a recently submitted item immediately - Key: DS-871 URL: https://jira.duraspace.org/browse/DS-871 Project: DSpace Issue Type: Bug Components: XMLUI Affects Versions: 1.7.1, 1.7.0 Reporter: Peter Dietz With discovery disabled in xmlui, a recently submitted item does not show on the recently submitted items list for the collection or community page, until the page cache expires. This may be by design, but it is a route that a user may be expecting to find their recently submitted item. Perhaps on submission, the cache for the parent container pages can be invalidated so that the next page view of it will get the recently submitted item in the list. To reproduce, in xmlui (tested with discovery off), view a collection page, then submit a new item to that collection, and go back to that collection page after submission. Continuously refreshing the page will not show the new item, unless a user tries to hard-clear the xmlui cache. Such as appending junk to the url as a parameter. i.e. servername.com/handle/123456789/1234?random-text -- 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 -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-871) XMLUI caches community / collection page which doesn't show a recently submitted item immediately
[ https://jira.duraspace.org/browse/DS-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19863#action_19863 ] Peter Dietz commented on DS-871: I've tried the suggestion to artifactbrowser.CollectionRecentSubmissions in removing all the implements caching, and tried the suggestion in DS-298 to change the pipeline to type=noncaching, and it hasn't decached the collection page's recent submissions. I have noticed that restarting tomcat will get the recent submissions to update, however, thats not a very practical solution. > XMLUI caches community / collection page which doesn't show a recently > submitted item immediately > - > > Key: DS-871 > URL: https://jira.duraspace.org/browse/DS-871 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.7.0, 1.7.1 >Reporter: Peter Dietz > > With discovery disabled in xmlui, a recently submitted item does not show on > the recently submitted items list for the collection or community page, until > the page cache expires. This may be by design, but it is a route that a user > may be expecting to find their recently submitted item. > Perhaps on submission, the cache for the parent container pages can be > invalidated so that the next page view of it will get the recently submitted > item in the list. > To reproduce, in xmlui (tested with discovery off), view a collection page, > then submit a new item to that collection, and go back to that collection > page after submission. Continuously refreshing the page will not show the new > item, unless a user tries to hard-clear the xmlui cache. Such as appending > junk to the url as a parameter. i.e. > servername.com/handle/123456789/1234?random-text -- 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 -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-599) SOLR statistics file download displays all files and not only those in the Bundle Original
[ https://jira.duraspace.org/browse/DS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20042#action_20042 ] Peter Dietz commented on DS-599: Hi Mark, Any progress on this? I think what would be desired would be a way to use stats-utils to purge non-ORIGINAL bitstream data, and a config to not-record non-ORIGINAL downloads from SOLR's stored data. > SOLR statistics file download displays all files and not only those in the > Bundle Original > -- > > Key: DS-599 > URL: https://jira.duraspace.org/browse/DS-599 > Project: DSpace > Issue Type: Bug > Components: Solr >Affects Versions: 1.6.0, 1.6.1, 1.6.2 >Reporter: Claudia Jürgen >Assignee: Mark Diggory >Priority: Major > Fix For: 1.8.0 > > > The file download statistic for an item displays all the bitstreams > regardless of the bundle they belong to. > So licenses, extracted texts got displayed and counted. This is a bit > confusing for the normal user as their existence is usually hidden from him. > Furthermore I wonder whether views from the edit item stage should be counted > as "regular" views at all. -- 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 -- Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-871) XMLUI caches community / collection page which doesn't show a recently submitted item immediately
[ https://jira.duraspace.org/browse/DS-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20127#action_20127 ] Peter Dietz commented on DS-871: I'm at an impasse too. You can disable cache on XMLUI all-together, but you don't want to do that. You can disable cache by changing https://github.com/DSpace/DSpace/blob/master/dspace-xmlui/dspace-xmlui-webapp/src/main/webapp/sitemap.xmap#L196 to type="noncaching". This is the same file as [dspace]/webapps/xmlui/sitemap.xmap. While load testing (10 concurrent users in JMeter), a cached community-list takes only 110ms on average. Yet an uncached community-list is upwards of 5 seconds per request. Most requests without caching become unbearable for a production system. Some pages in DSpace are caching and invalidating properly though. When you edit the metadata for an item, and then view the item page, the content changes to reflect your changes. So various transformers in xmlui need to be verified that they are properly checking the validity of the cache, and invalidating the cache when events have changed the content. Additionally, it is possible that some bug higher up has cached the entire pipeline, and ignoring an individual transformers validity. > XMLUI caches community / collection page which doesn't show a recently > submitted item immediately > - > > Key: DS-871 > URL: https://jira.duraspace.org/browse/DS-871 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.7.0, 1.7.1 >Reporter: Peter Dietz > > With discovery disabled in xmlui, a recently submitted item does not show on > the recently submitted items list for the collection or community page, until > the page cache expires. This may be by design, but it is a route that a user > may be expecting to find their recently submitted item. > Perhaps on submission, the cache for the parent container pages can be > invalidated so that the next page view of it will get the recently submitted > item in the list. > To reproduce, in xmlui (tested with discovery off), view a collection page, > then submit a new item to that collection, and go back to that collection > page after submission. Continuously refreshing the page will not show the new > item, unless a user tries to hard-clear the xmlui cache. Such as appending > junk to the url as a parameter. i.e. > servername.com/handle/123456789/1234?random-text -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
