[Dspace-devel] [DuraSpace JIRA] Commented: (DS-875) DSpace Configuration service error when using "dspace" script.
[
https://jira.duraspace.org/browse/DS-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20293#action_20293
]
Stuart Lewis commented on DS-875:
-
I can confirm that Kevin's patch fixes the problem.
However...
1) This loses anything in $CLASSPATH that may be set. We could instead use the
following:
# Class path for DSpace will be:
# Any existing classpath (if set)
# The JARs (WEB-INF/lib/*.jar)
# The WEB-INF/classes directory
if test "${CLASSPATH+set}" != set ; then
FULLPATH=$JARS:$DSPACEDIR/config
else
FULLPATH=$CLASSPATH:$JARS:$DSPACEDIR/config
fi
This will, if it is set, preserve the inclusion of CLASSPATH.
2) The original issue states:
"This error in itself is completely harmless since it is actually a log bug,
there is an e.printstacktrace() that should have been a log.error, the
configuration service will just fail to load the dspace config files in the
jars (which is harmless since the configuration service isn't used by DSpace at
the moment). "
I would recommend that we fix that at the same time before closing this issue.
> DSpace Configuration service error when using "dspace" script.
> --
>
> Key: DS-875
> URL: https://jira.duraspace.org/browse/DS-875
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
>Affects Versions: 1.7.1
>Reporter: Kevin Van de Velde
>Priority: Major
> Fix For: 1.8.0
>
> Attachments: dspace_script_bugfix.patch
>
>
> When using the dspace script (located in {dspace.dir}/bin directory) in
> DSpace 1.7.1 the following error will occur:
> java.lang.IllegalArgumentException: Resource path
> [{dspace.dir.path}/bin/dspace] does not denote a directory
> at
> org.springframework.core.io.support.PathMatchingResourcePatternResolver.retrieveMatchingFiles(PathMatchingResourcePatternResolver.java:563)
> at
> org.springframework.core.io.support.PathMatchingResourcePatternResolver.doFindMatchingFileSystemResources(PathMatchingResourcePatternResolver.java:543)
> at
> org.springframework.core.io.support.PathMatchingResourcePatternResolver.doFindPathMatchingFileResources(PathMatchingResourcePatternResolver.java:526)
> at
> org.springframework.core.io.support.PathMatchingResourcePatternResolver.findPathMatchingResources(PathMatchingResourcePatternResolver.java:342)
> at
> org.springframework.core.io.support.PathMatchingResourcePatternResolver.getResources(PathMatchingResourcePatternResolver.java:276)
> at
> org.dspace.servicemanager.config.DSpaceConfigurationService.loadInitialConfig(DSpaceConfigurationService.java:390)
> at
> org.dspace.servicemanager.config.DSpaceConfigurationService.(DSpaceConfigurationService.java:62)
> at
> org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:145)
> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:51)
> This error in itself is completely harmless since it is actually a log bug,
> there is an e.printstacktrace() that should have been a log.error, the
> configuration service will just fail to load the dspace config files in the
> jars (which is harmless since the configuration service isn't used by DSpace
> at the moment).
> The reason why the error is thrown lies in the configuration service, the
> following method is called when attempting to retrieve .cfg files from the
> classpath.
> PathMatchingResourcePatternResolver patchMatcher = new
> PathMatchingResourcePatternResolver();
> Resource[] resources =
> patchMatcher.getResources("classpath*:dspace/config-*.cfg");
> From the Spring documentation
> (http://static.springsource.org/spring/docs/2.5.x/reference/resources.html):
> Please note that "classpath*:" when combined with Ant-style patterns
> will only work reliably with at least one root directory before the
> pattern starts, unless the actual target files reside in the file
> system. This means that a pattern like "classpath*:*.xml" will not
> retrieve files from the root of jar files but rather only from the
> root of expanded directories. This originates from a limitation in the
> JDK's ClassLoader.getResources() method which only returns file system
> locations for a passed-in empty string (indicating potential roots to
> search).
> From the dspace script:
> FULLPATH=$CLASSPATH:$JARS:$DSPACEDIR/config
> java $JAVA_OPTS -classpath $FULLPATH org.dspace.app.launcher.ScriptLauncher
> "$@"
> Conclusion:
> The problem is caused by the fact that the JDK is expecting directories or
> directories with at least one subdirectory to be passed in the FULLPATH
> argument when invoking Java. It is obvious that {dspace.dir}/bin/dspace
> violates these requirements, causing the process to throw an exception when
> trying to use this location as a directory. In order to
[Dspace-devel] [DuraSpace JIRA] Created: (DS-903) Link Checker curaton task
Link Checker curaton task - Key: DS-903 URL: https://jira.duraspace.org/browse/DS-903 Project: DSpace Issue Type: New Feature Components: DSpace API Reporter: Stuart Lewis Fix For: 1.8.0 Two link checker curation tasks: - A basic link checker that checks that any value of anyschema.anyelement.uri returns a 20x http status when retrieved. This link checker is also designed to be extended by overidding either or both of the getURLs and checkURL methods. - A simple link checker that extends the basic link checker, but isntead checks all elements that begin with http:// or https:// (Probably need to think of better names than simplelinkchecker and basiclinkchecker to differentiate between them better.) -- 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-903) Link Checker curaton task
[ https://jira.duraspace.org/browse/DS-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-903: Status: Open (was: Received) > Link Checker curaton task > - > > Key: DS-903 > URL: https://jira.duraspace.org/browse/DS-903 > Project: DSpace > Issue Type: New Feature > Components: DSpace API >Reporter: Stuart Lewis > Fix For: 1.8.0 > > Attachments: DS-903.patch > > > Two link checker curation tasks: > - A basic link checker that checks that any value of > anyschema.anyelement.uri returns a 20x http status when retrieved. This link > checker is also designed to be extended by overidding either or both of the > getURLs and checkURL methods. > - A simple link checker that extends the basic link checker, but isntead > checks all elements that begin with http:// or https:// > (Probably need to think of better names than simplelinkchecker and > basiclinkchecker to differentiate between them better.) -- 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-903) Link Checker curaton task
[ https://jira.duraspace.org/browse/DS-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-903: Attachment: DS-903.patch > Link Checker curaton task > - > > Key: DS-903 > URL: https://jira.duraspace.org/browse/DS-903 > Project: DSpace > Issue Type: New Feature > Components: DSpace API >Reporter: Stuart Lewis > Fix For: 1.8.0 > > Attachments: DS-903.patch > > > Two link checker curation tasks: > - A basic link checker that checks that any value of > anyschema.anyelement.uri returns a 20x http status when retrieved. This link > checker is also designed to be extended by overidding either or both of the > getURLs and checkURL methods. > - A simple link checker that extends the basic link checker, but isntead > checks all elements that begin with http:// or https:// > (Probably need to think of better names than simplelinkchecker and > basiclinkchecker to differentiate between them better.) -- 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] Commented: (DS-906) For moving items in the Admin UI, add checkbox option to replace resource policies with defaults of the new collection
[ https://jira.duraspace.org/browse/DS-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20364#action_20364 ] Stuart Lewis commented on DS-906: - Is this a duplicate of DS-525 which is included in 1.7? > For moving items in the Admin UI, add checkbox option to replace resource > policies with defaults of the new collection > -- > > Key: DS-906 > URL: https://jira.duraspace.org/browse/DS-906 > Project: DSpace > Issue Type: Improvement > Components: XMLUI >Affects Versions: 1.7.2, 1.8.0 >Reporter: Bill Hays > > This is a single call in the API: > item.inheritCollectionDefaultPolicies(targetCollection) -- 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 Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including 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] Commented: (DS-912) Authorization policy
[ https://jira.duraspace.org/browse/DS-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20503#action_20503 ] Stuart Lewis commented on DS-912: - One way to accomplish this (relatively) easily, would be to write a small curation task 'Inherit parent policies'. This would be about 10 lines of code, and you'd simply run the curation task on any collection which needs fixing. This might make a useful little curation task to put in the main DSpace distribution. > Authorization policy > > > Key: DS-912 > URL: https://jira.duraspace.org/browse/DS-912 > Project: DSpace > Issue Type: Improvement > Environment: Definition of authorization policies >Reporter: Biblioteca Digital do Superior Tribunal de Justiça > > When applying a new policy for authorization of a collection of DSpace, this > policy just going to be applied only to new items included in the collection. > Items deposited before setting new policy remain with the policy previously > defined. I wonder if it is possible to deploy the application for > establishing a policy for all collection items, even items that were > deposited before setting the new policy. -- 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] Commented: (DS-943) Login cache problem, login does not stick.
[ https://jira.duraspace.org/browse/DS-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20835#action_20835 ] Stuart Lewis commented on DS-943: - One small thing to try - set 'webui.session.invalidate = true' to false in dspace.cfg. It might help (or it might not!). Have you tried the jspui to see if you get the same behaviour? > Login cache problem, login does not stick. > -- > > Key: DS-943 > URL: https://jira.duraspace.org/browse/DS-943 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.7.1, 1.7.2 > Environment: Redhat Enterprise Linux, Linux Mint >Reporter: Jeremiah Pehlasery > > From mostly any page, when I try to login I am taken to the login page, I > enter my credentials, login and when the next page loads, I again have the > option to login. i can continously click the login link login and repeat > forever. The only difference will be if I try to access restricted content, I > will login and be shown the content and the various context menus will update > to actually show I'm logged in (giving the option to log out). > I have tried editing the sitemap.xmap file of various xmlui themes to try and > disable caching but no luck. I've also tried editing cache settings in > dspace.cfg, but I don't think there's anything in there that pertains to this > kind of caching. Changing it anyways, didn't prove fruitful. -- 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] Updated: (DS-826) LDAPServlet.java incorrectly redirects to incorrect.jsp rather than ldap-incorrect.jsp
[ https://jira.duraspace.org/browse/DS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-826: Assignee: Stuart Lewis Status: Open (was: Received) > LDAPServlet.java incorrectly redirects to incorrect.jsp rather than > ldap-incorrect.jsp > -- > > Key: DS-826 > URL: https://jira.duraspace.org/browse/DS-826 > Project: DSpace > Issue Type: Bug > Components: JSPUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0 >Reporter: Terry Burton >Assignee: Stuart Lewis > Attachments: LDAPServlet.java.patch > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > With wrong credentials LDAPServlet.java incorrectly redirects to > incorrect.jsp rather than ldap-incorrect.jsp. > Demonstrated by enabling both LDAP- and password-based authentication plugins > then logging into LDAP with wrong credentials. -- 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] Resolved: (DS-826) LDAPServlet.java incorrectly redirects to incorrect.jsp rather than ldap-incorrect.jsp
[ https://jira.duraspace.org/browse/DS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis resolved DS-826. - Resolution: Fixed Fix Version/s: 1.8.0 Hi Terry - thanks for spotting this and for providing a patch. Thanks also to Alex for confirming the behaviour. This has now been added for 1.8. > LDAPServlet.java incorrectly redirects to incorrect.jsp rather than > ldap-incorrect.jsp > -- > > Key: DS-826 > URL: https://jira.duraspace.org/browse/DS-826 > Project: DSpace > Issue Type: Bug > Components: JSPUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0 >Reporter: Terry Burton >Assignee: Stuart Lewis > Fix For: 1.8.0 > > Attachments: LDAPServlet.java.patch > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > With wrong credentials LDAPServlet.java incorrectly redirects to > incorrect.jsp rather than ldap-incorrect.jsp. > Demonstrated by enabling both LDAP- and password-based authentication plugins > then logging into LDAP with wrong credentials. -- 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-941) Marker ticket for splitting up the dspace.cfg.
[ https://jira.duraspace.org/browse/DS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20899#action_20899 ] Stuart Lewis commented on DS-941: - I've started to work on moving the authN configurations out into separate classes. A few questions: - Should they all go into a single authentication.cfg, or what I have done is create authentication.cfg for configuring the authN stack, and then authentication-[ldap|x509|ip|password].cfg for each of the different methods. - I've had to edit calls to ConfigurationManager to specify the (e.g.) "authentication-ldap" module. Is this the correct way to be doing this, or is there a cleaner way without having to edit so much of the source? Thanks, Stuart > Marker ticket for splitting up the dspace.cfg. > --- > > Key: DS-941 > URL: https://jira.duraspace.org/browse/DS-941 > Project: DSpace > Issue Type: Improvement >Reporter: Robin Taylor > Fix For: 1.8.0 > > > Split dspace.cfg into separate files where appropriate. -- 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-941) Marker ticket for splitting up the dspace.cfg.
[
https://jira.duraspace.org/browse/DS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20900#action_20900
]
Stuart Lewis commented on DS-941:
-
I've been looking at this a bit more - I might be using this wrong, but since
the SWORD settings have been moved to modules/sword-server.cfg, they are not
read. They are only read if the following change is made:
int mus = ConfigurationManager.getIntProperty("sword.max-upload-size");
to
int mus = ConfigurationManager.getIntProperty("sword-server",
"sword.max-upload-size");
> Marker ticket for splitting up the dspace.cfg.
> ---
>
> Key: DS-941
> URL: https://jira.duraspace.org/browse/DS-941
> Project: DSpace
> Issue Type: Improvement
>Reporter: Robin Taylor
> Fix For: 1.8.0
>
>
> Split dspace.cfg into separate files where appropriate.
--
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] Resolved: (DS-834) CSV import dialog doesn't handle csv errors gracefully
[ https://jira.duraspace.org/browse/DS-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis resolved DS-834. - Resolution: Fixed Fix Version/s: 1.8.0 Fixed in trunk revision 6452 > CSV import dialog doesn't handle csv errors gracefully > -- > > Key: DS-834 > URL: https://jira.duraspace.org/browse/DS-834 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.6.2 >Reporter: Timo Aalto >Assignee: Stuart Lewis > Fix For: 1.8.0 > > Attachments: > [DS-834]_CSV_import_dialog_doesn_t_handle_csv_errors_gracefully.patch > > > I was trying to upload a csv containing some metadata changes. In the upload > dialog I all got was "no changes were detected" splash. It turned out that I > had accidentally left some completely empty columns in the middle of the CSV > file. Luckily I had a ssh screen running and it showed the stack trace below. > It would be good to catch that exception and provide some guidance for the > poor dspace admin trying to figure out what went wrong. > java.lang.ArrayIndexOutOfBoundsException: 1 > at > org.dspace.app.bulkedit.MetadataImport.compare(MetadataImport.java:345) > at > org.dspace.app.bulkedit.MetadataImport.runImport(MetadataImport.java:154) > at > org.dspace.app.xmlui.aspect.administrative.FlowMetadataImportUtils.processUploadCSV(FlowMetadataImportUtils.java:178) > 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:585) > 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) > at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2394) > at > org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:162) > at > org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393) > at > org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834) > at > org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160) > at org.mozilla.javascript.Context.call(Context.java:538) > at > org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1833) > at > org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1803) > at > org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:698) > at > org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:94) > at > org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55) > at > org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87) > at > org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55) > at > org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87) -- 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] Updated: (DS-834) CSV import dialog doesn't handle csv errors gracefully
[ https://jira.duraspace.org/browse/DS-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-834: Attachment: [DS-834]_CSV_import_dialog_doesn_t_handle_csv_errors_gracefully.patch Patch attached. Also fixes an issue where no header is given, but there is data in that column. Adds better log4j logging too to help debugging. > CSV import dialog doesn't handle csv errors gracefully > -- > > Key: DS-834 > URL: https://jira.duraspace.org/browse/DS-834 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.6.2 >Reporter: Timo Aalto >Assignee: Stuart Lewis > Attachments: > [DS-834]_CSV_import_dialog_doesn_t_handle_csv_errors_gracefully.patch > > > I was trying to upload a csv containing some metadata changes. In the upload > dialog I all got was "no changes were detected" splash. It turned out that I > had accidentally left some completely empty columns in the middle of the CSV > file. Luckily I had a ssh screen running and it showed the stack trace below. > It would be good to catch that exception and provide some guidance for the > poor dspace admin trying to figure out what went wrong. > java.lang.ArrayIndexOutOfBoundsException: 1 > at > org.dspace.app.bulkedit.MetadataImport.compare(MetadataImport.java:345) > at > org.dspace.app.bulkedit.MetadataImport.runImport(MetadataImport.java:154) > at > org.dspace.app.xmlui.aspect.administrative.FlowMetadataImportUtils.processUploadCSV(FlowMetadataImportUtils.java:178) > 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:585) > 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) > at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2394) > at > org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:162) > at > org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393) > at > org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834) > at > org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160) > at org.mozilla.javascript.Context.call(Context.java:538) > at > org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1833) > at > org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1803) > at > org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:698) > at > org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:94) > at > org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55) > at > org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87) > at > org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55) > at > org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87) -- 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] Assigned: (DS-700) Bulk Metadata Editing: defining "formats" for export/re-import of selected fields
[ https://jira.duraspace.org/browse/DS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reassigned DS-700: --- Assignee: Kim Shepherd (was: Stuart Lewis) > Bulk Metadata Editing: defining "formats" for export/re-import of selected > fields > - > > Key: DS-700 > URL: https://jira.duraspace.org/browse/DS-700 > Project: DSpace > Issue Type: Improvement > Components: DSpace API, JSPUI >Reporter: Christophe Dupriez >Assignee: Kim Shepherd >Priority: Major > Attachments: vancouver.csv > > Original Estimate: 16 hours > Remaining Estimate: 16 hours > > When looking at use cases like: > 1) bulk correction of keyword assignment (export existing indexation and let > indexers create a new one using global search and replace) > 2) translation of abstracts (export existing abstracts in different languages > and let translators complete it and reimport) > 3) export of records for merging in a word processor template > current CSV Bulk Metadata Editing has many good feature and may be a lack in > terms of defining exports/reimport of a selection of fields. > Another thing which surprises me is the use of item ID instead of handle to > identify the records. But this may be due to conflicting use cases: > 1) bulk reorganisation of handle assignment (IDs stay but handles may change) > 2) move from one version of an instance to another (IDs change but handles > stay) > I would like to define different thing in accordance with community whims if > possible: > 1) FORMATS: each format would be a list of metadata fields+language to be > exported. > 2) Standardize output directories: using a configurable pattern in > DSpace.CFG, the exported/imported files would be send to a directory > structure made of the user name and the format. A timestamp and/or a name > choosen by the user would be used as a file name. For instance, > /users/~[user]/dspace/csv/[format]/[filename].csv could be such a pattern. > Missing directories would be automatically created. One could define a > pattern where filenames contain the format type also: > /users/~[user]/dspace/csv/[format]/[format]-[filename].csv > My proposal for Export Formats Configuration would be to add a subdirectory > dspace/conf/bulkedit where format.csv files would each give the headers of > the desired columns in the export files with this format. > We could keep a format named "allfields" for the current behavior. > Please let me know soon what you would like so I can propose a module in line > with community wishes! -- 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-941) Marker ticket for splitting up the dspace.cfg.
[ https://jira.duraspace.org/browse/DS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20942#action_20942 ] Stuart Lewis commented on DS-941: - So it sounds like the best option in these case is to use the prefix for the filename (e.g. ldap.cfg / sword.cfg / authentication.cfg) and then to remove that from the keys when we transfer them - e.g. 'ldap.enable' become 'enable'. However if we did that, then many will be in their own files (e.g. ldap) however others such as x509 and shibboleth always use the 'authentication.' prefix. What's the best thing here - re-work the code that reads those to drop the 'authentication.'? > Marker ticket for splitting up the dspace.cfg. > --- > > Key: DS-941 > URL: https://jira.duraspace.org/browse/DS-941 > Project: DSpace > Issue Type: Improvement >Reporter: Robin Taylor > Fix For: 1.8.0 > > > Split dspace.cfg into separate files where appropriate. -- 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-941) Marker ticket for splitting up the dspace.cfg.
[
https://jira.duraspace.org/browse/DS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20948#action_20948
]
Stuart Lewis commented on DS-941:
-
I've got a patch that does that - it creates 'authentication.cfg' and then
'authentication-{method}.cfg'. To make this work, I've had to add these file
names into all the calls to
ConfigurationManager.getProperty("authentication-ldap", "ldap.enable"). If
that sounds OK, I can get it committed.
Or the second option is to do as above, but to drop the prefixes, so it
becomes: ConfigurationManager.getProperty("authentication-ldap", "enable")
Any preferences?
> Marker ticket for splitting up the dspace.cfg.
> ---
>
> Key: DS-941
> URL: https://jira.duraspace.org/browse/DS-941
> Project: DSpace
> Issue Type: Improvement
>Reporter: Robin Taylor
> Fix For: 1.8.0
>
>
> Split dspace.cfg into separate files where appropriate.
--
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-811) Delete / withdraw items via bulk csv editing
[
https://jira.duraspace.org/browse/DS-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20951#action_20951
]
Stuart Lewis commented on DS-811:
-
I've been working on this and now have a working version, but before I complete
the work to update the UIs and write the documentation, I need to check it with
everyone. It works as follows:
1) Add an 'action' column
2) Insert into the action column either 'delete', 'withdraw', 'reinstate' or
nothing.
3) ANY CHANGES IN METADATA ARE IGNORED IF THERE IS AN ACTION COLUMN. Is that
OK?
4) The action column is then examined, and if applicable (e.g. it won't attempt
to reinstate an item that isn't withdrawn) it will make the changes.
Feedback welcome. Hopefully I'll post a patch soon.
Thanks,
Stuart
> Delete / withdraw items via bulk csv editing
>
>
> Key: DS-811
> URL: https://jira.duraspace.org/browse/DS-811
> Project: DSpace
> Issue Type: New Feature
> Components: DSpace API, JSPUI, XMLUI
>Reporter: Stuart Lewis
>Assignee: Stuart Lewis
> Fix For: 1.8.0
>
>
> I want to enhance the CSV-based batch editing tool. One obvious enhancement
> is to allow the withdrawal / deletion of items. I propose to implement this
> by:
> - In the 'collection' column which normally holds the primary and mapped
> collection(s) in which the item resides, allow the values ('DELETE' or
> 'WITHDRAW') to be entered. These will, after the normal confirmation screen,
> perform those actions.
> Any comments on that before I implement it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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-941) Marker ticket for splitting up the dspace.cfg.
[ https://jira.duraspace.org/browse/DS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20978#action_20978 ] Stuart Lewis commented on DS-941: - dspace-api/src/main/java/org/dspace/app/mets/METSExport.java still uses oai.mets.hide-provenance. See https://jira.duraspace.org/browse/DS-196 for details. > Marker ticket for splitting up the dspace.cfg. > --- > > Key: DS-941 > URL: https://jira.duraspace.org/browse/DS-941 > Project: DSpace > Issue Type: Improvement >Reporter: Robin Taylor > Fix For: 1.8.0 > > > Split dspace.cfg into separate files where appropriate. -- 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-941) Marker ticket for splitting up the dspace.cfg.
[ https://jira.duraspace.org/browse/DS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20979#action_20979 ] Stuart Lewis commented on DS-941: - Have just read the related ticket about METS (DS-708). Apologies for the confusion. > Marker ticket for splitting up the dspace.cfg. > --- > > Key: DS-941 > URL: https://jira.duraspace.org/browse/DS-941 > Project: DSpace > Issue Type: Improvement >Reporter: Robin Taylor > Fix For: 1.8.0 > > > Split dspace.cfg into separate files where appropriate. -- 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] Assigned: (DS-827) Autoregister in LDAPHierarchicalAuthentication is incompatible with ldap.netid_email_domain option
[ https://jira.duraspace.org/browse/DS-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reassigned DS-827: --- Assignee: Stuart Lewis > Autoregister in LDAPHierarchicalAuthentication is incompatible with > ldap.netid_email_domain option > -- > > Key: DS-827 > URL: https://jira.duraspace.org/browse/DS-827 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0 >Reporter: Terry Burton >Assignee: Stuart Lewis > Attachments: LDAPHierarchicalAuthentication.java.patch > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When the ldap.netid_email_domain option is provided and ldap.email_mail field > omitted, LDAPHierarchicalAuthentication autoregister cannot function due to > an erroneous check for a null/empty ldap.ldapEmail property. > Note: This also appears to be the case in LDAPAuthentication.java, however > maybe somebody that is running this would like to provide a patch for that. -- 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-827) Autoregister in LDAPHierarchicalAuthentication is incompatible with ldap.netid_email_domain option
[ https://jira.duraspace.org/browse/DS-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20990#action_20990 ] Stuart Lewis commented on DS-827: - I can confirm that this is a bug, and this patch fixes it. The same issue applies in the normal (non hierarchical) LDAP login. I will apply the patch shortly. > Autoregister in LDAPHierarchicalAuthentication is incompatible with > ldap.netid_email_domain option > -- > > Key: DS-827 > URL: https://jira.duraspace.org/browse/DS-827 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0 >Reporter: Terry Burton >Assignee: Stuart Lewis > Attachments: LDAPHierarchicalAuthentication.java.patch > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When the ldap.netid_email_domain option is provided and ldap.email_mail field > omitted, LDAPHierarchicalAuthentication autoregister cannot function due to > an erroneous check for a null/empty ldap.ldapEmail property. > Note: This also appears to be the case in LDAPAuthentication.java, however > maybe somebody that is running this would like to provide a patch for that. -- 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] Updated: (DS-827) Autoregister in LDAPHierarchicalAuthentication is incompatible with ldap.netid_email_domain option
[ https://jira.duraspace.org/browse/DS-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-827: Attachment: [DS-827].patch Complete patch attached. > Autoregister in LDAPHierarchicalAuthentication is incompatible with > ldap.netid_email_domain option > -- > > Key: DS-827 > URL: https://jira.duraspace.org/browse/DS-827 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0 >Reporter: Terry Burton >Assignee: Stuart Lewis > Attachments: [DS-827].patch, LDAPHierarchicalAuthentication.java.patch > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When the ldap.netid_email_domain option is provided and ldap.email_mail field > omitted, LDAPHierarchicalAuthentication autoregister cannot function due to > an erroneous check for a null/empty ldap.ldapEmail property. > Note: This also appears to be the case in LDAPAuthentication.java, however > maybe somebody that is running this would like to provide a patch for that. -- 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] Resolved: (DS-827) Autoregister in LDAPHierarchicalAuthentication is incompatible with ldap.netid_email_domain option
[ https://jira.duraspace.org/browse/DS-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis resolved DS-827. - Resolution: Fixed Fix Version/s: 1.8.0 Committed. Also added a fix to the incomplete tabindex settings in ldap-form.jsp which caused tabindexes not to work properly in order in Chrome. > Autoregister in LDAPHierarchicalAuthentication is incompatible with > ldap.netid_email_domain option > -- > > Key: DS-827 > URL: https://jira.duraspace.org/browse/DS-827 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0 >Reporter: Terry Burton >Assignee: Stuart Lewis > Fix For: 1.8.0 > > Attachments: [DS-827].patch, LDAPHierarchicalAuthentication.java.patch > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When the ldap.netid_email_domain option is provided and ldap.email_mail field > omitted, LDAPHierarchicalAuthentication autoregister cannot function due to > an erroneous check for a null/empty ldap.ldapEmail property. > Note: This also appears to be the case in LDAPAuthentication.java, however > maybe somebody that is running this would like to provide a patch for that. -- 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] Updated: (DS-811) Delete / withdraw items via bulk csv editing
[
https://jira.duraspace.org/browse/DS-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart Lewis updated DS-811:
Attachment: Patch_v1.patch
Comments taken on board - this patch allows actions AND metadata changes to
take place at the same time. Feedback requested on patch.
To test, add a new column to a CSV with the header 'action'. This can hold
values of '' (empty), 'delete', 'withdraw', or 'reinstate'. Actions that
cannot be made (e.g. withdrawing a withdrawn item) are ignored in the same way
that applying identical metadata is ignored.
> Delete / withdraw items via bulk csv editing
>
>
> Key: DS-811
> URL: https://jira.duraspace.org/browse/DS-811
> Project: DSpace
> Issue Type: New Feature
> Components: DSpace API, JSPUI, XMLUI
>Reporter: Stuart Lewis
>Assignee: Stuart Lewis
> Fix For: 1.8.0
>
> Attachments: Patch_v1.patch
>
>
> I want to enhance the CSV-based batch editing tool. One obvious enhancement
> is to allow the withdrawal / deletion of items. I propose to implement this
> by:
> - In the 'collection' column which normally holds the primary and mapped
> collection(s) in which the item resides, allow the values ('DELETE' or
> 'WITHDRAW') to be entered. These will, after the normal confirmation screen,
> perform those actions.
> Any comments on that before I implement it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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-811) Delete / withdraw items via bulk csv editing
[
https://jira.duraspace.org/browse/DS-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21026#action_21026
]
Stuart Lewis commented on DS-811:
-
Strange - this patch was made today against trunk.
I'll attached the complete files that failed instead.
> Delete / withdraw items via bulk csv editing
>
>
> Key: DS-811
> URL: https://jira.duraspace.org/browse/DS-811
> Project: DSpace
> Issue Type: New Feature
> Components: DSpace API, JSPUI, XMLUI
>Reporter: Stuart Lewis
>Assignee: Stuart Lewis
> Fix For: 1.8.0
>
> Attachments: Patch_v1.patch
>
>
> I want to enhance the CSV-based batch editing tool. One obvious enhancement
> is to allow the withdrawal / deletion of items. I propose to implement this
> by:
> - In the 'collection' column which normally holds the primary and mapped
> collection(s) in which the item resides, allow the values ('DELETE' or
> 'WITHDRAW') to be entered. These will, after the normal confirmation screen,
> perform those actions.
> Any comments on that before I implement it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] Updated: (DS-811) Delete / withdraw items via bulk csv editing
[
https://jira.duraspace.org/browse/DS-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart Lewis updated DS-811:
Attachment: BulkEditChange.java
DSpaceCSV.java
DSpaceCSVLine.java
> Delete / withdraw items via bulk csv editing
>
>
> Key: DS-811
> URL: https://jira.duraspace.org/browse/DS-811
> Project: DSpace
> Issue Type: New Feature
> Components: DSpace API, JSPUI, XMLUI
>Reporter: Stuart Lewis
>Assignee: Stuart Lewis
> Fix For: 1.8.0
>
> Attachments: BulkEditChange.java, DSpaceCSV.java, DSpaceCSVLine.java,
> Patch_v1.patch
>
>
> I want to enhance the CSV-based batch editing tool. One obvious enhancement
> is to allow the withdrawal / deletion of items. I propose to implement this
> by:
> - In the 'collection' column which normally holds the primary and mapped
> collection(s) in which the item resides, allow the values ('DELETE' or
> 'WITHDRAW') to be entered. These will, after the normal confirmation screen,
> perform those actions.
> Any comments on that before I implement it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] Created: (DS-959) XMLUI login failure when using Tomcat 7.0.16
XMLUI login failure when using Tomcat 7.0.16 Key: DS-959 URL: https://jira.duraspace.org/browse/DS-959 Project: DSpace Issue Type: Bug Components: XMLUI Affects Versions: 1.7.2 Reporter: Stuart Lewis Priority: Major See: http://dspace.2283337.n4.nabble.com/Login-and-IE8-td3671944.html -- 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 -- Storage Efficiency Calculator This modeling tool is based on patent-pending intellectual property that has been used successfully in hundreds of IBM storage optimization engage- ments, worldwide. Store less, Store more with what you own, Move data to the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-959) XMLUI login failure when using Tomcat 7.0.16
[ https://jira.duraspace.org/browse/DS-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21171#action_21171 ] Stuart Lewis commented on DS-959: - Setting webui.session.invalidate to false hasn't helped. This also affects other authN methods, such a LDAP. The SESSION ID seems to change: 2011-07-19 10:00:16,620 INFO org.dspace.authenticate.LDAPAuthentication @ anonymous:session_id=A52F009064BC5D7253557A44FDE4F59B:ip_addr=127.0.0.1:auth:attempting trivial auth of user=stuart but then 2011-07-19 10:00:17,532 INFO org.dspace.app.xmlui.aspect.artifactbrowser.CommunityBrowser @ anonymous:session_id=D43A7166EA32E734A74D66869602AA43:ip_addr=127.0.0.1:view_community_list: I have confirmed with jspui that the session ID is getting persisted OK though. > XMLUI login failure when using Tomcat 7.0.16 > > > Key: DS-959 > URL: https://jira.duraspace.org/browse/DS-959 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.7.2 >Reporter: Stuart Lewis >Priority: Major > > See: http://dspace.2283337.n4.nabble.com/Login-and-IE8-td3671944.html -- 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 -- Storage Efficiency Calculator This modeling tool is based on patent-pending intellectual property that has been used successfully in hundreds of IBM storage optimization engage- ments, worldwide. Store less, Store more with what you own, Move data to the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-959) XMLUI login failure when using Tomcat 7.0.16
[ https://jira.duraspace.org/browse/DS-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21173#action_21173 ] Stuart Lewis commented on DS-959: - On my local copy, downgrading to 7.0.11 worked. Upgrading to 7.0.19 didn't help. > XMLUI login failure when using Tomcat 7.0.16 > > > Key: DS-959 > URL: https://jira.duraspace.org/browse/DS-959 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.7.2 >Reporter: Stuart Lewis >Priority: Major > > See: http://dspace.2283337.n4.nabble.com/Login-and-IE8-td3671944.html -- 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 -- Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-963) DSpaceI18NTransformer.java logs too aggressively
DSpaceI18NTransformer.java logs too aggressively
Key: DS-963
URL: https://jira.duraspace.org/browse/DS-963
Project: DSpace
Issue Type: Improvement
Components: XMLUI
Reporter: Stuart Lewis
Assignee: Stuart Lewis
Fix For: 1.8.0
log.info("Adding i18n location path for '"+catalogueId+"' catalogue:
"+baseLocationPath);
log.info("Adding i18n location path for '"+catalogueId+"' catalogue:
"+aspectLocationPath);
These should be debug log entries, not info. They fill up log files with no
immediately useful information.
--
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
--
5 Ways to Improve & Secure Unified Communications
Unified Communications promises greater efficiencies for business. UC can
improve internal communications as well as offer faster, more efficient ways
to interact with customers and streamline customer service. Learn more!
http://www.accelacomm.com/jaw/sfnl/114/51426253/
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Closed: (DS-973) Improve error reporting during CSV import
[ https://jira.duraspace.org/browse/DS-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis closed DS-973. --- Resolution: Duplicate Duplicate of DS-834 CSV import dialog doesn't handle csv errors gracefully. Fixed in trunk. > Improve error reporting during CSV import > - > > Key: DS-973 > URL: https://jira.duraspace.org/browse/DS-973 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.7.0, 1.7.1, 1.7.2, 1.8.0 >Reporter: Ivan Masár > > The metadata-import script returns "Error reading file: 1" when the CSV > header contains an unknown element (e.g. "test"). > It works well if the element is qualified (e.g. "dc.test") "Error reading > file: Unknown metadata element in heading: dc.test" > There should be a more helpful error message for this. -- 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 -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Reopened: (DS-973) Improve error reporting during CSV import
[ https://jira.duraspace.org/browse/DS-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reopened DS-973: - Assignee: Stuart Lewis Hi Ivan, apologies - I'll check this out. > Improve error reporting during CSV import > - > > Key: DS-973 > URL: https://jira.duraspace.org/browse/DS-973 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.7.0, 1.7.1, 1.7.2, 1.8.0 >Reporter: Ivan Masár >Assignee: Stuart Lewis > > The metadata-import script returns "Error reading file: 1" when the CSV > header contains an unknown element (e.g. "test"). > It works well if the element is qualified (e.g. "dc.test") "Error reading > file: Unknown metadata element in heading: dc.test" > There should be a more helpful error message for this. -- 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 -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1180) LDAP: if no adminUser is set, build the DN using the object_context
Stuart Lewis commented on DS-1180 LDAP: if no adminUser is set, build the DN using the object_context Is the intention of this patch to remove the need for the normal LDAP authentication class, as this new behaviour (not searching the tree) is how that already works. If so, this might be a sensible move to remove the duplication and having two LDAP authentication classes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1180) LDAP: if no adminUser is set, build the DN using the object_context
[ https://jira.duraspace.org/browse/DS-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25362#comment-25362 ] Stuart Lewis commented on DS-1180: -- It could be, and perhaps should be, now that you've added this patch to make the one class perform both functions. We just need to make this decision and go with it if we want to, then remember to remove the other LDAP authenticator class, and all associated documentation. I'd be happy for this to be done. > LDAP: if no adminUser is set, build the DN using the object_context > --- > > Key: DS-1180 > URL: https://jira.duraspace.org/browse/DS-1180 > Project: DSpace > Issue Type: Improvement >Reporter: Samuel Ottenhoff >Assignee: Ivan Masár > Fix For: 3.0 > > > Before attempting a user authentication, LDAPHierarchicalAuthentication > attempts to lookup the user's DN using an adminUser and adminPassword. This > is unnecessary if all users from an institution are in the same LDAP > container, e.g.,: > uid=sam,ou=Users,dc=example,dc=edu > The necessary variables for building the DN manually are already in > authentication-ldap.cfg. This patch attempts to build the DN manually *if* > the adminUser is empty. -- 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-172) Hit highlighting in search results
[ https://jira.duraspace.org/browse/DS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reassigned DS-172: --- Assignee: (was: Stuart Lewis) > Hit highlighting in search results > -- > > Key: DS-172 > URL: https://jira.duraspace.org/browse/DS-172 > Project: DSpace > Issue Type: Improvement >Reporter: Charles Kiplagat >Priority: Major > Attachments: screenshot-1.jpg > > > university of austrialia? Highlight hits of searched-for words in search > results. I think Lucene has a package for this and there is a patch of the > queue that uses that. -- 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-374) RSS/Atom feeds return too few Items when restricted items are excluded
[ https://jira.duraspace.org/browse/DS-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reassigned DS-374: --- Assignee: (was: Stuart Lewis) > RSS/Atom feeds return too few Items when restricted items are excluded > -- > > Key: DS-374 > URL: https://jira.duraspace.org/browse/DS-374 > Project: DSpace > Issue Type: Bug > Components: JSPUI, XMLUI >Affects Versions: 1.5.2, 1.6.0 >Reporter: Larry Stone > Attachments: > RSSAtom_feeds_return_too_few_Items_when_restricted_items_are_excluded.patch > > > The logic for excluding restricted (i.e. not world-readable) Items from the > RSS/Atom feeds results in too few Items being shown if any are actually > excluded. For example, when the DSpace Configuration properties set > harvest.includerestricted.rss = false, and webui.feed.items = 4, if two of > the selected (i.e. latest) Items are restricted then the feed will only list > 2 items instead of the configured 4. > This is a natural result of filtering by the access check _after_ getting the > requested number of results from the browse system. The effect is the same > in both JSPUI and XMLUI implementations of syndication feeds. > To demonstrate the effect, get a feed of e.g. 4 Items. Modify one of those > Items to remove the Anonymous READ access at the Item level. Be sure your > configuration sets harvest.includerestricted.rss = false. Get the same feed, > and observe that there is one fewer Item than the count configured in > webui.feed.items. -- 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-1083) Create new users from the command line
[ https://jira.duraspace.org/browse/DS-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reassigned DS-1083: Assignee: (was: Stuart Lewis) > Create new users from the command line > -- > > Key: DS-1083 > URL: https://jira.duraspace.org/browse/DS-1083 > Project: DSpace > Issue Type: New Feature > Components: DSpace API >Reporter: Stuart Lewis > > From dspace-tech 24th October 2011: > Hey all, > > Is there a way to register a new user via the command line on the server? I > want to perform the same activity as would happen via the "Register" link on > the dspace site, but via some scripted process. > > Is that doable? > > Thanks in advance! > > Justin -- 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-449) Command line utility org.dspace.app.harvest.Harvest -S throws AuthorizeException
[ https://jira.duraspace.org/browse/DS-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reassigned DS-449: --- Assignee: (was: Stuart Lewis) > Command line utility org.dspace.app.harvest.Harvest -S throws > AuthorizeException > > > Key: DS-449 > URL: https://jira.duraspace.org/browse/DS-449 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.6.0 >Reporter: Toni Prieto >Priority: Major > Attachments: patch_auth_excep_harvest.txt > > > Running the harvest command line utility with -S option (to start the harvest > scheduler), the system throws AuthorizeException: > Authorization denied for action WRITE on COLLECTION:1 by user 0 > Exception: > org.dspace.authorize.AuthorizeException: Authorization denied for action > WRITE on COLLECTION:1 by user 0 > at > org.dspace.authorize.AuthorizeManager.authorizeAction(AuthorizeManager.java:222) > at org.dspace.content.Collection.canEdit(Collection.java:1021) > at org.dspace.content.Collection.update(Collection.java:958) > at org.dspace.harvest.OAIHarvester.runHarvest(OAIHarvester.java:395) > at > org.dspace.harvest.OAIHarvester$HarvestThread.runHarvest(OAIHarvester.java:1301) > at > org.dspace.harvest.OAIHarvester$HarvestThread.run(OAIHarvester.java:1292) > at java.lang.Thread.run(Thread.java:619) > I have created a quick patch that ignore the authorization system when update > the collection. Probably, it isn't the best solution but it works. -- 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-536) Functional Test Framework for DSpace
[ https://jira.duraspace.org/browse/DS-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reassigned DS-536: --- Assignee: (was: Stuart Lewis) > Functional Test Framework for DSpace > > > Key: DS-536 > URL: https://jira.duraspace.org/browse/DS-536 > Project: DSpace > Issue Type: New Feature >Reporter: Scott Phillips >Priority: Major > Attachments: DSpace-1.5.2-FunctionalTest.patch.txt, > Dspace-1.5.2-FunctionalTest-V2.patch.txt > > > The Texas Digital Library has been focusing on testability for our projects. > Since DSpace is related too or part of most of our projects we've been > looking for a way to increase DSpace's testability. Traditionally this would > mean adding unit tests and integration tests. However as DSpace currently > stands is hard to break it up into individual components that can be tested > in isolation. You'll quickly find that writing tests for DSpace pull in the > entire system, plus databases, and a file system. To address this problem > we've created a simple framework for adding both integration tests and > functional tests which improve the reliability of our projects. I'm > interested to see if this is something the greater DSpace community would be > interested in? > The goals of our project were to create a mechanism where we could run > complete functional tests. Functional tests evaluate the entire system as the > end user would use it, so think of it as opening a web browser and evaluating > the output - but completely automated. They test everything all together. > Ideal it would be better to test each component individual, but this is in > practical for DSpace for two reasons 1) DSpace is highly integrated and > nearly impossible to separate from the database and file systems, 2) Creating > unit test for all of DSpace is very time consuming it is simpler to write a > few functional tests that cover a wide set of features over the whole > application. It gets you to a point where you can reliably verify the > software quicker. If you're working on unit tests for DSpace please do not > let this stand in your way. > The main concept is to script the install of a test DSpace, with a full > configuration and setup. Then we start DSpace in an embedded webserver and > then run through several scenarios just as a normal user would. This tests > the whole application, using a database, a file system, and a full build. The > ant script where you normally run "ant fresh_install" has a new target "ant > test". You pass it a few parameters such as what database to use. The script > will then run through a fresh install of DSpace into a local /test directory, > setup some communities and collections, and import some basic items. Then > JUnit-based tests are run against the embedded webserver using HtmlUnit to > simplify verifying the HTML output. > Here is how to run it. After compiling using a "mvn package", cd into > target/dspace-*-build.dir/ directory. Then run "ant test" you may need to > pass it some parameters as listed below. Each parameter has a default so if > you configure you're database connections the same way then it can be as > simple as running "ant test" without any parameters. > -Dtest.db.driver="org.postgresql.Driver" > -Dtest.db.url="jdbc:postgresql://localhost:5432/dspacetest" > -Dtest.db.username="dspacetest" > -Dtest.db.password="dspacetest" > -Dtest.dspace.dir="./test/" > -Dtest.config="./test/config/dspace.cfg" > We've used this approach rather successfully for two of our DSpace-based > projects here at TDL: an ETD submission system called vireo, and a learning > object repository. These projects haven't moved to 1.6 yet, but I do have a > patch available for DSpace 1.5.2. Most of the test cases we've created so far > are specific to the project we're working on. However the patch includes 4 > manakin tests, which are really just an example of how tests work within this > framework. -- 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-257) Item Import and Export, use of multiple metadata schema
[ https://jira.duraspace.org/browse/DS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reassigned DS-257: --- Assignee: (was: Stuart Lewis) > Item Import and Export, use of multiple metadata schema > --- > > Key: DS-257 > URL: https://jira.duraspace.org/browse/DS-257 > Project: DSpace > Issue Type: Improvement > Components: DSpace API >Affects Versions: 1.6.0 >Reporter: Claudia Jürgen >Priority: Major > Attachments: ItemImExport.patch > > > At the moment the item import of items with metadata from different metadata > schemata requires an extra metadata file per schema. > This patch enables the use of one metadata file which can hold metadata of > all schema both for import and export. > The new file is named (schema neutral) metadata.xml and got the structure > > > language="LANGUAGE">Foo > > ... > > A new command line option is introduced > -l for the use of the default language qualifier which defaults to not use it > This will avoid assigning unintentionally wrongly qualified metadata, as it > is often the case with DSpace instances which hold non en metainformation. > Furthermore this patch fixes DS-256 > http://jira.dspace.org/jira/browse/DS-256. > (The documentation will follow for the DSpace docs will follow.) -- 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-271) Make the OAI DC crosswalk configurable
[ https://jira.duraspace.org/browse/DS-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reassigned DS-271: --- Assignee: (was: Stuart Lewis) > Make the OAI DC crosswalk configurable > -- > > Key: DS-271 > URL: https://jira.duraspace.org/browse/DS-271 > Project: DSpace > Issue Type: Improvement > Components: DSpace API, OAI-PMH >Reporter: Andrea Bollini > Fix For: 1.6.0 > > Attachments: [DS-271]_Make_the_OAI_DC_crosswalk_configurable.patch, > oai_dc-configurable.patch > > > This patch makes configurable the oai_dc crosswalk so to make possible to > hide some metadata without hardcoding. > The configuration is read from a new oaidc.properties file in the config dir > with the follow syntax: > .(.) = OAI_DC ELEMENT > dc.title = title > dc.contributor.author(CONVERTER) = creator > dc.contributor.editor(CONVERTER) = contributor > ... > where the CONVERTER is the name of an option named plugin (interface class: > org.dspace.content.crosswalk.IConverter) that manipulate the string value > A default configuration, with the same behaviour of the "old" OAI_DC > crosswalk, is provided -- 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-1873) CheckSum Checker Emailer sends emails for 0 issues, doesn't specify any site info
Title: Message Title Stuart Lewis commented on an issue Re: CheckSum Checker Emailer sends emails for 0 issues, doesn't specify any site info I think part of the rationale for sending an email for 0 issues, is that the sys admin / repo manager knows that the checksum checker is working. They could go three years without receiving an email, and assume all is well, but actually they forgot to reinstate the checker cronjob at the last upgrade, and in the mean time have suffered some file corruption. But I agree daily is over the top. Could the rule be changed to something like (if errors < 0 OR day-of-month = 1) so that at least there is a periodic heartbeat of emails? Add Comment DSpace / DS-1873 CheckSum Checker Emailer sends emails for 0 issues, doesn't specify any site info When using the DSpace Checksum Checker Emailer ([dspace.dir]/bin/dspace checker-emailer), the "mail.admin" email address will receive a lot of emails with a subject of: "Checksum checker Report - 0 Bitstreams found with POSSIBLE issues" There's two problems with these email reports: (1) Often the majority of the emails report "0 Bitstreams". While... This message was sent by Atlassian JIRA (v6.1.1#6155-sha1:7188aee)
[Dspace-devel] [DuraSpace JIRA] (DS-1873) CheckSum Checker Emailer sends emails for 0 issues, doesn't specify any site info
Title: Message Title Stuart Lewis commented on an issue Re: CheckSum Checker Emailer sends emails for 0 issues, doesn't specify any site info Hi Tim, Thanks for the explanation, that all sounds great. I didn't want my comment to be a negative reaction to the suggested improvement, but was thinking aloud about enhancements to the emails to make them more useful - thanks for opening up the new JIRA ticket for that. Stuart Add Comment DSpace / DS-1873 CheckSum Checker Emailer sends emails for 0 issues, doesn't specify any site info When using the DSpace Checksum Checker Emailer ([dspace.dir]/bin/dspace checker-emailer), the "mail.admin" email address will receive a lot of emails with a subject of: "Checksum checker Report - 0 Bitstreams found with POSSIBLE issues" There's two problems with these email reports: (1) Often the majority of the emails report "0 Bitstreams". While... This message was sent by Atlassian JIRA (v6.1.1#6155-sha1:7188aee) -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, De
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-632) Batch Metadata Import needs to validate metadata fields specified in CSVs
[ https://jira.duraspace.org/browse/DS-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-632: Attachment: (was: [DS-632]_Batch_Metadata_Import_needs_to_validate_metadata_fields_specified_in_CSVs.patch) > Batch Metadata Import needs to validate metadata fields specified in CSVs > - > > Key: DS-632 > URL: https://jira.duraspace.org/browse/DS-632 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.6.0, 1.6.1, 1.6.2 > Environment: All >Reporter: Kim Shepherd >Assignee: Stuart Lewis >Priority: Major > Fix For: 1.7.0 > > Attachments: > [DS-632]_Batch_Metadata_Import_needs_to_validate_metadata_fields_specified_in_CSVs.patch > > > Batch metadata importer does not properly validate metadata fields specified > in the uploaded CSV. > If a user uploads a CSV with a non-existent metadata field name, changes will > be displayed as though the CSV were valid, then when the user confirms, they > will be told "No changes detected, 0 processed". > However, the items get ingested as completely empty items containing no > metadata, without being deleted from the uploader's workspace. > As a result, the administrator/uploader can not delete the item from the > collection (as there is an fkey reference to workspace_items) and can not > remove the item from the workspace, as there is a reference to > collection2item. Manual SQL queries must be run to completely remove the > object. > Proposed solution: Quick validation against metadata registries before > displaying confirmation of changes, and display an error if a field does not > exist or is invalid in some other way (formatting, rights, etc.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-632) Batch Metadata Import needs to validate metadata fields specified in CSVs
[ https://jira.duraspace.org/browse/DS-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-632: Attachment: [DS-632]_Batch_Metadata_Import_needs_to_validate_metadata_fields_specified_in_CSVs.patch Updated patch. XMLUI and JSPUI now display meaningful i18n'd messages > Batch Metadata Import needs to validate metadata fields specified in CSVs > - > > Key: DS-632 > URL: https://jira.duraspace.org/browse/DS-632 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.6.0, 1.6.1, 1.6.2 > Environment: All >Reporter: Kim Shepherd >Assignee: Stuart Lewis >Priority: Major > Fix For: 1.7.0 > > Attachments: > [DS-632]_Batch_Metadata_Import_needs_to_validate_metadata_fields_specified_in_CSVs.patch > > > Batch metadata importer does not properly validate metadata fields specified > in the uploaded CSV. > If a user uploads a CSV with a non-existent metadata field name, changes will > be displayed as though the CSV were valid, then when the user confirms, they > will be told "No changes detected, 0 processed". > However, the items get ingested as completely empty items containing no > metadata, without being deleted from the uploader's workspace. > As a result, the administrator/uploader can not delete the item from the > collection (as there is an fkey reference to workspace_items) and can not > remove the item from the workspace, as there is a reference to > collection2item. Manual SQL queries must be run to completely remove the > object. > Proposed solution: Quick validation against metadata registries before > displaying confirmation of changes, and display an error if a field does not > exist or is invalid in some other way (formatting, rights, etc.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-632) Batch Metadata Import needs to validate metadata fields specified in CSVs
[ https://jira.duraspace.org/browse/DS-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis resolved DS-632. - Resolution: Fixed Author: stuartlewis Date: Fri Oct 15 02:53:20 2010 New Revision: 5429 Log: [DS-632] Batch Metadata Import needs to validate metadata fields specified in CSVs > Batch Metadata Import needs to validate metadata fields specified in CSVs > - > > Key: DS-632 > URL: https://jira.duraspace.org/browse/DS-632 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.6.0, 1.6.1, 1.6.2 > Environment: All >Reporter: Kim Shepherd >Assignee: Stuart Lewis >Priority: Major > Fix For: 1.7.0 > > Attachments: > [DS-632]_Batch_Metadata_Import_needs_to_validate_metadata_fields_specified_in_CSVs.patch > > > Batch metadata importer does not properly validate metadata fields specified > in the uploaded CSV. > If a user uploads a CSV with a non-existent metadata field name, changes will > be displayed as though the CSV were valid, then when the user confirms, they > will be told "No changes detected, 0 processed". > However, the items get ingested as completely empty items containing no > metadata, without being deleted from the uploader's workspace. > As a result, the administrator/uploader can not delete the item from the > collection (as there is an fkey reference to workspace_items) and can not > remove the item from the workspace, as there is a reference to > collection2item. Manual SQL queries must be run to completely remove the > object. > Proposed solution: Quick validation against metadata registries before > displaying confirmation of changes, and display an error if a field does not > exist or is invalid in some other way (formatting, rights, etc.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Assigned: (DS-646) Remove /bin scripts (replaced by 'dspace' commmand)
[ https://jira.duraspace.org/browse/DS-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reassigned DS-646: --- Assignee: Jeffrey Trimble (was: Stuart Lewis) Changes made to DSpace bin's directory. Now to check all the documentation. > Remove /bin scripts (replaced by 'dspace' commmand) > --- > > Key: DS-646 > URL: https://jira.duraspace.org/browse/DS-646 > Project: DSpace > Issue Type: Task > Components: DSpace API >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2 >Reporter: Stuart Lewis >Assignee: Jeffrey Trimble > Fix For: 1.7.0 > > > Must also check documentation to ensure all references have been removed. > [08:52am] stuartlewis: Can I raise a quick question? In 1.6.1 we sort-of > deprecated the /bin scripts. Can we vote to remove them in 1.7? > [08:53am] stuartlewis: (just leave 'dspace', and any non-java scripts) > [08:53am] mhwood: If it's been announced already, and we make some more noise > as release approaches, I think we should do that. > [08:54am] bollini: I agree too > [08:54am] tdonohue: hi stuartlewis -- sure, we can vote on that... I'd be +1 > [08:54am] kgerbeitson: +1, definitely with noise > [08:54am] kshepherd: yep, +1 to removal and to more noise/documentation > [08:54am] richardrodgers: stuartlewis: can we replace them with clones that > say 'use dpsace'? > [08:55am] kshepherd: richardrodgers: hmm.. that's a good idea for people who > forget about old cronjobs, etc. > [08:55am] richardrodgers: (just to be a little friendlier about pulling the > rug out) > [08:55am] stuartlewis: richardrodgers: Maybe, but we've got to deprecate them > sometime, so it might just confuse people more? Maybe a clean cut is better? > Especially if people run these via cron, they might not see the warning > message. > [08:55am] richardrodgers: true - it might get lost > [08:55am] kshepherd: it it's stderr output, cron should email it > [08:55am] mhwood: If they don't see the message from a cron job, will they > see the job fail? > [08:56am] PeterDietz: also, are we changed the header code license to be a > bit more abbreviated > [08:56am] stuartlewis: So we're plus four (incl me) for dropping the scripts. > Any other votes? > [08:56am] tdonohue: I'd like to see us actually cut things off that we > 'deprecate', and just document/announce it broadly (we've been notoriously > bad about this in the past -- we've been releasing with a deprecated DCValue > class for years now) > [08:57am] richardrodgers: +1 ok with me > [08:57am] stuartlewis: Thanks - will get that done. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Reopened: (DS-603) Having a most used item list similar to the recent submissions
[ https://jira.duraspace.org/browse/DS-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reopened DS-603: - Hi Ben, This patch doesn't seem to work, based on a fresh checkout of trunk. The /statistics link is clashing with the 'classic' statistics link. (If I remove the statistics map:match from the artefact browser, then it works OK.) Also, there is an e.printStackTrace() in the patch, which probably isn't meant to be there? Cheers, Stuart > Having a most used item list similar to the recent submissions > -- > > Key: DS-603 > URL: https://jira.duraspace.org/browse/DS-603 > Project: DSpace > Issue Type: New Feature >Affects Versions: 1.6.2 >Reporter: Claudia Jürgen >Assignee: Ben Bosman > Fix For: 1.7.0 > > > Apart from the discussion which should be counted items views, bitstream > downloads, reusing the information to display > Top n item lists similar to the recent submissions would be great. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-588) Patch for SFX (OpenURL resolver)
[ https://jira.duraspace.org/browse/DS-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-588: Attachment: [DS-588]_Patch_for_SFX_(OpenURL_resolver).patch Latest patch - as committed on 20th October 2010 > Patch for SFX (OpenURL resolver) > -- > > Key: DS-588 > URL: https://jira.duraspace.org/browse/DS-588 > Project: DSpace > Issue Type: Improvement > Components: JSPUI, XMLUI >Affects Versions: 1.6.0 >Reporter: Yin Yin Latt >Assignee: Kim Shepherd >Priority: Major > Attachments: [DS-588]_Patch_for_SFX_(OpenURL_resolver).patch, > sfx-all.patch, sfx-ducumentation.doc > > > Customized SFX work for both JSP and XML version. (Patch create against 1.6) > Eg: http://researchspace.auckland.ac.nz/handle/2292/5763 > it is a bit different with original SFX in DSpace. Patch will update > following > 1. SFXLinkTag.java (for JSPUI) > 2. ItemViewer.java (for XMLUI) > 3. SFXFileReader.java (this is new api used by both JSP and XML) > 4. sfx.xml (new config file for sfx parameter and metadata mapping) > 5. DIM-handler.xsl and structural.xsl -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Assigned: (DS-588) Patch for SFX (OpenURL resolver)
[ https://jira.duraspace.org/browse/DS-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reassigned DS-588: --- Assignee: Jeffrey Trimble (was: Kim Shepherd) Patch committed, ready for documentation. Documentation doc attached. Thanks. > Patch for SFX (OpenURL resolver) > -- > > Key: DS-588 > URL: https://jira.duraspace.org/browse/DS-588 > Project: DSpace > Issue Type: Improvement > Components: JSPUI, XMLUI >Affects Versions: 1.6.0 >Reporter: Yin Yin Latt >Assignee: Jeffrey Trimble >Priority: Major > Attachments: [DS-588]_Patch_for_SFX_(OpenURL_resolver).patch, > sfx-all.patch, sfx-ducumentation.doc > > > Customized SFX work for both JSP and XML version. (Patch create against 1.6) > Eg: http://researchspace.auckland.ac.nz/handle/2292/5763 > it is a bit different with original SFX in DSpace. Patch will update > following > 1. SFXLinkTag.java (for JSPUI) > 2. ItemViewer.java (for XMLUI) > 3. SFXFileReader.java (this is new api used by both JSP and XML) > 4. sfx.xml (new config file for sfx parameter and metadata mapping) > 5. DIM-handler.xsl and structural.xsl -- 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] Created: (DS-713) dspace.log only logs remoteAddr, needs extending to include X-Forwarded-For
dspace.log only logs remoteAddr, needs extending to include X-Forwarded-For --- Key: DS-713 URL: https://jira.duraspace.org/browse/DS-713 Project: DSpace Issue Type: Improvement Components: JSPUI, XMLUI Affects Versions: 1.6.2, 1.6.1, 1.6.0, 1.5.2, 1.5.1, 1.5.0 Reporter: Stuart Lewis Assignee: Stuart Lewis Fix For: 1.7.0 If there is a proxy in front of a DSpace server, dspace.log will report the IP address to be that of the proxy. dspace-stats is OK, as it looks for the presence of an X-Forwarded-For header. dspace.log needs to do the same. Patch created, currently being tested. -- 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-713) dspace.log only logs remoteAddr, needs extending to include X-Forwarded-For
[ https://jira.duraspace.org/browse/DS-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-713: Status: Open (was: Received) > dspace.log only logs remoteAddr, needs extending to include X-Forwarded-For > --- > > Key: DS-713 > URL: https://jira.duraspace.org/browse/DS-713 > Project: DSpace > Issue Type: Improvement > Components: JSPUI, XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2 >Reporter: Stuart Lewis >Assignee: Stuart Lewis > Fix For: 1.7.0 > > > If there is a proxy in front of a DSpace server, dspace.log will report the > IP address to be that of the proxy. dspace-stats is OK, as it looks for the > presence of an X-Forwarded-For header. dspace.log needs to do the same. > Patch created, currently being tested. -- 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-713) dspace.log only logs remoteAddr, needs extending to include X-Forwarded-For
[ https://jira.duraspace.org/browse/DS-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-713: Attachment: [DS-713]_dspace_log_only_logs_remoteAddr,_needs_extending_to_include_X-Forwarded-For.patch Moves the useProxies config setting out of the solr stats section, and up to the logging section. It makes mention that it affects both general logging and solr stats. > dspace.log only logs remoteAddr, needs extending to include X-Forwarded-For > --- > > Key: DS-713 > URL: https://jira.duraspace.org/browse/DS-713 > Project: DSpace > Issue Type: Improvement > Components: JSPUI, XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2 >Reporter: Stuart Lewis >Assignee: Stuart Lewis > Fix For: 1.7.0 > > Attachments: > [DS-713]_dspace_log_only_logs_remoteAddr,_needs_extending_to_include_X-Forwarded-For.patch > > > If there is a proxy in front of a DSpace server, dspace.log will report the > IP address to be that of the proxy. dspace-stats is OK, as it looks for the > presence of an X-Forwarded-For header. dspace.log needs to do the same. > Patch created, currently being tested. -- 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] Commented: (DS-713) dspace.log only logs remoteAddr, needs extending to include X-Forwarded-For
[ https://jira.duraspace.org/browse/DS-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848#action_17848 ] Stuart Lewis commented on DS-713: - If there's no opposition, I'll get this committed in the next 24 hours or so. > dspace.log only logs remoteAddr, needs extending to include X-Forwarded-For > --- > > Key: DS-713 > URL: https://jira.duraspace.org/browse/DS-713 > Project: DSpace > Issue Type: Improvement > Components: JSPUI, XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2 >Reporter: Stuart Lewis >Assignee: Stuart Lewis > Fix For: 1.7.0 > > Attachments: > [DS-713]_dspace_log_only_logs_remoteAddr,_needs_extending_to_include_X-Forwarded-For.patch > > > If there is a proxy in front of a DSpace server, dspace.log will report the > IP address to be that of the proxy. dspace-stats is OK, as it looks for the > presence of an X-Forwarded-For header. dspace.log needs to do the same. > Patch created, currently being tested. -- 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] Commented: (DS-640) Interal System Error when browsing with wrong argument
[ https://jira.duraspace.org/browse/DS-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17849#action_17849 ] Stuart Lewis commented on DS-640: - I promised to outline the options that we have to fix this: 1) Throw a 404. This is probably safe for browse?type=foobar but it might cause problems if a search engine gets a 404 from /browse and removes all urls with that root from its index. 2) Respond with 200 OK and a useful error message. However this won't teach crawlers that the pages are bad. 3) Create a /browse index page that lists the possible browse indexes, and redirect bad browse requests to that page. 4) Respond with some other error message? a 50x code and an 'invalid browse index' message? 5) Other? Are there any preferences? > Interal System Error when browsing with wrong argument > -- > > Key: DS-640 > URL: https://jira.duraspace.org/browse/DS-640 > 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: Stuart Lewis >Priority: Major > > On Browsing Items: > If someone tries to use browse type for which browse index does not exist, > like browse=publisher > e.g. http://dspace.webinito.com/browse?type > OR > e.g. http://dspace.webinito.com/browse?type=xyz > You will get Internal System Error -- 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] Assigned: (DS-713) dspace.log only logs remoteAddr, needs extending to include X-Forwarded-For
[ https://jira.duraspace.org/browse/DS-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reassigned DS-713: --- Assignee: Jeffrey Trimble (was: Stuart Lewis) Now committed. Need documenting. What has changed is that the 'useProxies' setting now applies to dspace.log logging, as well as solr stats. Because logging comes first in the dspace.cfg file, I've moved that setting up there. > dspace.log only logs remoteAddr, needs extending to include X-Forwarded-For > --- > > Key: DS-713 > URL: https://jira.duraspace.org/browse/DS-713 > Project: DSpace > Issue Type: Improvement > Components: JSPUI, XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2 >Reporter: Stuart Lewis >Assignee: Jeffrey Trimble > Fix For: 1.7.0 > > Attachments: > [DS-713]_dspace_log_only_logs_remoteAddr,_needs_extending_to_include_X-Forwarded-For.patch > > > If there is a proxy in front of a DSpace server, dspace.log will report the > IP address to be that of the proxy. dspace-stats is OK, as it looks for the > presence of an X-Forwarded-For header. dspace.log needs to do the same. > Patch created, currently being tested. -- 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] Resolved: (DS-713) dspace.log only logs remoteAddr, needs extending to include X-Forwarded-For
[ https://jira.duraspace.org/browse/DS-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis resolved DS-713. - Documentation Status: Complete or Committed (was: Needed) Resolution: Fixed Wiki documentation updated. Also updated the solr stats docs to mention that the useProxies setting is now n the logging section. > dspace.log only logs remoteAddr, needs extending to include X-Forwarded-For > --- > > Key: DS-713 > URL: https://jira.duraspace.org/browse/DS-713 > Project: DSpace > Issue Type: Improvement > Components: JSPUI, XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2 >Reporter: Stuart Lewis >Assignee: Stuart Lewis > Fix For: 1.7.0 > > Attachments: > [DS-713]_dspace_log_only_logs_remoteAddr,_needs_extending_to_include_X-Forwarded-For.patch > > > If there is a proxy in front of a DSpace server, dspace.log will report the > IP address to be that of the proxy. dspace-stats is OK, as it looks for the > presence of an X-Forwarded-For header. dspace.log needs to do the same. > Patch created, currently being tested. -- 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] Assigned: (DS-713) dspace.log only logs remoteAddr, needs extending to include X-Forwarded-For
[ https://jira.duraspace.org/browse/DS-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reassigned DS-713: --- Assignee: Stuart Lewis (was: Jeffrey Trimble) > dspace.log only logs remoteAddr, needs extending to include X-Forwarded-For > --- > > Key: DS-713 > URL: https://jira.duraspace.org/browse/DS-713 > Project: DSpace > Issue Type: Improvement > Components: JSPUI, XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2 >Reporter: Stuart Lewis >Assignee: Stuart Lewis > Fix For: 1.7.0 > > Attachments: > [DS-713]_dspace_log_only_logs_remoteAddr,_needs_extending_to_include_X-Forwarded-For.patch > > > If there is a proxy in front of a DSpace server, dspace.log will report the > IP address to be that of the proxy. dspace-stats is OK, as it looks for the > presence of an X-Forwarded-For header. dspace.log needs to do the same. > Patch created, currently being tested. -- 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] Closed: (DS-725) Installation instructions for Windows is out of date.
[ https://jira.duraspace.org/browse/DS-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis closed DS-725. --- Resolution: Duplicate Duplicate of DS-646. DS-646 is still open for the documentation to be updated. If you find any specific examples that are out of date in https://wiki.duraspace.org/display/DSDOC/DSpace+Documentation please feel free to update them. I suspect there will be a lot of references that need updating, so many eyes will help. Cheers, Stuart > Installation instructions for Windows is out of date. > - > > Key: DS-725 > URL: https://jira.duraspace.org/browse/DS-725 > Project: DSpace > Issue Type: Documentation >Affects Versions: 1.7.0 >Reporter: Robin Taylor > > The installation instructions for Windows still instructs the user to run... > [dspace]\bin\dsrun org.dspace.administer.CreateAdministrator > .. but dsrun.bat no longer exists. The instructions need to be brought in > line with those for Unix installs. -- 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] Created: (DS-735) Allow IPAuthentcation to work with proxies (examine X-Forwarded-For header)
Allow IPAuthentcation to work with proxies (examine X-Forwarded-For header) --- Key: DS-735 URL: https://jira.duraspace.org/browse/DS-735 Project: DSpace Issue Type: Improvement Components: DSpace API, JSPUI, XMLUI Affects Versions: 1.6.2, 1.6.1, 1.6.0, 1.5.2, 1.5.1, 1.5.0 Reporter: Stuart Lewis Assignee: Stuart Lewis Fix For: 1.7.0 IPAuthentication looks at the remote address header to get the IP address, but this fails if a proxy is being used. If this is the case, as with solr stats and log4j logging, we need to look at the X-Forwarded-For header. -- 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-735) Allow IPAuthentcation to work with proxies (examine X-Forwarded-For header)
[ https://jira.duraspace.org/browse/DS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-735: Status: Open (was: Received) > Allow IPAuthentcation to work with proxies (examine X-Forwarded-For header) > --- > > Key: DS-735 > URL: https://jira.duraspace.org/browse/DS-735 > Project: DSpace > Issue Type: Improvement > Components: DSpace API, JSPUI, XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2 >Reporter: Stuart Lewis >Assignee: Stuart Lewis > Fix For: 1.7.0 > > > IPAuthentication looks at the remote address header to get the IP address, > but this fails if a proxy is being used. If this is the case, as with solr > stats and log4j logging, we need to look at the X-Forwarded-For header. -- 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-735) Allow IPAuthentcation to work with proxies (examine X-Forwarded-For header)
[ https://jira.duraspace.org/browse/DS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-735: Attachment: [DS-735]_Allow_IPAuthentcation_to_work_with_proxies_(examine_X-Forwarded-For_header)_.patch > Allow IPAuthentcation to work with proxies (examine X-Forwarded-For header) > --- > > Key: DS-735 > URL: https://jira.duraspace.org/browse/DS-735 > Project: DSpace > Issue Type: Improvement > Components: DSpace API, JSPUI, XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2 >Reporter: Stuart Lewis >Assignee: Stuart Lewis > Fix For: 1.7.0 > > Attachments: > [DS-735]_Allow_IPAuthentcation_to_work_with_proxies_(examine_X-Forwarded-For_header)_.patch > > > IPAuthentication looks at the remote address header to get the IP address, > but this fails if a proxy is being used. If this is the case, as with solr > stats and log4j logging, we need to look at the X-Forwarded-For header. -- 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] Resolved: (DS-735) Allow IPAuthentcation to work with proxies (examine X-Forwarded-For header)
[ https://jira.duraspace.org/browse/DS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis resolved DS-735. - Documentation Status: Complete or Committed (was: Needed) Resolution: Fixed Added documentation in the 1.7 dspace doc wiki pages. > Allow IPAuthentcation to work with proxies (examine X-Forwarded-For header) > --- > > Key: DS-735 > URL: https://jira.duraspace.org/browse/DS-735 > Project: DSpace > Issue Type: Improvement > Components: DSpace API, JSPUI, XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2 >Reporter: Stuart Lewis >Assignee: Stuart Lewis > Fix For: 1.7.0 > > Attachments: > [DS-735]_Allow_IPAuthentcation_to_work_with_proxies_(examine_X-Forwarded-For_header)_.patch > > > IPAuthentication looks at the remote address header to get the IP address, > but this fails if a proxy is being used. If this is the case, as with solr > stats and log4j logging, we need to look at the X-Forwarded-For header. -- 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-740) Allow media filter to set non-default permissions on derivative bitstreams
[ https://jira.duraspace.org/browse/DS-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-740: Status: Open (was: Received) > Allow media filter to set non-default permissions on derivative bitstreams > -- > > Key: DS-740 > URL: https://jira.duraspace.org/browse/DS-740 > Project: DSpace > Issue Type: New Feature > Components: DSpace API >Reporter: Stuart Lewis > > At present, derivative bitstreams created by filter-media all take on the > authZ policies of their parent item. In some cases, such as locked images, > the thumbnail could still be open. > From a recent thread on dspace-tech. It seems as if this would make a useful > feature if we can agree on a set of requirements: > Hi George, > Thanks for your reply. Do you have open access to any of your content or is > it all restricted? We have a mix which makes running the filter-media etc > scripts interesting. > Ideally the solution would be to set permissions at a collection level for > each of the types of bundles. The item permissions would then inherit from > the collection, or override if policies are set on individual items.. I don't > seem to be able to do that (1.5). > For reference, heres the (cutdown) SQL. This will update all thumbnail > bitstream policies and set them to anonymous. We only had to do it for one > group though. If you want to update intermediates, change THUMBNAIL to > BRANDED_PREVIEW. > update resourcepolicy > set epersongroup_id=0 > where policy_id in ( > select > rp.policy_id > from > resourcepolicy rp, > bundle2bitstream bb, > bundle b > where > b.name='THUMBNAIL' > and b.bundle_id=bb.bundle_id > and bb.bitstream_id=rp.resource_id > ); > cheers, > Steve > On 04/11/2010, at 11:59 PM, George Stanley Kozak wrote: > Steve: > This is the way that thumbnails have worked for me at my site (we have been > using DSpace since 2003). It can be frustrating. Your solution is > interesting. I never thought about going into SQL to update the policies on > the thumbnail bundles. I am not sure if there are any other solutions. > George Kozak > Digital Library Specialist > Cornell University Library Information Technologies (CUL-IT) > 501 Olin Library > Cornell University > Ithaca, NY 14853 > 607-255-8924 > -Original Message- > From: Steve Swinsburg [mailto:steve.swinsb...@gmail.com] > Sent: Wednesday, November 03, 2010 9:39 PM > To: dspace-t...@lists.sourceforge.net > Subject: Re: [Dspace-tech] thumbnails restricted if main item is restricted > We've fixed this up with some carefully crafted SQL to update the policies to > the Anonymous group for the bitstreams in the thumbnail bundles, but it would > be interesting to know if this is actually how things are meant to work, ie > inherit the permissions from the parent item when generating the thumbnails. > regards, > Steve > On 04/11/2010, at 10:53 AM, Steve Swinsburg wrote: > Hi, > We have a situation where some items in a collection are restricted, ie you > need to login to access the full version. However we want the thumbnails and > branded previews to still show up for the general public. > When we run the thumbnail generator, it seems to inherit the permissions from > the main bitstream, which means if the bitstream is protected, the thumbnail > doesn't show up unless you are logged in and have the appropriate permission. > Is this a common situation? We've inherited this instance so it might be a > change made by people before us, but if anyone has addressed this, it would > be great to hear from you. > thanks, > Steve -- 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-740) Allow media filter to set non-default permissions on derivative bitstreams
Allow media filter to set non-default permissions on derivative bitstreams -- Key: DS-740 URL: https://jira.duraspace.org/browse/DS-740 Project: DSpace Issue Type: New Feature Components: DSpace API Reporter: Stuart Lewis At present, derivative bitstreams created by filter-media all take on the authZ policies of their parent item. In some cases, such as locked images, the thumbnail could still be open. >From a recent thread on dspace-tech. It seems as if this would make a useful >feature if we can agree on a set of requirements: Hi George, Thanks for your reply. Do you have open access to any of your content or is it all restricted? We have a mix which makes running the filter-media etc scripts interesting. Ideally the solution would be to set permissions at a collection level for each of the types of bundles. The item permissions would then inherit from the collection, or override if policies are set on individual items.. I don't seem to be able to do that (1.5). For reference, heres the (cutdown) SQL. This will update all thumbnail bitstream policies and set them to anonymous. We only had to do it for one group though. If you want to update intermediates, change THUMBNAIL to BRANDED_PREVIEW. update resourcepolicy set epersongroup_id=0 where policy_id in ( select rp.policy_id from resourcepolicy rp, bundle2bitstream bb, bundle b where b.name='THUMBNAIL' and b.bundle_id=bb.bundle_id and bb.bitstream_id=rp.resource_id ); cheers, Steve On 04/11/2010, at 11:59 PM, George Stanley Kozak wrote: Steve: This is the way that thumbnails have worked for me at my site (we have been using DSpace since 2003). It can be frustrating. Your solution is interesting. I never thought about going into SQL to update the policies on the thumbnail bundles. I am not sure if there are any other solutions. George Kozak Digital Library Specialist Cornell University Library Information Technologies (CUL-IT) 501 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 -Original Message- From: Steve Swinsburg [mailto:steve.swinsb...@gmail.com] Sent: Wednesday, November 03, 2010 9:39 PM To: dspace-t...@lists.sourceforge.net Subject: Re: [Dspace-tech] thumbnails restricted if main item is restricted We've fixed this up with some carefully crafted SQL to update the policies to the Anonymous group for the bitstreams in the thumbnail bundles, but it would be interesting to know if this is actually how things are meant to work, ie inherit the permissions from the parent item when generating the thumbnails. regards, Steve On 04/11/2010, at 10:53 AM, Steve Swinsburg wrote: Hi, We have a situation where some items in a collection are restricted, ie you need to login to access the full version. However we want the thumbnails and branded previews to still show up for the general public. When we run the thumbnail generator, it seems to inherit the permissions from the main bitstream, which means if the bitstream is protected, the thumbnail doesn't show up unless you are logged in and have the appropriate permission. Is this a common situation? We've inherited this instance so it might be a change made by people before us, but if anyone has addressed this, it would be great to hear from you. thanks, Steve -- 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-738) sword.cfg seems no longer used after 1.5
[ https://jira.duraspace.org/browse/DS-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-738: Documentation Status: In Comments (was: Needed) Assignee: Stuart Lewis Status: Open (was: Received) > sword.cfg seems no longer used after 1.5 > > > Key: DS-738 > URL: https://jira.duraspace.org/browse/DS-738 > Project: DSpace > Issue Type: Code Task >Affects Versions: 1.6.0, 1.6.1, 1.6.2 >Reporter: Bill Hays >Assignee: Stuart Lewis > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Sword configuration is now located in dspace.cfg. Is there a reason not to > delete sword.cfg from trunk? There is also brief mention of sword.cfg in the > sword module's README.txt which would need to be edited if it is deleted. -- 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-738) sword.cfg seems no longer used after 1.5
[ https://jira.duraspace.org/browse/DS-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-738: Attachment: [DS-738]_sword_cfg_seems_no_longer_used_after_1_5.patch > sword.cfg seems no longer used after 1.5 > > > Key: DS-738 > URL: https://jira.duraspace.org/browse/DS-738 > Project: DSpace > Issue Type: Code Task >Affects Versions: 1.6.0, 1.6.1, 1.6.2 >Reporter: Bill Hays >Assignee: Stuart Lewis > Fix For: 1.7.0 > > Attachments: [DS-738]_sword_cfg_seems_no_longer_used_after_1_5.patch > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Sword configuration is now located in dspace.cfg. Is there a reason not to > delete sword.cfg from trunk? There is also brief mention of sword.cfg in the > sword module's README.txt which would need to be edited if it is deleted. -- 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] Resolved: (DS-738) sword.cfg seems no longer used after 1.5
[ https://jira.duraspace.org/browse/DS-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis resolved DS-738. - Documentation Status: Not Required (was: In Comments) Resolution: Fixed Fix Version/s: 1.7.0 > sword.cfg seems no longer used after 1.5 > > > Key: DS-738 > URL: https://jira.duraspace.org/browse/DS-738 > Project: DSpace > Issue Type: Code Task >Affects Versions: 1.6.0, 1.6.1, 1.6.2 >Reporter: Bill Hays >Assignee: Stuart Lewis > Fix For: 1.7.0 > > Attachments: [DS-738]_sword_cfg_seems_no_longer_used_after_1_5.patch > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Sword configuration is now located in dspace.cfg. Is there a reason not to > delete sword.cfg from trunk? There is also brief mention of sword.cfg in the > sword module's README.txt which would need to be edited if it is deleted. -- 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] Resolved: (DS-268) XMLUI Item Mapper cannot handle multiple words in search box
[ https://jira.duraspace.org/browse/DS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis resolved DS-268. - Resolution: Fixed Fix Version/s: 1.7.0 Assignee: Stuart Lewis Thanks for the patch Andrea. This is now in DSpace 1.7. > XMLUI Item Mapper cannot handle multiple words in search box > > > Key: DS-268 > URL: https://jira.duraspace.org/browse/DS-268 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.5.1, 1.5.2 >Reporter: Tim Donohue >Assignee: Stuart Lewis > Fix For: 1.7.0 > > Attachments: administrative.js, DS-268.patch > > > When searching in the XMLUI Item Mapper, multiple words (with a space in > between) always returns no results. > It seems like it could be an encoding problem, as inserting a plus symbol (+) > in place of a space will return results. > So, for example: > A search on "my topic" (no quotes) will always return no results (even if > there are matches). But, a search on "my+topic" (no quotes) will return the > correct number of results. -- 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 -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-525) Move item - inherit default policies of destination collection
[ https://jira.duraspace.org/browse/DS-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-525: Attachment: [DS-525]_Move_item_-_inherit_default_policies_of_destination_collection_5827.patch Second version of the patch - same as before, but against trunk revision 5827, as a lot of code has changed since the patch was first written. > Move item - inherit default policies of destination collection > -- > > Key: DS-525 > URL: https://jira.duraspace.org/browse/DS-525 > Project: DSpace > Issue Type: New Feature > Components: DSpace API, JSPUI, XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0 >Reporter: Stuart Lewis >Priority: Major > Fix For: 1.7.0 > > Attachments: > [DS-525]_Move_item_-_inherit_default_policies_of_destination_collection.patch, > > [DS-525]_Move_item_-_inherit_default_policies_of_destination_collection_5827.patch > > > When using the UI to move an item, the item is moved, and it takes its authZ > policies with it, > However, a common use case is to move an item from a dark collection, to an > open collection. In this case, it is desired behaviour for the authZ policies > to be updated to the default policies of the destination collection. > This patch gives a new checkbox for jspui and xmlui to allow the destination > policy to be inherited. By default the checkbox is unchecked. > The API has been updated to add this as a boolean option on the Item.moveItem > method. > The patch also fixes two bugs with the xmlui move item function: > 1) When selecting which collection to move the item to, the collection that > is is currently in is no longer listed. > 2) Previously a new authZ policy was added to the item to allow the admin to > move the item. This was not removed once the item had been moved. If an item > was moved multiple times, lots of these policies were left in the item. > Instead, the patch updates it to set a temporary action allowing this, rather > than a policy. -- 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 -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-525) Move item - inherit default policies of destination collection
[ https://jira.duraspace.org/browse/DS-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis resolved DS-525. - Documentation Status: Complete or Committed (was: Needed) Resolution: Fixed Assignee: Stuart Lewis Added documentation, with warning about embargoes: https://wiki.duraspace.org/pages/diffpages.action?pageId=22022835&originalId=22547177 > Move item - inherit default policies of destination collection > -- > > Key: DS-525 > URL: https://jira.duraspace.org/browse/DS-525 > Project: DSpace > Issue Type: New Feature > Components: DSpace API, JSPUI, XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0 >Reporter: Stuart Lewis >Assignee: Stuart Lewis >Priority: Major > Fix For: 1.7.0 > > Attachments: > [DS-525]_Move_item_-_inherit_default_policies_of_destination_collection.patch, > > [DS-525]_Move_item_-_inherit_default_policies_of_destination_collection_5827.patch > > > When using the UI to move an item, the item is moved, and it takes its authZ > policies with it, > However, a common use case is to move an item from a dark collection, to an > open collection. In this case, it is desired behaviour for the authZ policies > to be updated to the default policies of the destination collection. > This patch gives a new checkbox for jspui and xmlui to allow the destination > policy to be inherited. By default the checkbox is unchecked. > The API has been updated to add this as a boolean option on the Item.moveItem > method. > The patch also fixes two bugs with the xmlui move item function: > 1) When selecting which collection to move the item to, the collection that > is is currently in is no longer listed. > 2) Previously a new authZ policy was added to the item to allow the admin to > move the item. This was not removed once the item had been moved. If an item > was moved multiple times, lots of these policies were left in the item. > Instead, the patch updates it to set a temporary action allowing this, rather > than a policy. -- 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 -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-753) Fix CSV parsing that got broken by refactoring
Fix CSV parsing that got broken by refactoring -- Key: DS-753 URL: https://jira.duraspace.org/browse/DS-753 Project: DSpace Issue Type: Bug Components: DSpace API Affects Versions: 1.7.0 Reporter: Stuart Lewis Assignee: Stuart Lewis Priority: Critical Fix For: 1.7.0 See uservoice comments from .7 testathon -- 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-753) Fix CSV parsing that got broken by refactoring
[ https://jira.duraspace.org/browse/DS-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-753: Status: Open (was: Received) > Fix CSV parsing that got broken by refactoring > -- > > Key: DS-753 > URL: https://jira.duraspace.org/browse/DS-753 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.7.0 >Reporter: Stuart Lewis >Assignee: Stuart Lewis >Priority: Critical > Fix For: 1.7.0 > > > See uservoice comments from .7 testathon -- 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-753) Fix CSV parsing that got broken by refactoring
[ https://jira.duraspace.org/browse/DS-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis resolved DS-753. - Resolution: Fixed > Fix CSV parsing that got broken by refactoring > -- > > Key: DS-753 > URL: https://jira.duraspace.org/browse/DS-753 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.7.0 >Reporter: Stuart Lewis >Assignee: Stuart Lewis >Priority: Critical > Fix For: 1.7.0 > > > See uservoice comments from .7 testathon -- 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-643) New testing framework (GSoC 2010)
[ https://jira.duraspace.org/browse/DS-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis resolved DS-643. - Resolution: Fixed > New testing framework (GSoC 2010) > - > > Key: DS-643 > URL: https://jira.duraspace.org/browse/DS-643 > Project: DSpace > Issue Type: New Feature > Components: DSpace API >Reporter: Stuart Lewis >Assignee: Stuart Lewis >Priority: Major > Fix For: 1.7.0 > > Attachments: DS-643.patch > > > A new testing framework for DSpace, built by Pere Villega as part of the 2010 > Google Summer of Code. > See: > - > https://wiki.duraspace.org/display/DSPACE/GSOC10+-+Add+Unit+Testing+to+Dspace -- 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-652) Wrong behaviour of special groups at login. Use only special groups of the authetication that DID authenticate the user.
[
https://jira.duraspace.org/browse/DS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18332#action_18332
]
Stuart Lewis commented on DS-652:
-
LDAPAuthentication getSpecialGroups looks like it should work ok, as it
contains the following check before setting the special groups:
if (!context.getCurrentUser().getNetid().equals(""))
The only problem might be if a user has authenticated with a method other than
LDAP where the netid is used and set.
> Wrong behaviour of special groups at login. Use only special groups of the
> authetication that DID authenticate the user.
>
>
> Key: DS-652
> URL: https://jira.duraspace.org/browse/DS-652
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
>Affects Versions: 1.6.0
>Reporter: Flávio Botelho
>Priority: Major
> Attachments: Fix_behaviour_of_autentication_specialGroups.patch
>
>
> We have internal users autheticating thru LDAP. And external users are still
> able to create new users.
> Unfortunally the authentication is putting all external users created thru
> the Login Authentication also in the ldap.login.specialgroup, of course that
> is not expected.
> Looking at code at AuthenticationManager it becomes clear that it is adding
> ALL the special groups of ALL the possible authentication mechanism, which
> doesnt make any sense whatsoever...
> It should only add special groups of the authentication mechanism that DID
> authenticate the user.
--
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
--
Oracle to DB2 Conversion Guide: Compatibility Made Easier than Ever Before
New IBM DB2 features make compatibility easy. In this guide, you'll learn
about native support for PL/SQL, new data types, scalar functions, improved
concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-652) Wrong behaviour of special groups at login. Use only special groups of the authetication that DID authenticate the user.
[
https://jira.duraspace.org/browse/DS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18337#action_18337
]
Stuart Lewis commented on DS-652:
-
Hi Flávio,
That's right - this is caught, and is taken to show that they do not have a
netid set. It isn't the prettiest of code, but should work.
catch (Exception npe) {
// The user is not an LDAP user, so we don't need to worry about them
}
return new int[0];
> Wrong behaviour of special groups at login. Use only special groups of the
> authetication that DID authenticate the user.
>
>
> Key: DS-652
> URL: https://jira.duraspace.org/browse/DS-652
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
>Affects Versions: 1.6.0
>Reporter: Flávio Botelho
>Priority: Major
> Attachments: Fix_behaviour_of_autentication_specialGroups.patch
>
>
> We have internal users autheticating thru LDAP. And external users are still
> able to create new users.
> Unfortunally the authentication is putting all external users created thru
> the Login Authentication also in the ldap.login.specialgroup, of course that
> is not expected.
> Looking at code at AuthenticationManager it becomes clear that it is adding
> ALL the special groups of ALL the possible authentication mechanism, which
> doesnt make any sense whatsoever...
> It should only add special groups of the authentication mechanism that DID
> authenticate the user.
--
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 happens now with your Lotus Notes apps - do you make another costly
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-779) Upgrade steps (1.5->1.6) need reordering
[ https://jira.duraspace.org/browse/DS-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-779: Status: Open (was: Received) > Upgrade steps (1.5->1.6) need reordering > > > Key: DS-779 > URL: https://jira.duraspace.org/browse/DS-779 > Project: DSpace > Issue Type: Documentation > Components: Documentation >Affects Versions: 1.6.0, 1.6.1, 1.6.2 >Reporter: Stuart Lewis > Fix For: 1.7.0 > > > In the 1.5.x -> 1.6.x upgrade steps, step 7 (upgrade the format registry for > creative commons mime types) needs moving slightly later, after the 'ant > upgrade' step. -- 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 -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-779) Upgrade steps (1.5->1.6) need reordering
Upgrade steps (1.5->1.6) need reordering Key: DS-779 URL: https://jira.duraspace.org/browse/DS-779 Project: DSpace Issue Type: Documentation Components: Documentation Affects Versions: 1.6.2, 1.6.1, 1.6.0 Reporter: Stuart Lewis Fix For: 1.7.0 In the 1.5.x -> 1.6.x upgrade steps, step 7 (upgrade the format registry for creative commons mime types) needs moving slightly later, after the 'ant upgrade' step. -- 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 -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-779) Upgrade steps (1.5->1.6) need reordering
[ https://jira.duraspace.org/browse/DS-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18405#action_18405 ] Stuart Lewis commented on DS-779: - Another related issue: Another typo in the same place: -f /dspace-1.6-1-src-release/dspace/etc/postgres/database_schema_15_16.sql should be -f /dspace-1.6-1-src-release/dspace/etc/postgres/database_schema_15-16.sql Stuart - Thanks for your help! Jason Jason Stirnaman Biomedical Librarian, Digital Projects A.R. Dykes Library, University of Kansas Medical Center jstirna...@kumc.edu 913-588-7319 > Upgrade steps (1.5->1.6) need reordering > > > Key: DS-779 > URL: https://jira.duraspace.org/browse/DS-779 > Project: DSpace > Issue Type: Documentation > Components: Documentation >Affects Versions: 1.6.0, 1.6.1, 1.6.2 >Reporter: Stuart Lewis > Fix For: 1.7.0 > > > In the 1.5.x -> 1.6.x upgrade steps, step 7 (upgrade the format registry for > creative commons mime types) needs moving slightly later, after the 'ant > upgrade' step. -- 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 -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-806) Item.match() incorrect logic for schema testing
Item.match() incorrect logic for schema testing
---
Key: DS-806
URL: https://jira.duraspace.org/browse/DS-806
Project: DSpace
Issue Type: Bug
Components: DSpace API
Affects Versions: 1.7.0, 1.6.2, 1.6.1, 1.6.0, 1.5.2, 1.5.1, 1.5.0
Reporter: Stuart Lewis
Priority: Blocker
Fix For: 1.7.1
Item.match(String schema, String element, String qualifier, String language,
DCValue dcv) contains the following code:
if (language == null)
{
// Value must be null language to match
if (dcv.language != null)
{
// Value is qualified, so no match
return false;
}
}
else if (!language.equals(Item.ANY))
{
// Not a wildcard, so language must match exactly
if (!language.equals(dcv.language))
{
return false;
}
}
else if (!schema.equals(Item.ANY))
{
if (dcv.schema != null && !dcv.schema.equals(schema))
{
// The namespace doesn't match
return false;
}
}
Therefore, the schema is not being checked if the language of the metadata
field is empty (null) or set to Item.ANY. This leads to the following case:
dc.type = foo
dc2.type = bar
MyItem.getMetadata("dc", "type", null, null) should return 1 result 'foo'.
Instead, it returns 'foo' and 'bar'.
To fix, change the 'else if' for the 'else if (language == null)' to 'if
(language == null)'.
--
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-806) Item.match() incorrect logic for schema testing
[
https://jira.duraspace.org/browse/DS-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart Lewis updated DS-806:
Attachment: [DS-806]_junit_test.patch
Patch included with a test (and update to the test dublin-core-types.xml to add
a dc2 schema, and a dc2.type element) which should fail. If you make the
correction (remove the else), it should then pass.
> Item.match() incorrect logic for schema testing
> ---
>
> Key: DS-806
> URL: https://jira.duraspace.org/browse/DS-806
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
>Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0
>Reporter: Stuart Lewis
>Priority: Blocker
> Fix For: 1.7.1
>
> Attachments: [DS-806]_junit_test.patch
>
>
> Item.match(String schema, String element, String qualifier, String language,
> DCValue dcv) contains the following code:
> if (language == null)
> {
> // Value must be null language to match
> if (dcv.language != null)
> {
> // Value is qualified, so no match
> return false;
> }
> }
> else if (!language.equals(Item.ANY))
> {
> // Not a wildcard, so language must match exactly
> if (!language.equals(dcv.language))
> {
> return false;
> }
> }
> else if (!schema.equals(Item.ANY))
> {
> if (dcv.schema != null && !dcv.schema.equals(schema))
> {
> // The namespace doesn't match
> return false;
> }
> }
> Therefore, the schema is not being checked if the language of the metadata
> field is empty (null) or set to Item.ANY. This leads to the following case:
> dc.type = foo
> dc2.type = bar
> MyItem.getMetadata("dc", "type", null, null) should return 1 result 'foo'.
> Instead, it returns 'foo' and 'bar'.
> To fix, change the 'else if' for the 'else if (language == null)' to 'if
> (language == null)'.
--
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-806) Item.match() incorrect logic for schema testing
[
https://jira.duraspace.org/browse/DS-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart Lewis updated DS-806:
Description:
Item.match(String schema, String element, String qualifier, String language,
DCValue dcv) contains the following code:
if (language == null)
{
// Value must be null language to match
if (dcv.language != null)
{
// Value is qualified, so no match
return false;
}
}
else if (!language.equals(Item.ANY))
{
// Not a wildcard, so language must match exactly
if (!language.equals(dcv.language))
{
return false;
}
}
else if (!schema.equals(Item.ANY))
{
if (dcv.schema != null && !dcv.schema.equals(schema))
{
// The namespace doesn't match
return false;
}
}
Therefore, the schema is not being checked if the language of the metadata
field is empty (null) or set to Item.ANY. This leads to the following case:
dc.type = foo
dc2.type = bar
MyItem.getMetadata("dc", "type", null, null) should return 1 result 'foo'.
Instead, it returns 'foo' and 'bar'.
To fix, change the 'else if' for the ' else if (!schema.equals(Item.ANY))' to
'if (!schema.equals(Item.ANY))'.
was:
Item.match(String schema, String element, String qualifier, String language,
DCValue dcv) contains the following code:
if (language == null)
{
// Value must be null language to match
if (dcv.language != null)
{
// Value is qualified, so no match
return false;
}
}
else if (!language.equals(Item.ANY))
{
// Not a wildcard, so language must match exactly
if (!language.equals(dcv.language))
{
return false;
}
}
else if (!schema.equals(Item.ANY))
{
if (dcv.schema != null && !dcv.schema.equals(schema))
{
// The namespace doesn't match
return false;
}
}
Therefore, the schema is not being checked if the language of the metadata
field is empty (null) or set to Item.ANY. This leads to the following case:
dc.type = foo
dc2.type = bar
MyItem.getMetadata("dc", "type", null, null) should return 1 result 'foo'.
Instead, it returns 'foo' and 'bar'.
To fix, change the 'else if' for the 'else if (language == null)' to 'if
(language == null)'.
> Item.match() incorrect logic for schema testing
> ---
>
> Key: DS-806
> URL: https://jira.duraspace.org/browse/DS-806
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
>Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0
>Reporter: Stuart Lewis
>Priority: Blocker
> Fix For: 1.7.1
>
> Attachments: [DS-806]_junit_test.patch
>
>
> Item.match(String schema, String element, String qualifier, String language,
> DCValue dcv) contains the following code:
> if (language == null)
> {
> // Value must be null language to match
> if (dcv.language != null)
> {
> // Value is qualified, so no match
> return false;
> }
> }
> else if (!language.equals(Item.ANY))
> {
> // Not a wildcard, so language must match exactly
> if (!language.equals(dcv.language))
> {
> return false;
> }
> }
> else if (!schema.equals(Item.ANY))
> {
> if (dcv.schema != null && !dcv.schema.equals(schema))
> {
> // The namespace doesn't match
> return false;
> }
> }
> Therefore, the schema is not being checked if the language of the metadata
> field is empty (null) or set to Item.ANY. This leads to the following case:
> dc.type = foo
> dc2.type = bar
> MyItem.getMetadata("dc", "type", null, null) should return 1 result 'foo'.
> Instead, it returns 'foo' and 'bar'.
> To fix, change the 'else if' for the ' else if (!schema.equals(Item.ANY))' to
> 'if (!schema.equals(Item.ANY))'.
--
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-fre
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-806) Item.match() incorrect logic for schema testing
[
https://jira.duraspace.org/browse/DS-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18718#action_18718
]
Stuart Lewis commented on DS-806:
-
Hi Tim - thanks for your comment. Yes: I messed up the description! I've
corrected it now.
Thanks, Stuart
> Item.match() incorrect logic for schema testing
> ---
>
> Key: DS-806
> URL: https://jira.duraspace.org/browse/DS-806
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
>Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0
>Reporter: Stuart Lewis
>Priority: Blocker
> Fix For: 1.7.1
>
> Attachments: [DS-806]_junit_test.patch
>
>
> Item.match(String schema, String element, String qualifier, String language,
> DCValue dcv) contains the following code:
> if (language == null)
> {
> // Value must be null language to match
> if (dcv.language != null)
> {
> // Value is qualified, so no match
> return false;
> }
> }
> else if (!language.equals(Item.ANY))
> {
> // Not a wildcard, so language must match exactly
> if (!language.equals(dcv.language))
> {
> return false;
> }
> }
> else if (!schema.equals(Item.ANY))
> {
> if (dcv.schema != null && !dcv.schema.equals(schema))
> {
> // The namespace doesn't match
> return false;
> }
> }
> Therefore, the schema is not being checked if the language of the metadata
> field is empty (null) or set to Item.ANY. This leads to the following case:
> dc.type = foo
> dc2.type = bar
> MyItem.getMetadata("dc", "type", null, null) should return 1 result 'foo'.
> Instead, it returns 'foo' and 'bar'.
> To fix, change the 'else if' for the ' else if (!schema.equals(Item.ANY))' to
> 'if (!schema.equals(Item.ANY))'.
--
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] Resolved: (DS-806) Item.match() incorrect logic for schema testing
[
https://jira.duraspace.org/browse/DS-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart Lewis resolved DS-806.
-
Resolution: Fixed
Fix Version/s: 1.8.0
Assignee: Stuart Lewis
Fixed in trunk and 1_7_x branch.
> Item.match() incorrect logic for schema testing
> ---
>
> Key: DS-806
> URL: https://jira.duraspace.org/browse/DS-806
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
>Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0
>Reporter: Stuart Lewis
>Assignee: Stuart Lewis
>Priority: Blocker
> Fix For: 1.7.1, 1.8.0
>
> Attachments: [DS-806]_junit_test.patch
>
>
> Item.match(String schema, String element, String qualifier, String language,
> DCValue dcv) contains the following code:
> if (language == null)
> {
> // Value must be null language to match
> if (dcv.language != null)
> {
> // Value is qualified, so no match
> return false;
> }
> }
> else if (!language.equals(Item.ANY))
> {
> // Not a wildcard, so language must match exactly
> if (!language.equals(dcv.language))
> {
> return false;
> }
> }
> else if (!schema.equals(Item.ANY))
> {
> if (dcv.schema != null && !dcv.schema.equals(schema))
> {
> // The namespace doesn't match
> return false;
> }
> }
> Therefore, the schema is not being checked if the language of the metadata
> field is empty (null) or set to Item.ANY. This leads to the following case:
> dc.type = foo
> dc2.type = bar
> MyItem.getMetadata("dc", "type", null, null) should return 1 result 'foo'.
> Instead, it returns 'foo' and 'bar'.
> To fix, change the 'else if' for the ' else if (!schema.equals(Item.ANY))' to
> 'if (!schema.equals(Item.ANY))'.
--
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-811) Delete / withdraw items via bulk csv editing
[
https://jira.duraspace.org/browse/DS-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart Lewis updated DS-811:
Summary: Delete / withdraw items via bulk csv editing (was: Delete /
withdrawn items via bulk csv editing)
> Delete / withdraw items via bulk csv editing
>
>
> Key: DS-811
> URL: https://jira.duraspace.org/browse/DS-811
> Project: DSpace
> Issue Type: New Feature
> Components: DSpace API, JSPUI, XMLUI
>Reporter: Stuart Lewis
>Assignee: Stuart Lewis
> Fix For: 1.8.0
>
>
> I want to enhance the CSV-based batch editing tool. One obvious enhancement
> is to allow the withdrawal / deletion of items. I propose to implement this
> by:
> - In the 'collection' column which normally holds the primary and mapped
> collection(s) in which the item resides, allow the values ('DELETE' or
> 'WITHDRAW') to be entered. These will, after the normal confirmation screen,
> perform those actions.
> Any comments on that before I implement it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] Created: (DS-811) Delete / withdrawn items via bulk csv editing
Delete / withdrawn items via bulk csv editing
-
Key: DS-811
URL: https://jira.duraspace.org/browse/DS-811
Project: DSpace
Issue Type: New Feature
Components: DSpace API, JSPUI, XMLUI
Reporter: Stuart Lewis
Assignee: Stuart Lewis
Fix For: 1.8.0
I want to enhance the CSV-based batch editing tool. One obvious enhancement is
to allow the withdrawal / deletion of items. I propose to implement this by:
- In the 'collection' column which normally holds the primary and mapped
collection(s) in which the item resides, allow the values ('DELETE' or
'WITHDRAW') to be entered. These will, after the normal confirmation screen,
perform those actions.
Any comments on that before I implement it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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-811) Delete / withdraw items via bulk csv editing
[
https://jira.duraspace.org/browse/DS-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18777#action_18777
]
Stuart Lewis commented on DS-811:
-
My personal preference is to keep as much as possible in the CSV, as is it much
more self-contained, easier for the user (no options to choose - just upload
the file), and less UI tinkering to do with each change. Am happy to be guided
by popular preference though.
> Delete / withdraw items via bulk csv editing
>
>
> Key: DS-811
> URL: https://jira.duraspace.org/browse/DS-811
> Project: DSpace
> Issue Type: New Feature
> Components: DSpace API, JSPUI, XMLUI
>Reporter: Stuart Lewis
>Assignee: Stuart Lewis
> Fix For: 1.8.0
>
>
> I want to enhance the CSV-based batch editing tool. One obvious enhancement
> is to allow the withdrawal / deletion of items. I propose to implement this
> by:
> - In the 'collection' column which normally holds the primary and mapped
> collection(s) in which the item resides, allow the values ('DELETE' or
> 'WITHDRAW') to be entered. These will, after the normal confirmation screen,
> perform those actions.
> Any comments on that before I implement it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] Closed: (DS-813) XMLUI searching and browsing using UTF-8 characters fails
[ https://jira.duraspace.org/browse/DS-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis closed DS-813. --- Documentation Status: In Description (was: Needed) Resolution: Answered Closed as requested. Fixed in server.xml. > XMLUI searching and browsing using UTF-8 characters fails > - > > Key: DS-813 > URL: https://jira.duraspace.org/browse/DS-813 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.6.2 >Reporter: Karen Brooks >Priority: Major > Attachments: Browse Step 1.jpg, Browse Step 2.jpg, Browse Step 3.jpg, > Step 1.jpg, Step 2.jpg, Step 3.jpg > > > Using UTF-8 characters (Thai), some searches work, some do not, same with > browsing. We get "Search produced no results" and non-UTF-8 chars in place > of orig search chars. Problems seems worse in center search/browse box. > Example: After getting successful results from basic search in sidebar, we > can't browse further down list. We get "Now showing items 1-10 of xxx" > successfully, but cannot go to item 11-20. > Issue probably related to * DS-132 XMLUI overall UTF-8 encoding is > inconsistent and forms do not use UTF-8 -- 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] Created: (DS-821) AbstractMETSIngester creates an item before adding descriptive metadata
AbstractMETSIngester creates an item before adding descriptive metadata --- Key: DS-821 URL: https://jira.duraspace.org/browse/DS-821 Project: DSpace Issue Type: Bug Components: DSpace API Affects Versions: 1.7.0 Reporter: Stuart Lewis Priority: Major Fix For: 1.7.1 When items are ingested via SWORD (and anything that uses the METS package ingester mechanism), the 'thanks for your submission' email shows the title of the item to be untitled. This has been tracked down to changes made in 1.7 to introduce community and collection AIP restoration in AbstractMETSIngester.java. The item is created before descriptive metadata is added. This means at the time the email is sent, no descriptive metadata has yet been added, hence the 'untitled'. IRC log: [08:32am] stuartlewis: With all the packager changes in 1.7, has the order of item creation been changed? It looks like items are now created and installed (and therefore 'thanks for your submission' emails are sent), and following that, the package opened and the metadata etc is added to the item. Previously I think it all happened in one go, and the item was created at the end of the process. I think this might be the culprit to Jose's SWORD email problem in dspace-tech. [08:35am] tdonohue: hi stuartlewis -- yea, i got a minute [08:36am] tdonohue: so, can you point me at the code/classes you are looking at? I don't recall this process changing, but maybe that will help [08:37am] stuartlewis: AbstractMETSIngester [08:37am] stuartlewis: ingestObject method [08:38am] tdonohue: just a sec, pulling that up now [08:38am] stuartlewis: Just looking for some line numbers [08:38am] stuartlewis: Line 429 calls: [08:38am] stuartlewis: dso = PackageUtils.createDSpaceObject(context, parent, [08:38am] stuartlewis: type, handle, params); [08:39am] grahamtriggs: Actually, the offending line would be PackageUtils, Line 477 [08:39am] grahamtriggs: // Finish creating item with specified handle [08:39am] grahamtriggs: // (this will either install item immediately or start a workflow, based on params) [08:39am] grahamtriggs: dso = finishCreateItem(context, wsi, handle, params); [08:39am] stuartlewis: Yep - was just tracing it through to there. [08:39am] stuartlewis: Then it bounces back, and then in Step 5, descriptive metadata is added. [08:40am] stuartlewis: So the 'thanks' email is sent before the descriptive metadata has been set. [08:40am] stuartlewis: (I think!) [08:41am] tdonohue: hmmm...yea, I think you may be right about this. Obviously, wasn't my intention to change that processing... [08:41am] tdonohue: i'm digging around more...trying to determine *why* I did things this way (this was all part of the AIP work, obviously) [08:42am] grahamtriggs: you did it to get a DSpaceObject! [08:43am] tdonohue: yea, you're right -- I needed a DSpaceObject in order to deal with ingest of Community, Collection or Item in a generic fashion. [08:43am] tdonohue: unfortunately, WorkspaceItem is *not* a DSpaceObject, so I needed to obtain one [08:44am] tdonohue: (i.e. it's a result of our semi-backwards datamodel, where not everything is a DSpaceObject) [08:48am] tdonohue: wait -- where is the code that sends the email notifications? why am I not finding that in InstallItem? (sorry, I'm forgetful today) [08:48am] tdonohue: nevermind -- found it... it's an event [08:48am] tdonohue: // Notify interested parties of newly archived Item [08:48am] tdonohue: c.addEvent(new Event(Event.INSTALL, Constants.ITEM, item.getID(), [08:48am] tdonohue: item.getHandle())); [08:50am] tdonohue: so...this is definitely a bug. I'm not sure how best to fix it though off top of my head, as it's unfortunately very specific to Items, and AbstractMETSIngester needs to now support Community & Collection as well. [08:51am] stuartlewis: Shall I stick it in JIRA for now? [08:51am] tdonohue: definitely put it in JIRA. we need to fix this in 1.7.1, I'd say. [08:51am] stuartlewis: OK - will do. [08:53am] grahamtriggs: well, WorkspaceItem wraps a DSpaceObject - the storage for anything done in the workspace is the Item itself. So, you ought to be able to treat workspace [items] as DSpaceObjects - whether that is making them one or giving access to the internal 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 -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading erro
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-821) AbstractMETSIngester creates an item before adding descriptive metadata
[ https://jira.duraspace.org/browse/DS-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19138#action_19138 ] Stuart Lewis commented on DS-821: - I've not investigated to check, but I think this might also be having an effect on dc.description.provenance for the same reason. When a SWORD deposit is made, with 1 bitstream, the following is set: dc.description.provenance Submitted by Stuart Lewis.com (stu...@stuartlewis.com) on 2011-02-28T00:03:17Z No. of bitstreams: 0 en dc.description.provenance Made available in DSpace on 2011-02-28T00:03:17Z (GMT). No. of bitstreams: 0en > AbstractMETSIngester creates an item before adding descriptive metadata > --- > > Key: DS-821 > URL: https://jira.duraspace.org/browse/DS-821 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.7.0 >Reporter: Stuart Lewis >Assignee: Tim Donohue >Priority: Major > Fix For: 1.7.1 > > > When items are ingested via SWORD (and anything that uses the METS package > ingester mechanism), the 'thanks for your submission' email shows the title > of the item to be untitled. This has been tracked down to changes made in 1.7 > to introduce community and collection AIP restoration in > AbstractMETSIngester.java. The item is created before descriptive metadata > is added. This means at the time the email is sent, no descriptive metadata > has yet been added, hence the 'untitled'. > IRC log: > [08:32am] stuartlewis: With all the packager changes in 1.7, has the order of > item creation been changed? It looks like items are now created and > installed (and therefore 'thanks for your submission' emails are sent), and > following that, the package opened and the metadata etc is added to the item. > Previously I think it all happened in one go, and the item was created at > the end of the process. I think this might be the culprit to Jose's SWORD > email problem in dspace-tech. > [08:35am] tdonohue: hi stuartlewis -- yea, i got a minute > [08:36am] tdonohue: so, can you point me at the code/classes you are looking > at? I don't recall this process changing, but maybe that will help > [08:37am] stuartlewis: AbstractMETSIngester > [08:37am] stuartlewis: ingestObject method > [08:38am] tdonohue: just a sec, pulling that up now > [08:38am] stuartlewis: Just looking for some line numbers > [08:38am] stuartlewis: Line 429 calls: > [08:38am] stuartlewis: dso = PackageUtils.createDSpaceObject(context, parent, > [08:38am] stuartlewis: type, handle, params); > [08:39am] grahamtriggs: Actually, the offending line would be PackageUtils, > Line 477 > [08:39am] grahamtriggs: // Finish creating item with > specified handle > [08:39am] grahamtriggs: // (this will either install item > immediately or start a workflow, based on params) > [08:39am] grahamtriggs: dso = finishCreateItem(context, wsi, > handle, params); > [08:39am] stuartlewis: Yep - was just tracing it through to there. > [08:39am] stuartlewis: Then it bounces back, and then in Step 5, descriptive > metadata is added. > [08:40am] stuartlewis: So the 'thanks' email is sent before the descriptive > metadata has been set. > [08:40am] stuartlewis: (I think!) > [08:41am] tdonohue: hmmm...yea, I think you may be right about this. > Obviously, wasn't my intention to change that processing... > [08:41am] tdonohue: i'm digging around more...trying to determine *why* I did > things this way (this was all part of the AIP work, obviously) > [08:42am] grahamtriggs: you did it to get a DSpaceObject! > [08:43am] tdonohue: yea, you're right -- I needed a DSpaceObject in order to > deal with ingest of Community, Collection or Item in a generic fashion. > [08:43am] tdonohue: unfortunately, WorkspaceItem is *not* a DSpaceObject, so > I needed to obtain one > [08:44am] tdonohue: (i.e. it's a result of our semi-backwards datamodel, > where not everything is a DSpaceObject) > [08:48am] tdonohue: wait -- where is the code that sends the email > notifications? why am I not finding that in InstallItem? (sorry, I'm > forgetful today) > [08:48am] tdonohue: nevermind -- found it... it's an event > [08:48am] tdonohue: // Notify interested parties of newly archived Item > [08:48am] tdonohue: c.addEvent(new Event(Event.INSTALL, > Constants.ITEM, item.getID(), > [08:48am] tdonohue: item.getHandle())); > [08:50am] tdonohue: so...this is definitely a bug. I'm not sure how best to > fix it though off top of my head, as it's unfortunately very specific to > Items, and AbstractMETSIngester needs to now support Community & Collection > as well. > [08:51am] stuartlewis: Shall I stick it in JIRA for now
[Dspace-devel] [DuraSpace JIRA] Reopened: (DS-215) Single-argument Item.getMetadata does not work with mixed-case metadata
[ https://jira.duraspace.org/browse/DS-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis reopened DS-215: - It looks like this change got over written during the merge of the junit testing code into 1.7, so will need re-applying. http://scm.dspace.org/trac/dspace/changeset/5252/dspace/trunk/dspace-api/src/main/java/org/dspace/content/Item.java > Single-argument Item.getMetadata does not work with mixed-case metadata > --- > > Key: DS-215 > URL: https://jira.duraspace.org/browse/DS-215 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.5.2 >Reporter: Nicholas Riley >Assignee: Robin Taylor > Fix For: 1.7.0 > > Attachments: Allow_for_mixed_case_metadata_names_.patch > > > Item.getMetadata lowercases the metadata requested, which means it'll never > work for terms such as bibliographicCitation. -- 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 -- Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Closed: (DS-833) item.getMetadata(String mdString): issue for fields with upper case letter.
[ https://jira.duraspace.org/browse/DS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis closed DS-833. --- Resolution: Duplicate Hi Fabio, Thanks for spotting this. We thought this was already fixed in 1.7, but it appears that it wasn't: Duplicate of https://jira.duraspace.org/browse/DS-215 which was applied to trunk for 1.7, but got over written during a code merge. I have reopened DS-215 so that it can be re-applied. Thanks, Stuart > item.getMetadata(String mdString): issue for fields with upper case letter. > --- > > Key: DS-833 > URL: https://jira.duraspace.org/browse/DS-833 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.7.0 >Reporter: Fabio Bolognesi > > case 1: > metadata field: dc.coverage.stylePeriod > item.getMetadata(String mdString) return an empty DCValue[] > case2: > metadata field: dc.coverage.styleperiod > item.getMetadata(String mdString) return a full DCValue[] > I am forced to name the metadata field not using upper case letter. > The following line should be corrected: > Item.java(497) tokens[i] = dcf.nextToken().toLowerCase().trim(); -- 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 -- Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-834) CSV import dialog doesn't handle csv errors gracefully
[ https://jira.duraspace.org/browse/DS-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-834: Assignee: Stuart Lewis Status: Open (was: Received) Thanks Timo - we hope to do this for 1.8 later this year, along with some other improvements to the CSV editing. > CSV import dialog doesn't handle csv errors gracefully > -- > > Key: DS-834 > URL: https://jira.duraspace.org/browse/DS-834 > Project: DSpace > Issue Type: Bug > Components: XMLUI >Affects Versions: 1.6.2 >Reporter: Timo Aalto >Assignee: Stuart Lewis > > I was trying to upload a csv containing some metadata changes. In the upload > dialog I all got was "no changes were detected" splash. It turned out that I > had accidentally left some completely empty columns in the middle of the CSV > file. Luckily I had a ssh screen running and it showed the stack trace below. > It would be good to catch that exception and provide some guidance for the > poor dspace admin trying to figure out what went wrong. > java.lang.ArrayIndexOutOfBoundsException: 1 > at > org.dspace.app.bulkedit.MetadataImport.compare(MetadataImport.java:345) > at > org.dspace.app.bulkedit.MetadataImport.runImport(MetadataImport.java:154) > at > org.dspace.app.xmlui.aspect.administrative.FlowMetadataImportUtils.processUploadCSV(FlowMetadataImportUtils.java:178) > 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:585) > 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) > at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2394) > at > org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:162) > at > org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393) > at > org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834) > at > org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160) > at org.mozilla.javascript.Context.call(Context.java:538) > at > org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1833) > at > org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1803) > at > org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:698) > at > org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:94) > at > org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55) > at > org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87) > at > org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55) > at > org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87) -- 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 -- Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-835) DSpace 1.7.0 cannot search LDAP's subtree (OU) on openldap
[ https://jira.duraspace.org/browse/DS-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19172#action_19172 ] Stuart Lewis commented on DS-835: - Hi Daniel, Thanks for this bug report. I've tested 1.7 with openldap (non-TLS) and it worked fine. For a test server you can use, see: http://blog.stuartlewis.com/2008/08/18/test-ldap-service-upgraded-now-with-branches/ In your settings: ldap.object_context / ldap.search.context = ou=users,ou=users,dc=company,dc=br Is the repeated 'ou=users,ou=users' correct? Thanks, Stuart > DSpace 1.7.0 cannot search LDAP's subtree (OU) on openldap > -- > > Key: DS-835 > URL: https://jira.duraspace.org/browse/DS-835 > Project: DSpace > Issue Type: Bug >Affects Versions: 1.7.0 > Environment: Ubuntu Server Ubuntu 10.04.2 LTS, slapd 2.4.21 using > ldaps, Tomcat 6.0.24-2ubuntu1.6 >Reporter: Daniel Ettore >Priority: Blocker > > DSpace cannot search on ldap's subtree (OUs). > My dspace.cfg - ldap is: > ldap.enable = true > ldap.provider_url = ldaps://IPADDRESS:636/ > ldap.id_field = uid > ldap.object_context = ou=users,ou=users,dc=company,dc=br > ldap.search_context = ou=users,ou=users,dc=company,dc=br # (we have others > OU under this, exemple: ou=student,ou=users,ou=users,dc=company,dc=br - > ou=abc,ou=users,dc=company,dc=br,ou=br and others) > ldap.email_field = mail > ldap.surname_field = sn > ldap.givenname_field = givenName > #ldap.phone_field = telephoneNumber > webui.ldap.autoregister = true > ldap.search_scope = 2 > ldap.search.user = uid=read-only,ou=users,dc=company,dc=br > ldap.search.password = password > plugin.sequence.org.dspace.authenticate.AuthenticationMethod = \ >org.dspace.authenticate.LDAPHierarchicalAuthentication ,\ >org.dspace.authenticate.PasswordAuthentication > Log from LDAP > Mar 3 15:38:16 ldap slapd[3541]: conn=1772 fd=19 ACCEPT from > IP=IPADDRESS:35681 (IP=0.0.0.0:636) > Mar 3 15:38:16 ldap slapd[3541]: conn=1772 fd=19 TLS established tls_ssf=128 > ssf=128 > Mar 3 15:38:16 ldap slapd[3541]: conn=1772 op=0 BIND > dn="uid=read-only,ou=users,dc=company,dc=br" method=128 > Mar 3 15:38:16 ldap slapd[3541]: conn=1772 op=0 BIND > dn="uid=read-only,ou=users,dc=company,dc=br" mech=SIMPLE ssf=0 > Mar 3 15:38:16 ldap slapd[3541]: conn=1772 op=0 RESULT tag=97 err=0 text= > Mar 3 15:38:16 ldap slapd[3541]: conn=1772 op=1 SRCH > base="ou=users,ou=users,dc=company,dc=br" scope=2 deref=3 > filter="(&(uid=LOGIN))" ---> at this point, the user LOGIN is on > ou=student,ou=users,ou=users,dc=company,dc=br > Mar 3 15:38:16 ldap slapd[3541]: conn=1772 op=1 SEARCH RESULT tag=101 err=32 > nentries=0 text= > Mar 3 15:38:16 ldap slapd[3541]: conn=1772 op=2 UNBIND > Mar 3 15:38:16 ldap slapd[3541]: conn=1772 fd=19 closed > Mar 3 15:38:16 ldap slapd[3541]: conn=1771 op=1 UNBIND > Mar 3 15:38:16 ldap slapd[3541]: conn=1771 fd=18 closed > Log from DSpace: > 2011-03-03 16:47:50,078 INFO > org.dspace.authenticate.LDAPHierarchicalAuthentication @ > anonymous:session_id=8B6701643D44F55673C0F04B07C733E7:ip_addr=200.136.207.231:auth:attempting > trivial auth of user=LOGIN > 2011-03-03 16:47:50,165 WARN > org.dspace.authenticate.LDAPHierarchicalAuthentication @ > anonymous:session_id=8B6701643D44F55673C0F04B07C733E7:ip_addr=200.136.207.231:ldap_attribute_lookup:type=failed_search > javax.naming.NameNotFoundException\colon; [LDAP\colon; error code 32 - No > Such Object]; remaining name 'ou=users,ou=users,dc=company,dc=br' > 2011-03-03 16:47:50,166 INFO > org.dspace.authenticate.LDAPHierarchicalAuthentication @ > anonymous:session_id=8B6701643D44F55673C0F04B07C733E7:ip_addr=200.136.207.231:failed_login:no > DN found for user LOGIN > 2011-03-03 16:47:50,166 INFO org.dspace.authenticate.PasswordAuthentication > @ > anonymous:session_id=8B6701643D44F55673C0F04B07C733E7:ip_addr=200.136.207.231:authenticate:attempting > password auth of user=LOGIN > 2011-03-03 16:47:50,167 INFO org.dspace.app.webui.servlet.PasswordServlet @ > anonymous:session_id=8B6701643D44F55673C0F04B07C733E7:ip_addr=200.136.207.231:failed_login:email=LOGIN, > result=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-701) Remove unnecessary complexity of item mapping
[ https://jira.duraspace.org/browse/DS-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19173#action_19173 ] Stuart Lewis commented on DS-701: - [20:13] It looks a good issue, but needs a patch. [20:13] yes, needs a patch [20:13] DS-701 +1 needs patch [20:13] Do we want to leave the issue open pending a patch, or close it and await a patch? [20:14] Any votes, or we'll leave it as total = +1 [20:14] * mdiggory (~mdigg...@rrcs-74-87-47-100.west.biz.rr.com) has joined #duraspace [20:15] +1. Leave open. [20:15] +1 with patch [20:15] +1 needs improving, but not sure how far the patch would go, etc [20:15] OK - +4. > Remove unnecessary complexity of item mapping > - > > Key: DS-701 > URL: https://jira.duraspace.org/browse/DS-701 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Reporter: Mark H. Wood >Priority: Trivial > > [copied from DS-545 to separate two issues] > In the item mapper, one can only view items mapped to a collection via the > collections they were mapped from. > Just a list of the mapped items would be more useful than the list of > collections from where items were mapped. -- 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] Updated: (DS-701) Remove unnecessary complexity of item mapping
[ https://jira.duraspace.org/browse/DS-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-701: Comment: was deleted (was: [20:16] https://jira.duraspace.org/browse/DS-705 - Returning CLOBs fields data from ORACLE [20:16] * kshepherd reminds himself to get onto that JIRA bot again [20:17] Anyone know the reason for this? To get around a TEXT field length limitation for metadata? [20:17] I'm not sure what 705 is supposed to do for us. [20:17] I can't test oracle. +0 until i see a full patch with explanation [20:17] I'd like a bit more context for this [20:17] 0 [20:17] 0 [20:18] Ok - maybe we pass on this one, and we'll put a comment in JIRA asking the submitter for more details?) > Remove unnecessary complexity of item mapping > - > > Key: DS-701 > URL: https://jira.duraspace.org/browse/DS-701 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Reporter: Mark H. Wood >Priority: Trivial > > [copied from DS-545 to separate two issues] > In the item mapper, one can only view items mapped to a collection via the > collections they were mapped from. > Just a list of the mapped items would be more useful than the list of > collections from where items were mapped. -- 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] Commented: (DS-701) Remove unnecessary complexity of item mapping
[ https://jira.duraspace.org/browse/DS-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19174#action_19174 ] Stuart Lewis commented on DS-701: - [20:16] https://jira.duraspace.org/browse/DS-705 - Returning CLOBs fields data from ORACLE [20:16] * kshepherd reminds himself to get onto that JIRA bot again [20:17] Anyone know the reason for this? To get around a TEXT field length limitation for metadata? [20:17] I'm not sure what 705 is supposed to do for us. [20:17] I can't test oracle. +0 until i see a full patch with explanation [20:17] I'd like a bit more context for this [20:17] 0 [20:17] 0 [20:18] Ok - maybe we pass on this one, and we'll put a comment in JIRA asking the submitter for more details? > Remove unnecessary complexity of item mapping > - > > Key: DS-701 > URL: https://jira.duraspace.org/browse/DS-701 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Reporter: Mark H. Wood >Priority: Trivial > > [copied from DS-545 to separate two issues] > In the item mapper, one can only view items mapped to a collection via the > collections they were mapped from. > Just a list of the mapped items would be more useful than the list of > collections from where items were mapped. -- 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] Commented: (DS-705) Returning CLOBs fields data from ORACLE
[
https://jira.duraspace.org/browse/DS-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19176#action_19176
]
Stuart Lewis commented on DS-705:
-
Hi Danilo,
This JIRA issue was reviewed in our weekly development meeting yesterday (see
below). Are you able to provide us with some further information about the
reason for this change, and any implications it might have?
Thanks,
Stuart
[20:16] https://jira.duraspace.org/browse/DS-705 - Returning CLOBs
fields data from ORACLE
[20:16] * kshepherd reminds himself to get onto that JIRA bot again
[20:17] Anyone know the reason for this? To get around a TEXT
field length limitation for metadata?
[20:17] I'm not sure what 705 is supposed to do for us.
[20:17] I can't test oracle. +0 until i see a full patch with
explanation
[20:17] I'd like a bit more context for this
[20:17] 0
[20:17] 0
[20:18] Ok - maybe we pass on this one, and we'll put a comment
in JIRA asking the submitter for more details?
> Returning CLOBs fields data from ORACLE
> ---
>
> Key: DS-705
> URL: https://jira.duraspace.org/browse/DS-705
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API, JSPUI
>Reporter: Danilo Azevedo
>Priority: Critical
>
> // Support CLOBs in place of TEXT columns in Oracle
> row.setColumn(name, results.getString(i)); is always returning NULL
> possible fix:
> try {
> java.sql.Clob clob = results.getClob(i);
> java.io.Writer writer = new java.io.StringWriter();
> char[] buffer = new char[4000];
> Reader reader = new BufferedReader(new
> java.io.InputStreamReader(clob.getAsciiStream()));
> int n;
> while ((n = reader.read(buffer)) != -1) {
> writer.write(buffer, 0, n);
> }
> row.setColumn(name, writer.toString());
> } catch (Exception ioE) {
> row.setColumn(name, results.getString(i));
> }
--
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] 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=19177#action_19177 ] Stuart Lewis commented on DS-708: - [20:18] https://jira.duraspace.org/browse/DS-708 - Deprecate & Remove old 'org.dspace.app.mets.METSExport' class, as it is obsolete [20:18] +1 to 708. [20:18] +1 [20:18] Looks like we should leave this one to Tim, as he knows all this, and is the submitter and assigned. [20:19] So, +1 [20:19] agreed +1 to Tim [20:19] +1 [20:19] +1 [20:19] true [20:19] Result = +5, leave assigned to Tim. > 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 > > > 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 -- 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
