[Dspace-devel] [DuraSpace JIRA] Updated: (DS-638) check files on input for viruses, and verify file format
[ https://jira.duraspace.org/browse/DS-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-638: Attachment: virus_check.patch Attached a replacement patch that uses the existing Curation Framework to perform virus checking. > check files on input for viruses, and verify file format > - > > Key: DS-638 > URL: https://jira.duraspace.org/browse/DS-638 > Project: DSpace > Issue Type: New Feature > Components: JSPUI >Affects Versions: 1.6.2 > Environment: to use this patch you will need to have ClamAV, and > jhove installed on your system. >Reporter: Jose Blanco >Assignee: Robin Taylor > Attachments: java_files.zip, jhove_config_files.zip, jsp_files.zip, > virus_check.patch > > > This patch uses JHOVE to provide rough-and-ready format checking by > identifying that the file/bitstream extension matches formats verifiable by > JHOVE. (Currently DSpace accepts a deposit's file extension as gospel, so a > user could tack a ".txt" extension onto a GIF and DSpace would assign the > incorrect format to the file based on that incorrect extension.) > This patch also also contains code to check the file for the presence of > viruses. > In order to use this patch you must have jhove and ClamAV installed on your > system. > Important notes: > (1) HTML identification has proved unreliable ( by jhove ), so this patch > does not return accurate results for that > file format. > (2) This code does not fully incorporate JHOVE's validation functions; it > only verifies that what depositors intended to submit is in fact what they > submitted. > The following are returned messages when an error is detected: > Text in [brackets] is a returned value, ALLCAPS can/should be modified to > reflect your current installation. > Questionable AIFF, GIF, JPG, PDF, TIF, WAVE, XML: > DSPACE could not verify that your file is a valid [file_format_extension]. > Please check the file format and ".[file_format_extension]" extension. > Questionable TXT: > DSPACE found the text file you are trying to upload is neither UTF-8 nor > ASCII. Please verify that your file is in the format you wanted. > Spaces in filenames ( this is an additional check ): > The file name contains spaces; this is not recommended. If possible, please > replace spaces with underscores: "_". > Virus detected: > DSPACE detected a virus in this file. Please repair it and resume the > deposit. If you need assistance, please contact us: EMAIL_ADDRESS. > To get the patch working: > Add the jhove conf files to > [dspace]/jhove direcoty > Here are the conf files: > jhove-aiff.conf > jhove-ascii.conf > jhove-gif.conf > jhove-jpeg.conff > jhove-pdf.conf > jhove-tiff.conf > jhove-utf8.conf > jhove-wave.conf > jhove-xml.conf > Also the following files were changed: > dspace-api/src/main/java/org/dspace/submit/step/UploadStep.java > dspace-jspui/dspace-jspui-api/src/main/java/org/dspace/app/webui/submit/step/JSPUploadStep.java > dspace-api/src/main/java/org/dspace/content/FormatIdentifier.java > dspace/modules/jspui/src/main/webapp/submit/get-file-format.jsp ( locally > customized ) > dspace/modules/jspui/src/main/webapp/submit/upload-error-virus.jsp ( new file > - placed in locally modified area for the jspui interface) > These files are attached with this patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-638) check files on input for viruses, and verify file format
[ https://jira.duraspace.org/browse/DS-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20189#action_20189 ] Robin Taylor commented on DS-638: - Please note that the virus_check patch was created using IntellijIDEA, not sure if it will apply successfully using Unix patch command. > check files on input for viruses, and verify file format > - > > Key: DS-638 > URL: https://jira.duraspace.org/browse/DS-638 > Project: DSpace > Issue Type: New Feature > Components: JSPUI >Affects Versions: 1.6.2 > Environment: to use this patch you will need to have ClamAV, and > jhove installed on your system. >Reporter: Jose Blanco >Assignee: Robin Taylor > Attachments: java_files.zip, jhove_config_files.zip, jsp_files.zip, > virus_check.patch > > > This patch uses JHOVE to provide rough-and-ready format checking by > identifying that the file/bitstream extension matches formats verifiable by > JHOVE. (Currently DSpace accepts a deposit's file extension as gospel, so a > user could tack a ".txt" extension onto a GIF and DSpace would assign the > incorrect format to the file based on that incorrect extension.) > This patch also also contains code to check the file for the presence of > viruses. > In order to use this patch you must have jhove and ClamAV installed on your > system. > Important notes: > (1) HTML identification has proved unreliable ( by jhove ), so this patch > does not return accurate results for that > file format. > (2) This code does not fully incorporate JHOVE's validation functions; it > only verifies that what depositors intended to submit is in fact what they > submitted. > The following are returned messages when an error is detected: > Text in [brackets] is a returned value, ALLCAPS can/should be modified to > reflect your current installation. > Questionable AIFF, GIF, JPG, PDF, TIF, WAVE, XML: > DSPACE could not verify that your file is a valid [file_format_extension]. > Please check the file format and ".[file_format_extension]" extension. > Questionable TXT: > DSPACE found the text file you are trying to upload is neither UTF-8 nor > ASCII. Please verify that your file is in the format you wanted. > Spaces in filenames ( this is an additional check ): > The file name contains spaces; this is not recommended. If possible, please > replace spaces with underscores: "_". > Virus detected: > DSPACE detected a virus in this file. Please repair it and resume the > deposit. If you need assistance, please contact us: EMAIL_ADDRESS. > To get the patch working: > Add the jhove conf files to > [dspace]/jhove direcoty > Here are the conf files: > jhove-aiff.conf > jhove-ascii.conf > jhove-gif.conf > jhove-jpeg.conff > jhove-pdf.conf > jhove-tiff.conf > jhove-utf8.conf > jhove-wave.conf > jhove-xml.conf > Also the following files were changed: > dspace-api/src/main/java/org/dspace/submit/step/UploadStep.java > dspace-jspui/dspace-jspui-api/src/main/java/org/dspace/app/webui/submit/step/JSPUploadStep.java > dspace-api/src/main/java/org/dspace/content/FormatIdentifier.java > dspace/modules/jspui/src/main/webapp/submit/get-file-format.jsp ( locally > customized ) > dspace/modules/jspui/src/main/webapp/submit/upload-error-virus.jsp ( new file > - placed in locally modified area for the jspui interface) > These files are attached with this patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-638) check files on input for viruses, and verify file format
[ https://jira.duraspace.org/browse/DS-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-638: Attachment: UploadStep.java I have attached the modified UploadStep just to ease the review process. Cheers. > check files on input for viruses, and verify file format > - > > Key: DS-638 > URL: https://jira.duraspace.org/browse/DS-638 > Project: DSpace > Issue Type: New Feature > Components: JSPUI >Affects Versions: 1.6.2 > Environment: to use this patch you will need to have ClamAV, and > jhove installed on your system. >Reporter: Jose Blanco >Assignee: Robin Taylor > Attachments: java_files.zip, jhove_config_files.zip, jsp_files.zip, > UploadStep.java, virus_check.patch > > > This patch uses JHOVE to provide rough-and-ready format checking by > identifying that the file/bitstream extension matches formats verifiable by > JHOVE. (Currently DSpace accepts a deposit's file extension as gospel, so a > user could tack a ".txt" extension onto a GIF and DSpace would assign the > incorrect format to the file based on that incorrect extension.) > This patch also also contains code to check the file for the presence of > viruses. > In order to use this patch you must have jhove and ClamAV installed on your > system. > Important notes: > (1) HTML identification has proved unreliable ( by jhove ), so this patch > does not return accurate results for that > file format. > (2) This code does not fully incorporate JHOVE's validation functions; it > only verifies that what depositors intended to submit is in fact what they > submitted. > The following are returned messages when an error is detected: > Text in [brackets] is a returned value, ALLCAPS can/should be modified to > reflect your current installation. > Questionable AIFF, GIF, JPG, PDF, TIF, WAVE, XML: > DSPACE could not verify that your file is a valid [file_format_extension]. > Please check the file format and ".[file_format_extension]" extension. > Questionable TXT: > DSPACE found the text file you are trying to upload is neither UTF-8 nor > ASCII. Please verify that your file is in the format you wanted. > Spaces in filenames ( this is an additional check ): > The file name contains spaces; this is not recommended. If possible, please > replace spaces with underscores: "_". > Virus detected: > DSPACE detected a virus in this file. Please repair it and resume the > deposit. If you need assistance, please contact us: EMAIL_ADDRESS. > To get the patch working: > Add the jhove conf files to > [dspace]/jhove direcoty > Here are the conf files: > jhove-aiff.conf > jhove-ascii.conf > jhove-gif.conf > jhove-jpeg.conff > jhove-pdf.conf > jhove-tiff.conf > jhove-utf8.conf > jhove-wave.conf > jhove-xml.conf > Also the following files were changed: > dspace-api/src/main/java/org/dspace/submit/step/UploadStep.java > dspace-jspui/dspace-jspui-api/src/main/java/org/dspace/app/webui/submit/step/JSPUploadStep.java > dspace-api/src/main/java/org/dspace/content/FormatIdentifier.java > dspace/modules/jspui/src/main/webapp/submit/get-file-format.jsp ( locally > customized ) > dspace/modules/jspui/src/main/webapp/submit/upload-error-virus.jsp ( new file > - placed in locally modified area for the jspui interface) > These files are attached with this patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-829) OAI Extended Addon : Adding filter and modifying capacities to the OAI interface
[ https://jira.duraspace.org/browse/DS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20296#action_20296 ] Robin Taylor commented on DS-829: - Currently testing and this seems the best place to record anything notable... The dspace/pom.xml is patched to include profiles for the dspace-oaiextended-api and dspace-oaiextended-webapp but is missing one for their parent dspace-oaiextended. This needs added or Maven doesn't spot the source code when building and looks to the Snapshot repo instead. > OAI Extended Addon : Adding filter and modifying capacities to the OAI > interface > > > Key: DS-829 > URL: https://jira.duraspace.org/browse/DS-829 > Project: DSpace > Issue Type: New Feature > Components: OAI-PMH >Reporter: João Melo >Assignee: Robin Taylor > Fix For: 1.8.0 > > Attachments: OAIExtended-v2.2.tar.gz, > OAIExtended_v2.1_with_documentation.tar.gz > > > Purpose > The OAI Extended Addon was initially developed to allow DSpace to be > compliant with the Driver project guidelines > (http://www.driver-repository.eu). > How it works? > When an OAI-PMH request is received, the DSpace database is queried through > the standard OAI Interface included in DSpace. After that, the OAI Extended > Addon starts to work. First, the list of items retrieved from the database is > filtered by a Filter Mechanism, after that, each item associated metadata is > modified by a Modifier Mechanism. The results of both actions are returned to > the harvester that performed the request. > Because of the initial purpose, most of the filters and modifiers implemented > are specific to the Driver compliance issue. But there is an easy way to > develop your own filters and/or modifiers, just by extending the abstract > class Filter and/or Modifier. More information is included in the attachment. -- 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-852) Split the Creative Commons and Licence steps into two seperate steps.
[ https://jira.duraspace.org/browse/DS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-852: Attachment: Add_CC_License_Step.patch Add patch to split the existing LicenseStep in seperate CCLicenseStep and LicenseStep. Patch was created with IntelliJ IDEA. > Split the Creative Commons and Licence steps into two seperate steps. > - > > Key: DS-852 > URL: https://jira.duraspace.org/browse/DS-852 > Project: DSpace > Issue Type: Improvement > Components: XMLUI >Reporter: Robin Taylor > Attachments: Add_CC_License_Step.patch > > > At the moment I'm just looking for comments as I may have misunderstood the > code, but it seems to me that.. > The Creative Commons step and the Licence step are somewhat artificially > grouped together as one step in item-submission.xml. In order for this to > work there is a test at the start of LicenseStep that checks to see if > webui.submit.enable-cc is set to true in dspace.cfg and if so then control is > effectively passed to CCLicenseStep. It would be simpler if these classes > were completely independent of each other and defined as separate steps in > item-submission.xml. It would also mean we could remove the unneccessary flag > webui.submit.enable-cc from dspace.cfg. -- 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-852) Split the Creative Commons and Licence steps into two seperate steps.
[ https://jira.duraspace.org/browse/DS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-852: Attachment: JSPCCLicenseStep.java LicenseStep.java CCLicenseStep.java > Split the Creative Commons and Licence steps into two seperate steps. > - > > Key: DS-852 > URL: https://jira.duraspace.org/browse/DS-852 > Project: DSpace > Issue Type: Improvement > Components: XMLUI >Reporter: Robin Taylor > Attachments: Add_CC_License_Step.patch, CCLicenseStep.java, > CCLicenseStep.java, JSPCCLicenseStep.java, JSPLicenseStep.java, > LicenseStep.java, LicenseStep.java > > > At the moment I'm just looking for comments as I may have misunderstood the > code, but it seems to me that.. > The Creative Commons step and the Licence step are somewhat artificially > grouped together as one step in item-submission.xml. In order for this to > work there is a test at the start of LicenseStep that checks to see if > webui.submit.enable-cc is set to true in dspace.cfg and if so then control is > effectively passed to CCLicenseStep. It would be simpler if these classes > were completely independent of each other and defined as separate steps in > item-submission.xml. It would also mean we could remove the unneccessary flag > webui.submit.enable-cc from dspace.cfg. -- 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-852) Split the Creative Commons and Licence steps into two seperate steps.
[ https://jira.duraspace.org/browse/DS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-852: Attachment: LicenseStep.java CCLicenseStep.java JSPLicenseStep.java > Split the Creative Commons and Licence steps into two seperate steps. > - > > Key: DS-852 > URL: https://jira.duraspace.org/browse/DS-852 > Project: DSpace > Issue Type: Improvement > Components: XMLUI >Reporter: Robin Taylor > Attachments: Add_CC_License_Step.patch, CCLicenseStep.java, > CCLicenseStep.java, JSPCCLicenseStep.java, JSPLicenseStep.java, > LicenseStep.java, LicenseStep.java > > > At the moment I'm just looking for comments as I may have misunderstood the > code, but it seems to me that.. > The Creative Commons step and the Licence step are somewhat artificially > grouped together as one step in item-submission.xml. In order for this to > work there is a test at the start of LicenseStep that checks to see if > webui.submit.enable-cc is set to true in dspace.cfg and if so then control is > effectively passed to CCLicenseStep. It would be simpler if these classes > were completely independent of each other and defined as separate steps in > item-submission.xml. It would also mean we could remove the unneccessary flag > webui.submit.enable-cc from dspace.cfg. -- 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-852) Split the Creative Commons and Licence steps into two seperate steps.
[ https://jira.duraspace.org/browse/DS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20314#action_20314 ] Robin Taylor commented on DS-852: - Attached the various classes in case there is a problem with the patch. > Split the Creative Commons and Licence steps into two seperate steps. > - > > Key: DS-852 > URL: https://jira.duraspace.org/browse/DS-852 > Project: DSpace > Issue Type: Improvement > Components: XMLUI >Reporter: Robin Taylor > Attachments: Add_CC_License_Step.patch, CCLicenseStep.java, > CCLicenseStep.java, item-submission.xml, JSPCCLicenseStep.java, > JSPLicenseStep.java, LicenseStep.java, LicenseStep.java > > > At the moment I'm just looking for comments as I may have misunderstood the > code, but it seems to me that.. > The Creative Commons step and the Licence step are somewhat artificially > grouped together as one step in item-submission.xml. In order for this to > work there is a test at the start of LicenseStep that checks to see if > webui.submit.enable-cc is set to true in dspace.cfg and if so then control is > effectively passed to CCLicenseStep. It would be simpler if these classes > were completely independent of each other and defined as separate steps in > item-submission.xml. It would also mean we could remove the unneccessary flag > webui.submit.enable-cc from dspace.cfg. -- 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-852) Split the Creative Commons and Licence steps into two seperate steps.
[ https://jira.duraspace.org/browse/DS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-852: Attachment: item-submission.xml > Split the Creative Commons and Licence steps into two seperate steps. > - > > Key: DS-852 > URL: https://jira.duraspace.org/browse/DS-852 > Project: DSpace > Issue Type: Improvement > Components: XMLUI >Reporter: Robin Taylor > Attachments: Add_CC_License_Step.patch, CCLicenseStep.java, > CCLicenseStep.java, item-submission.xml, JSPCCLicenseStep.java, > JSPLicenseStep.java, LicenseStep.java, LicenseStep.java > > > At the moment I'm just looking for comments as I may have misunderstood the > code, but it seems to me that.. > The Creative Commons step and the Licence step are somewhat artificially > grouped together as one step in item-submission.xml. In order for this to > work there is a test at the start of LicenseStep that checks to see if > webui.submit.enable-cc is set to true in dspace.cfg and if so then control is > effectively passed to CCLicenseStep. It would be simpler if these classes > were completely independent of each other and defined as separate steps in > item-submission.xml. It would also mean we could remove the unneccessary flag > webui.submit.enable-cc from dspace.cfg. -- 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] Assigned: (DS-852) Split the Creative Commons and Licence steps into two seperate steps.
[ https://jira.duraspace.org/browse/DS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor reassigned DS-852: --- Assignee: Robin Taylor > Split the Creative Commons and Licence steps into two seperate steps. > - > > Key: DS-852 > URL: https://jira.duraspace.org/browse/DS-852 > Project: DSpace > Issue Type: Improvement > Components: XMLUI >Reporter: Robin Taylor >Assignee: Robin Taylor > Attachments: Add_CC_License_Step.patch, CCLicenseStep.java, > CCLicenseStep.java, item-submission.xml, JSPCCLicenseStep.java, > JSPLicenseStep.java, LicenseStep.java, LicenseStep.java > > > At the moment I'm just looking for comments as I may have misunderstood the > code, but it seems to me that.. > The Creative Commons step and the Licence step are somewhat artificially > grouped together as one step in item-submission.xml. In order for this to > work there is a test at the start of LicenseStep that checks to see if > webui.submit.enable-cc is set to true in dspace.cfg and if so then control is > effectively passed to CCLicenseStep. It would be simpler if these classes > were completely independent of each other and defined as separate steps in > item-submission.xml. It would also mean we could remove the unneccessary flag > webui.submit.enable-cc from dspace.cfg. -- 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-852) Split the Creative Commons and Licence steps into two seperate steps.
[ https://jira.duraspace.org/browse/DS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-852: Fix Version/s: 1.8.0 > Split the Creative Commons and Licence steps into two seperate steps. > - > > Key: DS-852 > URL: https://jira.duraspace.org/browse/DS-852 > Project: DSpace > Issue Type: Improvement > Components: XMLUI >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 1.8.0 > > Attachments: Add_CC_License_Step.patch, CCLicenseStep.java, > CCLicenseStep.java, item-submission.xml, JSPCCLicenseStep.java, > JSPLicenseStep.java, LicenseStep.java, LicenseStep.java > > > At the moment I'm just looking for comments as I may have misunderstood the > code, but it seems to me that.. > The Creative Commons step and the Licence step are somewhat artificially > grouped together as one step in item-submission.xml. In order for this to > work there is a test at the start of LicenseStep that checks to see if > webui.submit.enable-cc is set to true in dspace.cfg and if so then control is > effectively passed to CCLicenseStep. It would be simpler if these classes > were completely independent of each other and defined as separate steps in > item-submission.xml. It would also mean we could remove the unneccessary flag > webui.submit.enable-cc from dspace.cfg. -- 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-602) Marker ticket for developing a Sword client for DSpace.
[ https://jira.duraspace.org/browse/DS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20316#action_20316 ] Robin Taylor commented on DS-602: - If anyone is interested the code can be found at https://scm.dspace.org/svn/repo/sandbox/sword-client-prototype. It was copied from trunk just after 1.7 was released. All the code is in a separate module dspace-sword-client. It needs someone with a genuine interest to look at it and provide feedback. Cheers, Robin. > Marker ticket for developing a Sword client for DSpace. > --- > > Key: DS-602 > URL: https://jira.duraspace.org/browse/DS-602 > Project: DSpace > Issue Type: New Feature > Components: SWORD >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 1.8.0 > > -- 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-818) Asynchronous Release
[ https://jira.duraspace.org/browse/DS-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20326#action_20326 ] Robin Taylor commented on DS-818: - As a side benefit the removal of the dspace-parent pom might resolve the issues with Maven 3 and duplicate projects as described in DS-881. Cheers, Robin. > Asynchronous Release > > > Key: DS-818 > URL: https://jira.duraspace.org/browse/DS-818 > Project: DSpace > Issue Type: New Feature > Components: Documentation, DSpace API, JSPUI, Language Packs, LNI, > OAI-PMH, REST API (experimental), Solr, SWORD, Unit Testing Framework, XMLUI >Reporter: Mark Diggory >Assignee: Mark Diggory >Priority: Major > Fix For: 1.8.0 > > > Asynchronous Release: Asynchronous Release is change in the DSpace release > process and version numbering process on modules within the DSpace trunk to > allow more flexibility adding prebuilt Addon modules into DSpace. > Goals > The primary goal of Async release is to break the the authoritative grip that > dspace-parent has on the version assignment and dependencyManagement in the > DSpace trunk modules such that: > Make the build in the DSpace Modules Source Tree dependent on a specific > dspace-api and dspace-xmlui-api versions. Specifically, dspace-statistics and > dspace-discovery > Make a packaged release of DSpace that includes a combination of Trunk and > Module projects. > More easily package releases of DSpace cyclically while allowing minor > updates of core modules to occur more often, to easily provide a minor update > path for DSpace. > View wiki page for further details. > https://wiki.duraspace.org/display/DSPACE/Asynchronous+Release -- 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-866) OAI requests with resumption token start at the wrong offset if non-public items are included and there are withdrawn items
[ https://jira.duraspace.org/browse/DS-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20327#action_20327 ] Robin Taylor commented on DS-866: - Haven't tested this theory but at first glance DS-829 may include code to resolve this problem. Cheers, Robin. > OAI requests with resumption token start at the wrong offset if non-public > items are included and there are withdrawn items > --- > > Key: DS-866 > URL: https://jira.duraspace.org/browse/DS-866 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.6.1, 1.6.2, 1.7.0, 1.7.1 >Reporter: Andrea Schweer >Priority: Major > Fix For: 1.8.0 > > Attachments: oai-offset.patch > > > In some circumstances, items are not disseminated via OAI. > OAI responds to listRecords requests with batches of up to 100 (or other > number set via oai.didl.maxresponse property) records. Requests can include a > resumption token to specify which batch is required. The resumption token is > then translated into an offset to the response from the database. > OAI listRecords responses contain withdrawn items (marked as "deleted"). > If harvest.includerestricted.oai = false is set in dspace.cfg, only publicly > readable items are included in the response. The offset into the database > results is recalculated to skip over restricted items. If a withdrawn item is > found in the database response, this item will also be skipped over by the > offset recalculation code (because it is not publicly readable) even though > it shouldn't because it will still be included in the OAI response. The code > that actually adds items to the response, in contrast, does not skip over > withdrawn items. The next batch will start n items later in the database > response than it should, where n is the number of withdrawn items before the > start of the batch. > This means that a full OAI harvest via consecutive listRecords requests will > miss as many items as there are withdrawn items. > I first found this in the 1.6.1 code and it is still present in 1.7.1. I > didn't check whether this affects earlier versions too. A patch against 1.7.1 > is attached. -- 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-866) OAI requests with resumption token start at the wrong offset if non-public items are included and there are withdrawn items
[ https://jira.duraspace.org/browse/DS-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20330#action_20330 ] Robin Taylor commented on DS-866: - Can I retract that last comment ?! Looking at the code provided with DS-829 I think it may exacerbate the problems with Resumption Tokens. > OAI requests with resumption token start at the wrong offset if non-public > items are included and there are withdrawn items > --- > > Key: DS-866 > URL: https://jira.duraspace.org/browse/DS-866 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.6.1, 1.6.2, 1.7.0, 1.7.1 >Reporter: Andrea Schweer >Priority: Major > Fix For: 1.8.0 > > Attachments: oai-offset.patch > > > In some circumstances, items are not disseminated via OAI. > OAI responds to listRecords requests with batches of up to 100 (or other > number set via oai.didl.maxresponse property) records. Requests can include a > resumption token to specify which batch is required. The resumption token is > then translated into an offset to the response from the database. > OAI listRecords responses contain withdrawn items (marked as "deleted"). > If harvest.includerestricted.oai = false is set in dspace.cfg, only publicly > readable items are included in the response. The offset into the database > results is recalculated to skip over restricted items. If a withdrawn item is > found in the database response, this item will also be skipped over by the > offset recalculation code (because it is not publicly readable) even though > it shouldn't because it will still be included in the OAI response. The code > that actually adds items to the response, in contrast, does not skip over > withdrawn items. The next batch will start n items later in the database > response than it should, where n is the number of withdrawn items before the > start of the batch. > This means that a full OAI harvest via consecutive listRecords requests will > miss as many items as there are withdrawn items. > I first found this in the 1.6.1 code and it is still present in 1.7.1. I > didn't check whether this affects earlier versions too. A patch against 1.7.1 > is attached. -- 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-829) OAI Extended Addon : Adding filter and modifying capacities to the OAI interface
[ https://jira.duraspace.org/browse/DS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20366#action_20366 ] Robin Taylor commented on DS-829: - Just a wee comment about where we do the filtering. This module would do the filtering on the result set returned by Harvest.harvest(..). The problem with that is that the administrator may have specified that a partial response should contain 100 records, if we filter out records after creating the result set of 100 records we have to take some corrective action to bring the total number back up to 100. The code appears to achieve this by a recursive call to Harvest.harvest(..). Would it not be better to filter out unwanted items whilst creating the result set ? So the filtering would take place in Harvest.harvest(..) ? There is already some filtering done there, depending on configuration both withdrawn items and items with restricted visibility can be excluded from the result set. The calling code could pass an array of filters as part of the call which Harvest could use to exclude items. So in Harvest.harvest... (* Apologies for the pseudo code *) Read database Apply filters If not required then go back and read another item else add to result set > OAI Extended Addon : Adding filter and modifying capacities to the OAI > interface > > > Key: DS-829 > URL: https://jira.duraspace.org/browse/DS-829 > Project: DSpace > Issue Type: New Feature > Components: OAI-PMH >Reporter: João Melo >Assignee: Robin Taylor > Fix For: 1.8.0 > > Attachments: OAIExtended-v2.2.tar.gz, > OAIExtended_v2.1_with_documentation.tar.gz > > > Purpose > The OAI Extended Addon was initially developed to allow DSpace to be > compliant with the Driver project guidelines > (http://www.driver-repository.eu). > How it works? > When an OAI-PMH request is received, the DSpace database is queried through > the standard OAI Interface included in DSpace. After that, the OAI Extended > Addon starts to work. First, the list of items retrieved from the database is > filtered by a Filter Mechanism, after that, each item associated metadata is > modified by a Modifier Mechanism. The results of both actions are returned to > the harvester that performed the request. > Because of the initial purpose, most of the filters and modifiers implemented > are specific to the Driver compliance issue. But there is an easy way to > develop your own filters and/or modifiers, just by extending the abstract > class Filter and/or Modifier. More information is included in the attachment. -- 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-829) OAI Extended Addon : Adding filter and modifying capacities to the OAI interface
[
https://jira.duraspace.org/browse/DS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20368#action_20368
]
Robin Taylor commented on DS-829:
-
Another wee comment. The existing code in Harvest.harvest(..) takes the stance
that withdrawn items should always be included in the result set flagged as
withdrawn even if they had restricted visibility. I guess the logic is that
they may in the past have been harvested therefore we need to tell harvesters
that they have now been withdrawn. this means that all the OAI-extended filters
would need to check that the item was not flagged as withdrawn before filtering
it. Another argument for doing the filtering in Harvest. The pseudo logic would
be amended to be...
Read database
If not withdrawn
{
then apply filters
If not required then go back and read another item
}
add to result set
> OAI Extended Addon : Adding filter and modifying capacities to the OAI
> interface
>
>
> Key: DS-829
> URL: https://jira.duraspace.org/browse/DS-829
> Project: DSpace
> Issue Type: New Feature
> Components: OAI-PMH
>Reporter: João Melo
>Assignee: Robin Taylor
> Fix For: 1.8.0
>
> Attachments: OAIExtended-v2.2.tar.gz,
> OAIExtended_v2.1_with_documentation.tar.gz
>
>
> Purpose
> The OAI Extended Addon was initially developed to allow DSpace to be
> compliant with the Driver project guidelines
> (http://www.driver-repository.eu).
> How it works?
> When an OAI-PMH request is received, the DSpace database is queried through
> the standard OAI Interface included in DSpace. After that, the OAI Extended
> Addon starts to work. First, the list of items retrieved from the database is
> filtered by a Filter Mechanism, after that, each item associated metadata is
> modified by a Modifier Mechanism. The results of both actions are returned to
> the harvester that performed the request.
> Because of the initial purpose, most of the filters and modifiers implemented
> are specific to the Driver compliance issue. But there is an easy way to
> develop your own filters and/or modifiers, just by extending the abstract
> class Filter and/or Modifier. More information is included in the attachment.
--
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-852) Split the Creative Commons and Licence steps into two seperate steps.
[ https://jira.duraspace.org/browse/DS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20413#action_20413 ] Robin Taylor commented on DS-852: - Changes committed to trunk, version 6384. Note. Any references to flag webui.submit.enable-cc can now be deleted from the code and config. I'll do this once MIT's Creative Commons work is committed. > Split the Creative Commons and Licence steps into two seperate steps. > - > > Key: DS-852 > URL: https://jira.duraspace.org/browse/DS-852 > Project: DSpace > Issue Type: Improvement > Components: XMLUI >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 1.8.0 > > Attachments: Add_CC_License_Step.patch, CCLicenseStep.java, > CCLicenseStep.java, item-submission.xml, JSPCCLicenseStep.java, > JSPLicenseStep.java, LicenseStep.java, LicenseStep.java > > > At the moment I'm just looking for comments as I may have misunderstood the > code, but it seems to me that.. > The Creative Commons step and the Licence step are somewhat artificially > grouped together as one step in item-submission.xml. In order for this to > work there is a test at the start of LicenseStep that checks to see if > webui.submit.enable-cc is set to true in dspace.cfg and if so then control is > effectively passed to CCLicenseStep. It would be simpler if these classes > were completely independent of each other and defined as separate steps in > item-submission.xml. It would also mean we could remove the unneccessary flag > webui.submit.enable-cc from dspace.cfg. -- 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] Closed: (DS-825) Market ticket for work being done to allow the user to select licences other than those offered by Creative Commons.
[ https://jira.duraspace.org/browse/DS-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor closed DS-825. --- Resolution: Won't Fix No longer a priority for my own institution. > Market ticket for work being done to allow the user to select licences other > than those offered by Creative Commons. > > > Key: DS-825 > URL: https://jira.duraspace.org/browse/DS-825 > Project: DSpace > Issue Type: Improvement > Components: DSpace API >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 1.8.0 > > > Create a new Licence Service that manages the retrieval of licence > information from a number of sources, not just the Creative Commons website. > I am aware of the work being done at MIT to revamp the existing CC but I > don't foresee a conflict. > I would be grateful for any comments, positive or negative. -- 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] Resolved: (DS-780) MetadataExposure.java doesn't check the boolean value of hidden field in dspace.cfg
[ https://jira.duraspace.org/browse/DS-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor resolved DS-780. - Resolution: Duplicate Fix Version/s: 1.8.0 Please correct me if I am wrong but I believe this bug was fixed by Kim Shepherd in DS-853 (release 1.7.1). I've just tested on trunk and it appears to be working with the default XMLUI theme. > MetadataExposure.java doesn't check the boolean value of hidden field in > dspace.cfg > --- > > Key: DS-780 > URL: https://jira.duraspace.org/browse/DS-780 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.6.2 >Reporter: Samuel Ottenhoff >Assignee: Robin Taylor > Fix For: 1.8.0 > > > To replicate > 1) Add item to DSpace > 2) Set metadata.hide.dc.description.provenance = false in dspace.cfg > 3) Restart > 4) View full item as anonymous 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 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] Assigned: (DS-634) Improvment to OAI-PMH + OAI-ORE harvesting support
[ https://jira.duraspace.org/browse/DS-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor reassigned DS-634: --- Assignee: (was: Robin Taylor) Returned status to unassigned as I have no plans to do this work in the foreseeable future. > Improvment to OAI-PMH + OAI-ORE harvesting support > -- > > Key: DS-634 > URL: https://jira.duraspace.org/browse/DS-634 > Project: DSpace > Issue Type: New Feature > Components: OAI-PMH >Affects Versions: 1.6.2 > Environment: All >Reporter: Paul Brindley > > At the moment the OAI-PMH + OAI-ORE harvester will allow the admin to harvest > from an external source and to set up a scheduled harvest. However it would > be nice to be able to specify different frequencys for different collections. -- 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-724) createAdministrators() and createSubmitters() should not add policies if the associated group already exists
[ https://jira.duraspace.org/browse/DS-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20424#action_20424 ] Robin Taylor commented on DS-724: - Hi Andreas, The patch looks sensible, however, I can't figure out when the error condition would ever occur. Looking at the code it looks like createSubmitters() and create createAdministrators() can only ever get called once. Did you have a real world example or did you just notice that the code was inconsistent ? Thanks, Robin. > createAdministrators() and createSubmitters() should not add policies if the > associated group already exists > > > Key: DS-724 > URL: https://jira.duraspace.org/browse/DS-724 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.6.2 >Reporter: Andreas Schwander >Assignee: Robin Taylor > Attachments: Collection.patch > > > New policies will be created when the methods createAdministrators() and > createSubmitters() in org.dspace.content.Collection will be called even if > the administrators or the submitters group already exists. > These methods should just return the group if one exists and should not > update the database or add policies. -- 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-724) createAdministrators() and createSubmitters() should not add policies if the associated group already exists
[ https://jira.duraspace.org/browse/DS-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20485#action_20485 ] Robin Taylor commented on DS-724: - In conclusion, Andreas is correct in that the code is inconsistent. My own preference would be that if the groups already exist then the methods should throw an Exception if someone calls them, rather than returning the existing groups. If I'm feeling brave one day I'll make the change, but since the errors don't actually occur within the existing code I'll not rush into it. > createAdministrators() and createSubmitters() should not add policies if the > associated group already exists > > > Key: DS-724 > URL: https://jira.duraspace.org/browse/DS-724 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.6.2 >Reporter: Andreas Schwander >Assignee: Robin Taylor > Attachments: Collection.patch > > > New policies will be created when the methods createAdministrators() and > createSubmitters() in org.dspace.content.Collection will be called even if > the administrators or the submitters group already exists. > These methods should just return the group if one exists and should not > update the database or add policies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-724) createAdministrators() and createSubmitters() should not add policies if the associated group already exists
[ https://jira.duraspace.org/browse/DS-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-724: Status: Open (was: Received) > createAdministrators() and createSubmitters() should not add policies if the > associated group already exists > > > Key: DS-724 > URL: https://jira.duraspace.org/browse/DS-724 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.6.2 >Reporter: Andreas Schwander >Assignee: Robin Taylor > Attachments: Collection.patch > > > New policies will be created when the methods createAdministrators() and > createSubmitters() in org.dspace.content.Collection will be called even if > the administrators or the submitters group already exists. > These methods should just return the group if one exists and should not > update the database or add policies. -- 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-818) Asynchronous Release
[ https://jira.duraspace.org/browse/DS-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20550#action_20550 ] Robin Taylor commented on DS-818: - Hi Mark, Overall looks good. Creating a project with IDEA and default settings it complained because there was no Pom at the top level. I changed the setting to search recursively and it worked fine. Trivial but it did lead me to wonder if we could move dspace to the top of the directory structure. I haven't thought this one out properly. Wouldn't build for me initially as modules/cli/pom.xml was empty, so I commented out that project from dspace/modules/pom.xml and built fine. I notice modules/pom.xml now has the dspace-parent as a dependency but the likes of dspace-xmlui still have dspace-parent as a parent, is the intention to change them all have dspace-parent as a depency rather than a parent ? Cheers, Robin. > Asynchronous Release > > > Key: DS-818 > URL: https://jira.duraspace.org/browse/DS-818 > Project: DSpace > Issue Type: New Feature > Components: Documentation, DSpace API, JSPUI, Language Packs, LNI, > OAI-PMH, REST API (experimental), Solr, SWORD, Unit Testing Framework, XMLUI >Reporter: Mark Diggory >Assignee: Mark Diggory >Priority: Major > Fix For: 1.8.0 > > > Asynchronous Release: Asynchronous Release is change in the DSpace release > process and version numbering process on modules within the DSpace trunk to > allow more flexibility adding prebuilt Addon modules into DSpace. > Goals > The primary goal of Async release is to break the the authoritative grip that > dspace-parent has on the version assignment and dependencyManagement in the > DSpace trunk modules such that: > Make the build in the DSpace Modules Source Tree dependent on a specific > dspace-api and dspace-xmlui-api versions. Specifically, dspace-statistics and > dspace-discovery > Make a packaged release of DSpace that includes a combination of Trunk and > Module projects. > More easily package releases of DSpace cyclically while allowing minor > updates of core modules to occur more often, to easily provide a minor update > path for DSpace. > View wiki page for further details. > https://wiki.duraspace.org/display/DSPACE/Asynchronous+Release -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-922) REST-API In an Item query the metadata is exposed as one String rather than as discrete Xml elements
REST-API In an Item query the metadata is exposed as one String rather than as discrete Xml elements Key: DS-922 URL: https://jira.duraspace.org/browse/DS-922 Project: DSpace Issue Type: Bug Components: REST API (experimental) Reporter: Robin Taylor Class ItemEntity calls XHTMLHeadDisseminationCrosswalk to create the metadata XML. This crosswalk was written to add the metadata as a String in the section of an html page and is probably not the correct crosswalk to use for the REST API. Below is a cut and pasted chunk from a REST API query which shows the metadata as a string containing escape characters.
[Dspace-devel] [DuraSpace JIRA] Created: (DS-923) REST-API Currently exposes and uses the internal DSpace database object id.
REST-API Currently exposes and uses the internal DSpace database object id. --- Key: DS-923 URL: https://jira.duraspace.org/browse/DS-923 Project: DSpace Issue Type: Bug Components: REST API (experimental) Reporter: Robin Taylor The internal database id's are currently exposed in responses to the REST API eg 58 In fact the internal id appended to the URL to limit the query to one object http://localhost:8080/rest/items/58.xml Should we be exposing internal id's or should we only be using handles ? My knee jerk reaction says handles but that would preclude exposing items which are still in submission or workflow and therefore do not yet have a handle. -- 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 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-926) REST-API The .xml or .json options cause the URl to be messy if an object is specified
REST-API The .xml or .json options cause the URl to be messy if an object is specified -- Key: DS-926 URL: https://jira.duraspace.org/browse/DS-926 Project: DSpace Issue Type: Bug Components: REST API (experimental) Reporter: Robin Taylor The request for all items is formed... http://localhost:8080/rest/items.xml but the rest for item with id 58 is... http://localhost:8080/rest/items/58.xml That's a bit ugly. Could/should the requests be formed as http://localhost:8080/rest/items/58?format=xml ? -- 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 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-927) REST-API All item submitter information is returned for an item request, even for an anonymous request.
REST-API All item submitter information is returned for an item request, even for an anonymous request. --- Key: DS-927 URL: https://jira.duraspace.org/browse/DS-927 Project: DSpace Issue Type: Bug Components: REST API (experimental) Reporter: Robin Taylor If I enter a request for a specific item eg. http://localhost:8080/rest/items/58.xml the response includes all the ePerson information for the person that submitted the request. This info is not visible in the UI and I suspect should not be exposed here, at least not to a non-administrator. robin.tay...@ed.ac.uk Robin Robin Taylor 1 en Taylor robin.tay...@ed.ac.uk false false 7 -- 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 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-924) ItemImport should allow you to import to a workspace
[ https://jira.duraspace.org/browse/DS-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20640#action_20640 ] Robin Taylor commented on DS-924: - Yes please. Did a similar thing once to allow users to add files to uploaded metadata only items. > ItemImport should allow you to import to a workspace > > > Key: DS-924 > URL: https://jira.duraspace.org/browse/DS-924 > Project: DSpace > Issue Type: Improvement >Reporter: Graham Triggs >Assignee: Graham Triggs > > Currently, ItemImport can import items directly into the archive, or push > them through a workflow. It would be useful if you could import into a user's > workspace but not push through to the workflow allowing for final > modifications before granting the license. > This is a tiny change to the importer - I already have the modifications, > just need a little bit of work before applying them to trunk. -- 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 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-926) REST-API The .xml or .json options cause the URl to be messy if an object is specified
[ https://jira.duraspace.org/browse/DS-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20644#action_20644 ] Robin Taylor commented on DS-926: - Cut and pasted from an email from Vibhaj Rajan... Hi Robin, I am not well experienced with REST technology but feel that this is the correct way of looking at a resource oriented architecture which REST promotes. More Details : http://microformats.org/wiki/rest/urls Warm Regards, > REST-API The .xml or .json options cause the URl to be messy if an object is > specified > -- > > Key: DS-926 > URL: https://jira.duraspace.org/browse/DS-926 > Project: DSpace > Issue Type: Bug > Components: REST API (experimental) >Reporter: Robin Taylor > > The request for all items is formed... > http://localhost:8080/rest/items.xml > but the rest for item with id 58 is... > http://localhost:8080/rest/items/58.xml > That's a bit ugly. Could/should the requests be formed as > http://localhost:8080/rest/items/58?format=xml ? -- 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 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-928) REST-API NullPointerException thrown for a request for a specific community if there are no community admistrators
REST-API NullPointerException thrown for a request for a specific community if there are no community admistrators -- Key: DS-928 URL: https://jira.duraspace.org/browse/DS-928 Project: DSpace Issue Type: Bug Components: REST API (experimental) Reporter: Robin Taylor On my local machine a request for http://localhost:8080/rest/communities/1.xml throws a NullPointerException in CommunityEntity. The problem is that res.getAdministrators() can legitimately return a null if there are no administrators for that Community. Instantiating GroupEntity with a null causes the Exception. this.administrators = includeFull ? new GroupEntity(res.getAdministrators(), level, uparams) : new GroupEntityId(res.getAdministrators()); We need to change the code to include a check - res.getAdministrators() != 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 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-928) REST-API NullPointerException thrown for a request for a specific community if there are no community admistrators
[ https://jira.duraspace.org/browse/DS-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20675#action_20675 ] Robin Taylor commented on DS-928: - Just noticed Peter Dietz has a fix for this in Github https://gist.github.com/952058 that has since been apllied to Subversion. > REST-API NullPointerException thrown for a request for a specific community > if there are no community admistrators > -- > > Key: DS-928 > URL: https://jira.duraspace.org/browse/DS-928 > Project: DSpace > Issue Type: Bug > Components: REST API (experimental) >Reporter: Robin Taylor > > On my local machine a request for > http://localhost:8080/rest/communities/1.xml throws a NullPointerException in > CommunityEntity. The problem is that res.getAdministrators() can legitimately > return a null if there are no administrators for that Community. > Instantiating GroupEntity with a null causes the Exception. > this.administrators = includeFull ? new GroupEntity(res.getAdministrators(), > level, uparams) : new GroupEntityId(res.getAdministrators()); > We need to change the code to include a check - res.getAdministrators() != > 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 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Closed: (DS-928) REST-API NullPointerException thrown for a request for a specific community if there are no community admistrators
[ https://jira.duraspace.org/browse/DS-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor closed DS-928. --- Resolution: Fixed Already fixed. > REST-API NullPointerException thrown for a request for a specific community > if there are no community admistrators > -- > > Key: DS-928 > URL: https://jira.duraspace.org/browse/DS-928 > Project: DSpace > Issue Type: Bug > Components: REST API (experimental) >Reporter: Robin Taylor > > On my local machine a request for > http://localhost:8080/rest/communities/1.xml throws a NullPointerException in > CommunityEntity. The problem is that res.getAdministrators() can legitimately > return a null if there are no administrators for that Community. > Instantiating GroupEntity with a null causes the Exception. > this.administrators = includeFull ? new GroupEntity(res.getAdministrators(), > level, uparams) : new GroupEntityId(res.getAdministrators()); > We need to change the code to include a check - res.getAdministrators() != > 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 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-923) REST-API Currently exposes and uses the internal DSpace database object id.
[ https://jira.duraspace.org/browse/DS-923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20677#action_20677 ] Robin Taylor commented on DS-923: - I suspect I am talking crap here (not unusual). I guess there is no issue in using the internal id's in URLs here since they are not meant to be persistent URLs ? Apologies for thinking this through in a Jira issue. > REST-API Currently exposes and uses the internal DSpace database object id. > --- > > Key: DS-923 > URL: https://jira.duraspace.org/browse/DS-923 > Project: DSpace > Issue Type: Bug > Components: REST API (experimental) >Reporter: Robin Taylor > > The internal database id's are currently exposed in responses to the REST API > eg 58 > In fact the internal id appended to the URL to limit the query to one object > http://localhost:8080/rest/items/58.xml > Should we be exposing internal id's or should we only be using handles ? My > knee jerk reaction says handles but that would preclude exposing items which > are still in submission or workflow and therefore do not yet have a handle. -- 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 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-935) REST-API Has a dependency on the dspace-jspui-api, it would be nice if this could be removed.
REST-API Has a dependency on the dspace-jspui-api, it would be nice if this could be removed. --- Key: DS-935 URL: https://jira.duraspace.org/browse/DS-935 Project: DSpace Issue Type: Improvement Components: REST API (experimental) Reporter: Robin Taylor It would be nice to remove the dependency on the dspace-jspui-api to allow for a distribution without the Jspui. The only place I know of a real dependency at the moment is in the use of the RecentSubmissions class, but there may be others. -- 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 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-935) REST-API Has a dependency on the dspace-jspui-api, it would be nice if this could be removed.
[ https://jira.duraspace.org/browse/DS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20715#action_20715 ] Robin Taylor commented on DS-935: - Those classes in package org.dspace.app.webui.components that are not directly related to the jspui should be moved into dspace-api (that itself may be a temporary move until a common business logic layer comes into being). This would allow us to remove the dependency. > REST-API Has a dependency on the dspace-jspui-api, it would be nice if this > could be removed. > --- > > Key: DS-935 > URL: https://jira.duraspace.org/browse/DS-935 > Project: DSpace > Issue Type: Improvement > Components: REST API (experimental) >Reporter: Robin Taylor > > It would be nice to remove the dependency on the dspace-jspui-api to allow > for a distribution without the Jspui. The only place I know of a real > dependency at the moment is in the use of the RecentSubmissions class, but > there may be others. -- 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 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-935) REST-API Has a dependency on the dspace-jspui-api, it would be nice if this could be removed.
[ https://jira.duraspace.org/browse/DS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20726#action_20726 ] Robin Taylor commented on DS-935: - Specifically, I would like to move classes.. RecentSubmissionsManager RecentSubmissions RecentSubmissionsException out of the dspace-jspui-api and into dspace-api. Any objections ? Cheers, Robin. > REST-API Has a dependency on the dspace-jspui-api, it would be nice if this > could be removed. > --- > > Key: DS-935 > URL: https://jira.duraspace.org/browse/DS-935 > Project: DSpace > Issue Type: Improvement > Components: REST API (experimental) >Reporter: Robin Taylor > > It would be nice to remove the dependency on the dspace-jspui-api to allow > for a distribution without the Jspui. The only place I know of a real > dependency at the moment is in the use of the RecentSubmissions class, but > there may be others. -- 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 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Assigned: (DS-819) Metadata Masking
[ https://jira.duraspace.org/browse/DS-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor reassigned DS-819: --- Assignee: Robin Taylor > Metadata Masking > > > Key: DS-819 > URL: https://jira.duraspace.org/browse/DS-819 > Project: DSpace > Issue Type: New Feature > Components: DSpace API >Reporter: Joseph Rhoads >Assignee: Robin Taylor > > Dear Dspace community, > I'm working on a project that needs to have different layers of access to > metadata fields. (ie. Only certain people/groups should have access to > certain metadata fields). I'm wondering if any in the dspace community have > any ideas or experiences with this sort of thing? I'm gonna throw out some > ideas to see if anyone is interested. > I know that there are currently a couple of options related to items access, > + You can let anonymous users view some info in the search/browse results > + Then approved users/groups can have full-item read access (minus fields > that are designated for administrators) > + Administrators can see all fields (including those designated > metadata.hide. in the dspace.cfg file.) > What I'm thinking about includes the following: > + Adding the ability to create masks or streams of masks that can be applied > at the community or collection level, and to specific groups. > + Each mask would simply be a set of (metadata key, boolean value) pairs > + I think collection administrators should be able to edit the masks though > the web interface > + And that the OAI indexing should be viewed as another group or person for > this purpose. > I have some questions: > + Should the mask be on the display end(post SQL request) or the request > end(pre SQL request)? > + Presumably these masks would be persistent, where should they be stored? > This topic is related to the following JIRA issues > https://jira.duraspace.org/browse/DS-800 > https://jira.duraspace.org/browse/DS-716 > https://jira.duraspace.org/browse/DS-655 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-935) REST-API Has a dependency on the dspace-jspui-api, it would be nice if this could be removed.
[ https://jira.duraspace.org/browse/DS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-935: Assignee: Robin Taylor Status: Open (was: Received) > REST-API Has a dependency on the dspace-jspui-api, it would be nice if this > could be removed. > --- > > Key: DS-935 > URL: https://jira.duraspace.org/browse/DS-935 > Project: DSpace > Issue Type: Improvement > Components: REST API (experimental) >Reporter: Robin Taylor >Assignee: Robin Taylor > > It would be nice to remove the dependency on the dspace-jspui-api to allow > for a distribution without the Jspui. The only place I know of a real > dependency at the moment is in the use of the RecentSubmissions class, but > there may be others. -- 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 the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense.. http://p.sf.net/sfu/splunk-d2d-c1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-935) REST-API Has a dependency on the dspace-jspui-api, it would be nice if this could be removed.
[ https://jira.duraspace.org/browse/DS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20775#action_20775 ] Robin Taylor commented on DS-935: - The best existing package I can find for them is org.dspace.browse, any objections ? > REST-API Has a dependency on the dspace-jspui-api, it would be nice if this > could be removed. > --- > > Key: DS-935 > URL: https://jira.duraspace.org/browse/DS-935 > Project: DSpace > Issue Type: Improvement > Components: REST API (experimental) >Reporter: Robin Taylor >Assignee: Robin Taylor > > It would be nice to remove the dependency on the dspace-jspui-api to allow > for a distribution without the Jspui. The only place I know of a real > dependency at the moment is in the use of the RecentSubmissions class, but > there may be others. -- 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 the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense.. http://p.sf.net/sfu/splunk-d2d-c1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-935) REST-API Has a dependency on the dspace-jspui-api, it would be nice if this could be removed.
[ https://jira.duraspace.org/browse/DS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20785#action_20785 ] Robin Taylor commented on DS-935: - Hi Richard and Tim, That sounds fine to me. I'll bring it up in the meeting on Wednesday. Cheers. > REST-API Has a dependency on the dspace-jspui-api, it would be nice if this > could be removed. > --- > > Key: DS-935 > URL: https://jira.duraspace.org/browse/DS-935 > Project: DSpace > Issue Type: Improvement > Components: REST API (experimental) >Reporter: Robin Taylor >Assignee: Robin Taylor > > It would be nice to remove the dependency on the dspace-jspui-api to allow > for a distribution without the Jspui. The only place I know of a real > dependency at the moment is in the use of the RecentSubmissions class, but > there may be others. -- 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-941) Marker ticket for splitting up the dspace.cfg.
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=20810#action_20810 ] Robin Taylor commented on DS-941: - Sword Server config moved to modules/sword-server.cfg. Committed to trunk rev 6446. > 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] Updated: (DS-941) Marker ticket for splitting up the dspace.cfg.
[ https://jira.duraspace.org/browse/DS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-941: Status: Open (was: Received) > 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] Updated: (DS-942) dspace.oai.url is currently generated from ${dspace.baseUrl}. Change the code to assume this unless overridden.
[
https://jira.duraspace.org/browse/DS-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Taylor updated DS-942:
Status: Open (was: Received)
> dspace.oai.url is currently generated from ${dspace.baseUrl}. Change the code
> to assume this unless overridden.
> ---
>
> Key: DS-942
> URL: https://jira.duraspace.org/browse/DS-942
> Project: DSpace
> Issue Type: Improvement
>Reporter: Robin Taylor
>Assignee: Robin Taylor
> Fix For: 1.8.0
>
>
> In order to separate out the entire OAI config from dspace config I would
> like to change the code so that it builds OAI url by reading dspace.baseUrl
> in the code and appending /oai, unless the URL has been overridden in config.
> This will mimic what happens for Sword and with the URL no longer being
> constructed by filtering it can be moved in with the rest of the OAI config.
--
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-942) dspace.oai.url is currently generated from ${dspace.baseUrl}. Change the code to assume this unless overridden.
dspace.oai.url is currently generated from ${dspace.baseUrl}. Change the code
to assume this unless overridden.
---
Key: DS-942
URL: https://jira.duraspace.org/browse/DS-942
Project: DSpace
Issue Type: Improvement
Reporter: Robin Taylor
Assignee: Robin Taylor
Fix For: 1.8.0
In order to separate out the entire OAI config from dspace config I would like
to change the code so that it builds OAI url by reading dspace.baseUrl in the
code and appending /oai, unless the URL has been overridden in config. This
will mimic what happens for Sword and with the URL no longer being constructed
by filtering it can be moved in with the rest of the OAI config.
--
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-942) dspace.oai.url is currently generated from ${dspace.baseUrl}. Change the code to assume this unless overridden.
[
https://jira.duraspace.org/browse/DS-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20818#action_20818
]
Robin Taylor commented on DS-942:
-
Doh ! I didn't know it was sophisticated enough to filter the contents of one
file based on values in another file. Thanks for putting me right.
> dspace.oai.url is currently generated from ${dspace.baseUrl}. Change the code
> to assume this unless overridden.
> ---
>
> Key: DS-942
> URL: https://jira.duraspace.org/browse/DS-942
> Project: DSpace
> Issue Type: Improvement
>Reporter: Robin Taylor
>Assignee: Robin Taylor
> Fix For: 1.8.0
>
>
> In order to separate out the entire OAI config from dspace config I would
> like to change the code so that it builds OAI url by reading dspace.baseUrl
> in the code and appending /oai, unless the URL has been overridden in config.
> This will mimic what happens for Sword and with the URL no longer being
> constructed by filtering it can be moved in with the rest of the OAI config.
--
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-942) dspace.oai.url is currently generated from ${dspace.baseUrl}. Change the code to assume this unless overridden.
[
https://jira.duraspace.org/browse/DS-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Taylor resolved DS-942.
-
Resolution: Won't Fix
> dspace.oai.url is currently generated from ${dspace.baseUrl}. Change the code
> to assume this unless overridden.
> ---
>
> Key: DS-942
> URL: https://jira.duraspace.org/browse/DS-942
> Project: DSpace
> Issue Type: Improvement
>Reporter: Robin Taylor
>Assignee: Robin Taylor
> Fix For: 1.8.0
>
>
> In order to separate out the entire OAI config from dspace config I would
> like to change the code so that it builds OAI url by reading dspace.baseUrl
> in the code and appending /oai, unless the URL has been overridden in config.
> This will mimic what happens for Sword and with the URL no longer being
> constructed by filtering it can be moved in with the rest of the OAI config.
--
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=20820#action_20820 ] Robin Taylor commented on DS-941: - OAI-PMH and OAI-ORE config moved to modules/oai.cfg. Committed to trunk rev 6447 > 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=20847#action_20847 ] Robin Taylor commented on DS-941: - Solr Stats config moved to dspace-solr-stats.cfg. Committed to trunk rev 6448. > 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-935) REST-API Has a dependency on the dspace-jspui-api, it would be nice if this could be removed.
[ https://jira.duraspace.org/browse/DS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20878#action_20878 ] Robin Taylor commented on DS-935: - In accordance with the decision made in the developers meeting I have copied the necessary classes from jspui to REST api. Committed to REST api module revision 6450. > REST-API Has a dependency on the dspace-jspui-api, it would be nice if this > could be removed. > --- > > Key: DS-935 > URL: https://jira.duraspace.org/browse/DS-935 > Project: DSpace > Issue Type: Improvement > Components: REST API (experimental) >Reporter: Robin Taylor >Assignee: Robin Taylor > > It would be nice to remove the dependency on the dspace-jspui-api to allow > for a distribution without the Jspui. The only place I know of a real > dependency at the moment is in the use of the RecentSubmissions class, but > there may be others. -- 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-922) REST-API In an Item query the metadata is exposed as one String rather than as discrete Xml elements
[ https://jira.duraspace.org/browse/DS-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20889#action_20889 ] Robin Taylor commented on DS-922: - I've done a bit more digging. The REST Api is built on http://code.google.com/p/entitybus/. Following the conventions used so far we would add a new Entity called MetadataEntity (effectively a pojo) with members of schema, element (possibly qualifier), and value. The entitybus libraries take care of serializing those objects into xml or json. The resulting XML would look like ... blah bloh bluh some text We don't really have the option of specifying DC or anything else since the code that builds the XML is buried in the entitybus libraries. Not too sure where that leaves us. > REST-API In an Item query the metadata is exposed as one String rather than > as discrete Xml elements > > > Key: DS-922 > URL: https://jira.duraspace.org/browse/DS-922 > Project: DSpace > Issue Type: Bug > Components: REST API (experimental) >Reporter: Robin Taylor > > Class ItemEntity calls XHTMLHeadDisseminationCrosswalk to create the metadata > XML. This crosswalk was written to add the metadata as a String in the > section of an html page and is probably not the correct crosswalk to use for > the REST API. Below is a cut and pasted chunk from a REST API query which > shows the metadata as a string containing escape characters. > /> /> We need to decide on a suitable format for exposing the metadata. Should we > default to DC ? How should this then be exposed if the request specifies Json > ? -- 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-922) REST-API In an Item query the metadata is exposed as one String rather than as discrete Xml elements
[ https://jira.duraspace.org/browse/DS-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20890#action_20890 ] Robin Taylor commented on DS-922: - Let me expand on that a little - we can fill up those members with any text we like, which could be DC, but we can't impose namespaces since that is done elsewhere. > REST-API In an Item query the metadata is exposed as one String rather than > as discrete Xml elements > > > Key: DS-922 > URL: https://jira.duraspace.org/browse/DS-922 > Project: DSpace > Issue Type: Bug > Components: REST API (experimental) >Reporter: Robin Taylor > > Class ItemEntity calls XHTMLHeadDisseminationCrosswalk to create the metadata > XML. This crosswalk was written to add the metadata as a String in the > section of an html page and is probably not the correct crosswalk to use for > the REST API. Below is a cut and pasted chunk from a REST API query which > shows the metadata as a string containing escape characters. > /> /> We need to decide on a suitable format for exposing the metadata. Should we > default to DC ? How should this then be exposed if the request specifies Json > ? -- 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-922) REST-API In an Item query the metadata is exposed as one String rather than as discrete Xml elements
[ https://jira.duraspace.org/browse/DS-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-922: Attachment: rest-metadata.png Hi Hayden, I have hastily hacked the code and attached a screenshot to give you an idea of what the returned xml would look like. Cheers, Robin. > REST-API In an Item query the metadata is exposed as one String rather than > as discrete Xml elements > > > Key: DS-922 > URL: https://jira.duraspace.org/browse/DS-922 > Project: DSpace > Issue Type: Bug > Components: REST API (experimental) >Reporter: Robin Taylor > Attachments: rest-metadata.png > > > Class ItemEntity calls XHTMLHeadDisseminationCrosswalk to create the metadata > XML. This crosswalk was written to add the metadata as a String in the > section of an html page and is probably not the correct crosswalk to use for > the REST API. Below is a cut and pasted chunk from a REST API query which > shows the metadata as a string containing escape characters. > /> /> We need to decide on a suitable format for exposing the metadata. Should we > default to DC ? How should this then be exposed if the request specifies Json > ? -- 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=20926#action_20926 ] Robin Taylor commented on DS-941: - Hi Stuart, Looks like you are right. I certainly hadn't understood that, I thought dspace.cfg could be split up without any recoding. To be fair Richard Rodgers sent me an email that explains quite clearly that is not the case, I just hadn't read it properly. So what to do ? For the stuff that has been split out already Sword, OAI, and some Solr stuff, I think it would be a fairly minor job to fix the code, which I'll happily do. It may mean that splitting up the JSPUI and XMLUI config is delayed as that is a bigger job. With regards to what the code changes should be, well maybe this is a good opportunity to switch to using the Configuration Service, I'll investigate. Cheers, Robin. > 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=20967#action_20967 ] Robin Taylor commented on DS-941: - Fixed the OIA module to correctly pick up the config from oai.cfg. Committed to trunk revision 6454. > 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-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=20966#action_20966 ] Robin Taylor commented on DS-708: - It also makes reference to parameter oai.mets.hide-provenance which is no longer visible to it since the OAI config was split out of dspace.cfg. > 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 -- 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-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=20996#action_20996 ] Robin Taylor commented on DS-708: - So, if this Jira isn't resolved for 1.8 we need to reinstate the parameter oai.mets.hide-provenance. > 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 -- 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-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=21027#action_21027 ] Robin Taylor commented on DS-708: - I would be happy with option A. I think dc.description.provenance is generally misused in DSpace. I suspect it is mostly used to record actions that have happened to the object eg deposited by Joe Bloggs on 25/12/2000. In the long run its probably more appropriate that that kind of information is recorded in an audit trail, or possibly in a 'DSpace admin metadata schema'. In the meantime its probably the lesser of two evils to always exclude it when generating Mods XML. Cheers. > Deprecate & Remove old 'org.dspace.app.mets.METSExport' class, as it is > obsolete > > > Key: DS-708 > URL: https://jira.duraspace.org/browse/DS-708 > Project: DSpace > Issue Type: Code Task > Components: DSpace API, OAI-PMH >Affects Versions: 1.7.0 >Reporter: Tim Donohue >Assignee: Tim Donohue > Fix For: 1.8.0 > > Attachments: DS-708-dspace-api.patch, DS-708-dspace-oai-api.patch, > sample-mods-properties.patch > > > With the improvements that have happened to the METS Ingest and Dissemination > packager classes in DSpace 1.7.0 (see DS-466), we should deprecate & remove > the old 'org.dspace.app.mets.METSExport' class, as it is now considered > obsolete. > This older METSExport class is currently used in the following places: > * OAI-PMH interface (by the org.dspace.app.oai.METSCrosswalk class) > My proposal is to deprecate this class in DSpace 1.7.0, and then work to > remove & replace its usage within the OAI-PMH interface in the next major > version of DSpace (1.8.0). > The replacement for METSExport is the following classes: > * org.dspace.content.packager.DSpaceMETSDisseminator > * org.dspace.content.packager.DSpaceMETSIngester -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-922) REST-API In an Item query the metadata is exposed as one String rather than as discrete Xml elements
[ https://jira.duraspace.org/browse/DS-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-922: Attachment: DS-922.patch Attached patch to return metadata as discrete elements. If nobody objects I will commit shortly. > REST-API In an Item query the metadata is exposed as one String rather than > as discrete Xml elements > > > Key: DS-922 > URL: https://jira.duraspace.org/browse/DS-922 > Project: DSpace > Issue Type: Bug > Components: REST API (experimental) >Reporter: Robin Taylor > Attachments: DS-922.patch, rest-metadata.png > > > Class ItemEntity calls XHTMLHeadDisseminationCrosswalk to create the metadata > XML. This crosswalk was written to add the metadata as a String in the > section of an html page and is probably not the correct crosswalk to use for > the REST API. Below is a cut and pasted chunk from a REST API query which > shows the metadata as a string containing escape characters. > /> /> We need to decide on a suitable format for exposing the metadata. Should we > default to DC ? How should this then be exposed if the request specifies Json > ? -- 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=21030#action_21030 ] Robin Taylor commented on DS-941: - Fixed the Sword Server to correctly pick up its config from sword-server.cfg. Committed to trunk 6457. > 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] Created: (DS-948) Migrate the REST code to new directory modules/dspace-rest
Migrate the REST code to new directory modules/dspace-rest -- Key: DS-948 URL: https://jira.duraspace.org/browse/DS-948 Project: DSpace Issue Type: Improvement Components: REST API (experimental) Reporter: Robin Taylor Assignee: Robin Taylor Create a new directory modules/dspace-rest in line with the naming convention for all the other supported DSpace modules. If memory serves me right this was to leave room for modules developed and supported elsewhere but housed with the DSpace svn space. -- 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-948) Migrate the REST code to new directory modules/dspace-rest
[ https://jira.duraspace.org/browse/DS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21052#action_21052 ] Robin Taylor commented on DS-948: - Hi Mark, It was just a vague recollection of an informal conversation that took place as part of a developer meeting quite a while back. If I remember correctly it was to allow for third party supported modules and to allow someone selecting modules to be able to distinguish at a glance between those modules supported by the 'DSpace developers' and those supported by third parties. As an aside I very much agree that unsupported, experimental modules should live in the sandbox and not in the modules directory. Cheers, Robin. > Migrate the REST code to new directory modules/dspace-rest > -- > > Key: DS-948 > URL: https://jira.duraspace.org/browse/DS-948 > Project: DSpace > Issue Type: Improvement > Components: REST API (experimental) >Reporter: Robin Taylor >Assignee: Robin Taylor > > Create a new directory modules/dspace-rest in line with the naming convention > for all the other supported DSpace modules. If memory serves me right this > was to leave room for modules developed and supported elsewhere but housed > with the DSpace svn space. -- 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-948) Migrate the REST code to new directory modules/dspace-rest
[ https://jira.duraspace.org/browse/DS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21108#action_21108 ] Robin Taylor commented on DS-948: - My reasons for wanting to rename this module are... 1. It seems to me a good convention that the created artifacts are prefixed by 'dspace-'. Its helpful if the modules that generate those artifacts are called the same thing. 2. It does allow for other non DSpace modules in the same space if we ever decide to allow for that. 3. Whilst not all modules currently residing in the modules directory are prefixed by 'dspace-', all those currently distributed with DSpace are, so it would maintain that convention. Cheers. > Migrate the REST code to new directory modules/dspace-rest > -- > > Key: DS-948 > URL: https://jira.duraspace.org/browse/DS-948 > Project: DSpace > Issue Type: Improvement > Components: REST API (experimental) >Reporter: Robin Taylor >Assignee: Robin Taylor > > Create a new directory modules/dspace-rest in line with the naming convention > for all the other supported DSpace modules. If memory serves me right this > was to leave room for modules developed and supported elsewhere but housed > with the DSpace svn space. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-948) Migrate the REST code to new directory modules/dspace-rest
[ https://jira.duraspace.org/browse/DS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21109#action_21109 ] Robin Taylor commented on DS-948: - And one last thing ! The most recent version of the DSpace REST code is held in https://scm.dspace.org/svn/repo/modules/rest/branches/dspace-rest-gsoc10. It looks like this wasn't actually branched from the trunk code, I guess it was checked out from trunk and then checked in to the branch. So the code that is in trunk is way out of date and has no direct connection to the branch. In order to make trunk the current version the sensible thing to do would be to delete the existing trunk and recreate it by checking out the branch and then checking it into trunk. Its all a bit messy, I would prefer to create a new module called dspace-rest with trunk created by checking in the contents of the current active branch. The existing module could then be mothballed. Cheers, Robin. > Migrate the REST code to new directory modules/dspace-rest > -- > > Key: DS-948 > URL: https://jira.duraspace.org/browse/DS-948 > Project: DSpace > Issue Type: Improvement > Components: REST API (experimental) >Reporter: Robin Taylor >Assignee: Robin Taylor > > Create a new directory modules/dspace-rest in line with the naming convention > for all the other supported DSpace modules. If memory serves me right this > was to leave room for modules developed and supported elsewhere but housed > with the DSpace svn space. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-815) DCDate throws NullPointerException with mangled dates
[ https://jira.duraspace.org/browse/DS-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21193#action_21193 ] Robin Taylor commented on DS-815: - Just a quick comment. There have been a number of attempts to incorporate date validation into DCDate, by Kim Shepherd and myself that I know of, that have proved fruitless. The reason being that the UI metadata pages only allow for a check on the presence of a value or not, there is no current way to indicate to the user that the value failed some validation test. This applies to all the metadata fields, not just dates. For that reason it serves no purpose to return any indication of an invalid date to the UI metadata input code because there is no way of passing on that information to the user. The UI currently insists on a year so I would be interested to know how the data was entered. Whilst a shared validation solution would be ideal the best quick fix might be to plug whatever gap allowed this dodgy data to be loaded. Cheers, Robin. > DCDate throws NullPointerException with mangled dates > - > > Key: DS-815 > URL: https://jira.duraspace.org/browse/DS-815 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.7.0 > Environment: CentOS 5.4 with OpenJDK 64-Bit Server VM (build > 1.6.0-b09, mixed mode) >Reporter: Àlex Magaz Graça >Assignee: Mark H. Wood > Attachments: DCDate_test_mangled_date.patch > > > DCDate.get*() methods throw a NullPointerException if the object has been > constructed with a wrong date like "[17--?]" (DCDateTest patch attached): > java.lang.NullPointerException > at org.dspace.content.DCDate.getYear(DCDate.java:298) > at org.dspace.content.DCDateTest.testDCDateString(DCDateTest.java:301) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) > at > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) > at > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) > at org.apache.maven.surefire.Surefire.run(Surefire.java:177) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) > at > org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) > It makes the browse by issue date fail in JSPUI. -- 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] Commented: (DS-950) Update OAI-PMH to fully obey 'metadata.hide.SCHEMA.ELEMENT.QUALIFIER' configuration settings
[ https://jira.duraspace.org/browse/DS-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21231#action_21231 ] Robin Taylor commented on DS-950: - Hi Tim, I would be in favour of commenting out provenance from mods.properties. Personally I'm not too big a fan of MetadataExposure so I would be happy if its usage wasn't extended. Cheers, Robin. > Update OAI-PMH to fully obey 'metadata.hide.SCHEMA.ELEMENT.QUALIFIER' > configuration settings > > > Key: DS-950 > URL: https://jira.duraspace.org/browse/DS-950 > Project: DSpace > Issue Type: Improvement > Components: OAI-PMH >Affects Versions: 1.7.0, 1.7.1, 1.7.2 >Reporter: Tim Donohue >Assignee: Tim Donohue > Fix For: 1.8.0 > > > This improvement came up as a sub-part of DS-708 (Deprecate & Remove old > 'org.dspace.app.mets.METSExport' class) > Essentially, most of the OAI-PMH interface does not obey the > metadata.hide.SCHEMA.ELEMENT.QUALIFIER settings in dspace.cfg. This is even > detailed in the dspace.cfg notes that say: > # Hide Item Metadata Fields # > # Fields named here are hidden in the following places UNLESS the > # logged-in user is an Administrator: > # 1. XMLUI metadata XML view, and Item splash pages (long and short views). > # 2. JSPUI Item splash pages > # 3. OAI-PMH server, "oai_dc" format. > # (NOTE: Other formats are _not_ affected.) > # To designate a field as hidden, add a property here in the form: > #metadata.hide.SCHEMA.ELEMENT.QUALIFIER = true > # > # This default configuration hides the dc.description.provenance field, > # since that usually contains email addresses which ought to be kept > # private and is mainly of interest to administrators: > metadata.hide.dc.description.provenance = true > The idea here is to actually make ALL of the OAI-PMH server's formats > (oai_dc, mets, rdf, etc) obey this setting. In addition, this allows us to > cleanup the old "oai.mets.hide-provenance" setting which was previously used > by the METS/MODS format from OAI-PMH (see DS-708) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks & Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Assigned: (DS-848) Add MARCXML crosswalk for OAI-PMH
[ https://jira.duraspace.org/browse/DS-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor reassigned DS-848: --- Assignee: Robin Taylor > Add MARCXML crosswalk for OAI-PMH > - > > Key: DS-848 > URL: https://jira.duraspace.org/browse/DS-848 > Project: DSpace > Issue Type: New Feature > Components: OAI-PMH >Reporter: Timo Aalto >Assignee: Robin Taylor > Attachments: DIM2MARC21slim.xsl > > > This is something that I and several others have asked several times on > DSpace Listservs over the years. Incidentally there is an implementation > already available in the TDL Vireo ETD solution just waiting for to be > included in DSpace proper. I don't have a patch but below are the > instructions I made for a colleague on how to enable the crosswalk. All > credit for the xwalk development belong to the TDL Vireo team, I'm just a > messenger here :) > 1) Add to dspace.cfg (crosswalks section): > ## > ## Configure XSLT-driven submission crosswalk for MARC21 > ## > crosswalk.dissemination.marc.stylesheet = crosswalks/DIM2MARC21slim.xsl > crosswalk.dissemination.marc.schemaLocation = http://www.loc.gov/MARC21/slim \ > http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd > crosswalk.dissemination.marc.preferList = true > 2) Add to oaicat.properties: > Crosswalks.marc=org.dspace.app.oai.PluginCrosswalk > 3) Add the enclosed crosswalk XSL to the config/crosswalks dir. > (Note that the copyright and/or licensing for the attached XSL is unknown to > me, admins should probably remove it if it's not A-ok) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks & Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-848) Add MARCXML crosswalk for OAI-PMH
[ https://jira.duraspace.org/browse/DS-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-848: Reviewer: robintaylor Status: Open (was: Received) > Add MARCXML crosswalk for OAI-PMH > - > > Key: DS-848 > URL: https://jira.duraspace.org/browse/DS-848 > Project: DSpace > Issue Type: New Feature > Components: OAI-PMH >Reporter: Timo Aalto >Assignee: Robin Taylor > Attachments: DIM2MARC21slim.xsl > > > This is something that I and several others have asked several times on > DSpace Listservs over the years. Incidentally there is an implementation > already available in the TDL Vireo ETD solution just waiting for to be > included in DSpace proper. I don't have a patch but below are the > instructions I made for a colleague on how to enable the crosswalk. All > credit for the xwalk development belong to the TDL Vireo team, I'm just a > messenger here :) > 1) Add to dspace.cfg (crosswalks section): > ## > ## Configure XSLT-driven submission crosswalk for MARC21 > ## > crosswalk.dissemination.marc.stylesheet = crosswalks/DIM2MARC21slim.xsl > crosswalk.dissemination.marc.schemaLocation = http://www.loc.gov/MARC21/slim \ > http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd > crosswalk.dissemination.marc.preferList = true > 2) Add to oaicat.properties: > Crosswalks.marc=org.dspace.app.oai.PluginCrosswalk > 3) Add the enclosed crosswalk XSL to the config/crosswalks dir. > (Note that the copyright and/or licensing for the attached XSL is unknown to > me, admins should probably remove it if it's not A-ok) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks & Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-815) DCDate throws NullPointerException with mangled dates
[ https://jira.duraspace.org/browse/DS-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21235#action_21235 ] Robin Taylor commented on DS-815: - Hi all, There were a bunch of date related issues resolved for 1.7. It would be worth giving them a quick review. I suspect the underlying problem here is that the data is being bulk imported and so doesn't use DCDate at all when being imported. I have reservations about patching over this just for Browse. I suspect the problems caused by bad data will keep bubbling up in different places (now Browse, but later OAI, etc etc). We need to prevent people importing bad data. Of course that is easier said than done :) Cheers. > DCDate throws NullPointerException with mangled dates > - > > Key: DS-815 > URL: https://jira.duraspace.org/browse/DS-815 > Project: DSpace > Issue Type: Bug > Components: DSpace API >Affects Versions: 1.7.0 > Environment: CentOS 5.4 with OpenJDK 64-Bit Server VM (build > 1.6.0-b09, mixed mode) >Reporter: Àlex Magaz Graça >Assignee: Mark H. Wood > Attachments: DCDate_test_mangled_date.patch > > > DCDate.get*() methods throw a NullPointerException if the object has been > constructed with a wrong date like "[17--?]" (DCDateTest patch attached): > java.lang.NullPointerException > at org.dspace.content.DCDate.getYear(DCDate.java:298) > at org.dspace.content.DCDateTest.testDCDateString(DCDateTest.java:301) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) > at > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) > at > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) > at org.apache.maven.surefire.Surefire.run(Surefire.java:177) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:616) > at > org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) > at > org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) > It makes the browse by issue date fail in JSPUI. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks & Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/ ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-922) REST-API In an Item query the metadata is exposed as one String rather than as discrete Xml elements
[ https://jira.duraspace.org/browse/DS-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-922: Assignee: Robin Taylor Status: Open (was: Received) > REST-API In an Item query the metadata is exposed as one String rather than > as discrete Xml elements > > > Key: DS-922 > URL: https://jira.duraspace.org/browse/DS-922 > Project: DSpace > Issue Type: Bug > Components: REST API (experimental) >Reporter: Robin Taylor >Assignee: Robin Taylor > Attachments: DS-922.patch, rest-metadata.png > > > Class ItemEntity calls XHTMLHeadDisseminationCrosswalk to create the metadata > XML. This crosswalk was written to add the metadata as a String in the > section of an html page and is probably not the correct crosswalk to use for > the REST API. Below is a cut and pasted chunk from a REST API query which > shows the metadata as a string containing escape characters. > /> /> We need to decide on a suitable format for exposing the metadata. Should we > default to DC ? How should this then be exposed if the request specifies Json > ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-974) REST API - Tidy up pom.xml and update version to be 1.8.0-SNAPSHOT
[ https://jira.duraspace.org/browse/DS-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-974: Assignee: Robin Taylor Status: Open (was: Received) > REST API - Tidy up pom.xml and update version to be 1.8.0-SNAPSHOT > -- > > Key: DS-974 > URL: https://jira.duraspace.org/browse/DS-974 > Project: DSpace > Issue Type: Improvement > Components: REST API (experimental) >Reporter: Robin Taylor >Assignee: Robin Taylor > > Tidy up pom.xml and update version to be 1.8.0-SNAPSHOT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-974) REST API - Tidy up pom.xml and update version to be 1.8.0-SNAPSHOT
REST API - Tidy up pom.xml and update version to be 1.8.0-SNAPSHOT -- Key: DS-974 URL: https://jira.duraspace.org/browse/DS-974 Project: DSpace Issue Type: Improvement Components: REST API (experimental) Reporter: Robin Taylor Tidy up pom.xml and update version to be 1.8.0-SNAPSHOT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-974) REST API - Tidy up pom.xml and update version to be 1.8.0-SNAPSHOT
[ https://jira.duraspace.org/browse/DS-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21393#action_21393 ] Robin Taylor commented on DS-974: - Committed to trunk revision 6513. > REST API - Tidy up pom.xml and update version to be 1.8.0-SNAPSHOT > -- > > Key: DS-974 > URL: https://jira.duraspace.org/browse/DS-974 > Project: DSpace > Issue Type: Improvement > Components: REST API (experimental) >Reporter: Robin Taylor >Assignee: Robin Taylor > > Tidy up pom.xml and update version to be 1.8.0-SNAPSHOT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-922) REST-API In an Item query the metadata is exposed as one String rather than as discrete Xml elements
[ https://jira.duraspace.org/browse/DS-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor resolved DS-922. - Resolution: Fixed Fix Version/s: 1.8.0 Committed patch to modules/dspace-rest/trunk - revision 6515. > REST-API In an Item query the metadata is exposed as one String rather than > as discrete Xml elements > > > Key: DS-922 > URL: https://jira.duraspace.org/browse/DS-922 > Project: DSpace > Issue Type: Bug > Components: REST API (experimental) >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 1.8.0 > > Attachments: DS-922.patch, rest-metadata.png > > > Class ItemEntity calls XHTMLHeadDisseminationCrosswalk to create the metadata > XML. This crosswalk was written to add the metadata as a String in the > section of an html page and is probably not the correct crosswalk to use for > the REST API. Below is a cut and pasted chunk from a REST API query which > shows the metadata as a string containing escape characters. > /> /> We need to decide on a suitable format for exposing the metadata. Should we > default to DC ? How should this then be exposed if the request specifies Json > ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-975) REST API - remove some stray files from the module
[ https://jira.duraspace.org/browse/DS-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-975: Assignee: Robin Taylor Status: Open (was: Received) > REST API - remove some stray files from the module > -- > > Key: DS-975 > URL: https://jira.duraspace.org/browse/DS-975 > Project: DSpace > Issue Type: Improvement >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 1.8.0 > > > Remove the following files from the module - collection.java.add.txt, > nb-configuration.xml, nbactions.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-975) REST API - remove some stray files from the module
REST API - remove some stray files from the module -- Key: DS-975 URL: https://jira.duraspace.org/browse/DS-975 Project: DSpace Issue Type: Improvement Reporter: Robin Taylor Fix For: 1.8.0 Remove the following files from the module - collection.java.add.txt, nb-configuration.xml, nbactions.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-975) REST API - remove some stray files from the module
[ https://jira.duraspace.org/browse/DS-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor resolved DS-975. - Resolution: Fixed Committed to modules/dspace-rest, revision 6516. > REST API - remove some stray files from the module > -- > > Key: DS-975 > URL: https://jira.duraspace.org/browse/DS-975 > Project: DSpace > Issue Type: Improvement >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 1.8.0 > > > Remove the following files from the module - collection.java.add.txt, > nb-configuration.xml, nbactions.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-974) REST API - Tidy up pom.xml and update version to be 1.8.0-SNAPSHOT
[ https://jira.duraspace.org/browse/DS-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor resolved DS-974. - Resolution: Fixed Fix Version/s: 1.8.0 > REST API - Tidy up pom.xml and update version to be 1.8.0-SNAPSHOT > -- > > Key: DS-974 > URL: https://jira.duraspace.org/browse/DS-974 > Project: DSpace > Issue Type: Improvement > Components: REST API (experimental) >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 1.8.0 > > > Tidy up pom.xml and update version to be 1.8.0-SNAPSHOT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Closed: (DS-935) REST-API Has a dependency on the dspace-jspui-api, it would be nice if this could be removed.
[ https://jira.duraspace.org/browse/DS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor closed DS-935. --- > REST-API Has a dependency on the dspace-jspui-api, it would be nice if this > could be removed. > --- > > Key: DS-935 > URL: https://jira.duraspace.org/browse/DS-935 > Project: DSpace > Issue Type: Improvement > Components: REST API (experimental) >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 1.8.0 > > > It would be nice to remove the dependency on the dspace-jspui-api to allow > for a distribution without the Jspui. The only place I know of a real > dependency at the moment is in the use of the RecentSubmissions class, but > there may be others. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-935) REST-API Has a dependency on the dspace-jspui-api, it would be nice if this could be removed.
[ https://jira.duraspace.org/browse/DS-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor resolved DS-935. - Resolution: Fixed Fix Version/s: 1.8.0 > REST-API Has a dependency on the dspace-jspui-api, it would be nice if this > could be removed. > --- > > Key: DS-935 > URL: https://jira.duraspace.org/browse/DS-935 > Project: DSpace > Issue Type: Improvement > Components: REST API (experimental) >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 1.8.0 > > > It would be nice to remove the dependency on the dspace-jspui-api to allow > for a distribution without the Jspui. The only place I know of a real > dependency at the moment is in the use of the RecentSubmissions class, but > there may be others. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Closed: (DS-974) REST API - Tidy up pom.xml and update version to be 1.8.0-SNAPSHOT
[ https://jira.duraspace.org/browse/DS-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor closed DS-974. --- Documentation Status: Not Required (was: Needed) > REST API - Tidy up pom.xml and update version to be 1.8.0-SNAPSHOT > -- > > Key: DS-974 > URL: https://jira.duraspace.org/browse/DS-974 > Project: DSpace > Issue Type: Improvement > Components: REST API (experimental) >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 1.8.0 > > > Tidy up pom.xml and update version to be 1.8.0-SNAPSHOT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Assigned: (DS-873) Creative commons license bundle on embargoed item will cause internal system errors on item pages
[ https://jira.duraspace.org/browse/DS-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor reassigned DS-873: --- Assignee: Robin Taylor > Creative commons license bundle on embargoed item will cause internal system > errors on item pages > - > > Key: DS-873 > URL: https://jira.duraspace.org/browse/DS-873 > Project: DSpace > Issue Type: Bug > Components: DSpace API, JSPUI >Affects Versions: 1.8.0 >Reporter: Kevin Van de Velde >Assignee: Robin Taylor > Attachments: creative_commons_embargo_bugfix.patch > > > When an item has a creative commons license and the item is under embargo the > DefaultEmbargoSetter will also remove the anonymous read rights from the > creative commons bundle. > On the display item jsp it will attempt to retrieve the creative commons url > (see lines below) and these will cause an authorize exception which in turn > will lead to an internal system error (unless the admin is logged in). > String cc_url = CreativeCommons.getLicenseURL(item); > String cc_rdf = CreativeCommons.getLicenseRDF(item); > I have attached a patch to fix this issue (if required I am also willing to > upload a script that can fix the permissions on these license bundles). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-873) Creative commons license bundle on embargoed item will cause internal system errors on item pages
[ https://jira.duraspace.org/browse/DS-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-873: Status: Open (was: Received) > Creative commons license bundle on embargoed item will cause internal system > errors on item pages > - > > Key: DS-873 > URL: https://jira.duraspace.org/browse/DS-873 > Project: DSpace > Issue Type: Bug > Components: DSpace API, JSPUI >Affects Versions: 1.8.0 >Reporter: Kevin Van de Velde >Assignee: Robin Taylor > Attachments: creative_commons_embargo_bugfix.patch > > > When an item has a creative commons license and the item is under embargo the > DefaultEmbargoSetter will also remove the anonymous read rights from the > creative commons bundle. > On the display item jsp it will attempt to retrieve the creative commons url > (see lines below) and these will cause an authorize exception which in turn > will lead to an internal system error (unless the admin is logged in). > String cc_url = CreativeCommons.getLicenseURL(item); > String cc_rdf = CreativeCommons.getLicenseRDF(item); > I have attached a patch to fix this issue (if required I am also willing to > upload a script that can fix the permissions on these license bundles). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-964) Implement Creative Commons Web Service API with the Submission Process
[ https://jira.duraspace.org/browse/DS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-964: Status: Open (was: Received) > Implement Creative Commons Web Service API with the Submission Process > -- > > Key: DS-964 > URL: https://jira.duraspace.org/browse/DS-964 > Project: DSpace > Issue Type: Improvement > Components: Documentation, DSpace API, XMLUI >Reporter: Wendy Bossons > Attachments: cclicense_1-5.diff, CreativeCommons_1-8_Patch.tar.gz, > dspace-cclicense-1.0.jar, dspace-cclicense-1.0.tar, README.txt > > > Creative Commons hosts a web service that can supply the user interface > elements that DSpace needs to provide a complete user experience in DSpace, > with respect to the Creative Commons license step. This patch implements the > Creative Commons web service api to support the user interface selections, > item view and search. > DSpace currently takes an integration approach to selecting a Creative > Commons (CC) license during the submission process that results in an awkward > user experience. This patch proposes to simplify the user experience through > implementing the CC License API in the submission process. This patch also > adds searchability to the CCLicensed items by storing the license uri as > metadata. > As well, the license rdf acquisition is separated from the submission process > into a curation task. > A future CC task(s) may address the issue of updating or migrating existing > CC license data. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Assigned: (DS-964) Implement Creative Commons Web Service API with the Submission Process
[ https://jira.duraspace.org/browse/DS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor reassigned DS-964: --- Assignee: Robin Taylor > Implement Creative Commons Web Service API with the Submission Process > -- > > Key: DS-964 > URL: https://jira.duraspace.org/browse/DS-964 > Project: DSpace > Issue Type: Improvement > Components: Documentation, DSpace API, XMLUI >Reporter: Wendy Bossons >Assignee: Robin Taylor > Attachments: cclicense_1-5.diff, CreativeCommons_1-8_Patch.tar.gz, > dspace-cclicense-1.0.jar, dspace-cclicense-1.0.tar, README.txt > > > Creative Commons hosts a web service that can supply the user interface > elements that DSpace needs to provide a complete user experience in DSpace, > with respect to the Creative Commons license step. This patch implements the > Creative Commons web service api to support the user interface selections, > item view and search. > DSpace currently takes an integration approach to selecting a Creative > Commons (CC) license during the submission process that results in an awkward > user experience. This patch proposes to simplify the user experience through > implementing the CC License API in the submission process. This patch also > adds searchability to the CCLicensed items by storing the license uri as > metadata. > As well, the license rdf acquisition is separated from the submission process > into a curation task. > A future CC task(s) may address the issue of updating or migrating existing > CC license data. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-964) Implement Creative Commons Web Service API with the Submission Process
[
https://jira.duraspace.org/browse/DS-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21458#action_21458
]
Robin Taylor commented on DS-964:
-
Hi Wendy,
Just looking over the patch, looks great. Just one wee query which I think
betrays my lack of knowledge on the XMLUI. I notice that you have amended the
Wing class Select to add an 'onchange' attribute to the generated html 'select'
element. Am I correct in saying it is there to allow for the following line in
CCLicenseStep ?
selectList.setOnchange("this.form.button_required.disabled=\"true\";this.form.submit();");
I am wondering if this might alternatively be done in the XSL? My understanding
of the original XMLUI design was that the Wing components would be structural
with the transformation to presentational (html) taking place in the XSL. To be
honest I think that idea has already been compromised in a number of places but
it may be a good thing to stick with the plan if at all possible. So, I guess
the alternative would be to code something in the XSL to look for the
'submit-cclicense' div and add the onchange attribute at that point ?
Please do tell me if I am talking nonsense (very likely!). I would be grateful
for comment from anyone with a better knowledge of the XMLUI that I.
Cheers, Robin.
> Implement Creative Commons Web Service API with the Submission Process
> --
>
> Key: DS-964
> URL: https://jira.duraspace.org/browse/DS-964
> Project: DSpace
> Issue Type: Improvement
> Components: Documentation, DSpace API, XMLUI
>Reporter: Wendy Bossons
>Assignee: Robin Taylor
> Attachments: cclicense_1-5.diff, CreativeCommons_1-8_Patch.tar.gz,
> dspace-cclicense-1.0.jar, dspace-cclicense-1.0.tar, README.txt
>
>
> Creative Commons hosts a web service that can supply the user interface
> elements that DSpace needs to provide a complete user experience in DSpace,
> with respect to the Creative Commons license step. This patch implements the
> Creative Commons web service api to support the user interface selections,
> item view and search.
> DSpace currently takes an integration approach to selecting a Creative
> Commons (CC) license during the submission process that results in an awkward
> user experience. This patch proposes to simplify the user experience through
> implementing the CC License API in the submission process. This patch also
> adds searchability to the CCLicensed items by storing the license uri as
> metadata.
> As well, the license rdf acquisition is separated from the submission process
> into a curation task.
> A future CC task(s) may address the issue of updating or migrating existing
> CC license data.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-602) Marker ticket for developing a Sword client for DSpace.
[ https://jira.duraspace.org/browse/DS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21460#action_21460 ] Robin Taylor commented on DS-602: - Any objections if I move this code out of sandbox and into 'trunk' ? Cheers, Robin. > Marker ticket for developing a Sword client for DSpace. > --- > > Key: DS-602 > URL: https://jira.duraspace.org/browse/DS-602 > Project: DSpace > Issue Type: New Feature > Components: SWORD >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 1.8.0 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-602) Marker ticket for developing a Sword client for DSpace.
[ https://jira.duraspace.org/browse/DS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21483#action_21483 ] Robin Taylor commented on DS-602: - Moved to trunk revision 6533. Please note :- There is a bug in the 'select collection' page that results in the first collection listed always being selected, should be fixed before you can say "Why do I find the XMLUI so complicated?". > Marker ticket for developing a Sword client for DSpace. > --- > > Key: DS-602 > URL: https://jira.duraspace.org/browse/DS-602 > Project: DSpace > Issue Type: New Feature > Components: SWORD >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 1.8.0 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-602) Marker ticket for developing a Sword client for DSpace.
[ https://jira.duraspace.org/browse/DS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21497#action_21497 ] Robin Taylor commented on DS-602: - Please note:- I have not as yet added the sword Client module as a dependency to either the dspace-parent or dspace pom's, just because of a lack of understanding on my part. To be revisited before 1.8 release. > Marker ticket for developing a Sword client for DSpace. > --- > > Key: DS-602 > URL: https://jira.duraspace.org/browse/DS-602 > Project: DSpace > Issue Type: New Feature > Components: SWORD >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 1.8.0 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] (DS-1032) DIDL Crosswalk exporting data without escaping specific XML chars
Robin Taylor assigned DS-1032 to Robin Taylor DIDL Crosswalk exporting data without escaping specific XML chars Change By: Robin Taylor (30/May/12 8:15 PM) Assignee: Robin Taylor 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-1190) Add Google Analytics tracking code to header-default.jsp
Robin Taylor created DS-1190: Summary: Add Google Analytics tracking code to header-default.jsp Key: DS-1190 URL: https://jira.duraspace.org/browse/DS-1190 Project: DSpace Issue Type: Improvement Components: JSPUI Reporter: Robin Taylor Assignee: Robin Taylor Fix For: 3.0 Allow the user to turn on GA tracking by configuration. -- 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-1190) Add Google Analytics tracking code to header-default.jsp
[ https://jira.duraspace.org/browse/DS-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25315#comment-25315 ] Robin Taylor commented on DS-1190: -- Hi Denys and Ivan, just wanted to say thanks for doing all the real work, it sounds just like what is needed. Cheers. > Add Google Analytics tracking code to header-default.jsp > > > Key: DS-1190 > URL: https://jira.duraspace.org/browse/DS-1190 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 3.0 > > > Allow the user to turn on GA tracking by configuration. -- 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-1172) Add basic Spring based DAOs
[ https://jira.duraspace.org/browse/DS-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25330#comment-25330 ] Robin Taylor commented on DS-1172: -- https://github.com/DSpace/DSpace/pull/22 > Add basic Spring based DAOs > > > Key: DS-1172 > URL: https://jira.duraspace.org/browse/DS-1172 > Project: DSpace > Issue Type: Improvement >Reporter: Robin Taylor >Assignee: Robin Taylor > > A marker ticket for work being done to introduce DAOs. -- 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-1208) Build time filtering to allow multi developer/environment builds
[ https://jira.duraspace.org/browse/DS-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor reassigned DS-1208: Assignee: Robin Taylor > Build time filtering to allow multi developer/environment builds > > > Key: DS-1208 > URL: https://jira.duraspace.org/browse/DS-1208 > Project: DSpace > Issue Type: Bug >Reporter: Steve Swinsburg >Assignee: Robin Taylor > > The addition of properly placeholders in dspace.cfg goes some of the way to > allowing multiple developers/environments to use the same source tree, > however not enough properties have been externalised. > For example,if I had 5 servers, how would I customise this property for each? > dspace.baseUrl = http://localhost:8080 > In addition, the current setup requires the build to activate a maven > profile, and supply properties either at build time or from a pom.xml, which > are then hardcoded. > This isn't as flexible as it could be, for example by putting all > configurable properties into a build.properties/filter.properties file and > keeping that out of source control. > Then each developer simply customises the properties file with the values for > their environment, and the build inserts the properties into the relevant > source files at build time. > This is a standard maven filtering approach in use by many other projects. > Note that any number of files can be filtered using this approach. > References: > http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html -- 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-825) Market ticket for work being done to allow the user to select licences other than those offered by Creative Commons.
[ https://jira.duraspace.org/browse/DS-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor updated DS-825: Fix Version/s: (was: 3.0) No longer scheduled for 3.0 > Market ticket for work being done to allow the user to select licences other > than those offered by Creative Commons. > > > Key: DS-825 > URL: https://jira.duraspace.org/browse/DS-825 > Project: DSpace > Issue Type: Improvement > Components: DSpace API >Reporter: Robin Taylor >Assignee: Robin Taylor > > Create a new Licence Service that manages the retrieval of licence > information from a number of sources, not just the Creative Commons website. > I am aware of the work being done at MIT to revamp the existing CC but I > don't foresee a conflict. > I would be grateful for any comments, positive or negative. -- 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-1127) Submission improvements: document type-based submission
[ https://jira.duraspace.org/browse/DS-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor reassigned DS-1127: Assignee: Robin Taylor > Submission improvements: document type-based submission > --- > > Key: DS-1127 > URL: https://jira.duraspace.org/browse/DS-1127 > Project: DSpace > Issue Type: Improvement > Components: DSpace API, XMLUI >Affects Versions: 1.8.0, 1.8.1, 1.8.2 >Reporter: Nestor Oviedo >Assignee: Robin Taylor >Priority: Major > Attachments: type-based-submission-classes.zip, > type-based-submission-diff-files.zip > > > Document type-based submission > As outlined in > https://wiki.duraspace.org/display/DSPACE/Document+Type+Based+Submission, > many repositories deal with several document types and the only approach > DSpace has to offer so far is a collection based form definition. > We found the following initiatives: https://jira.duraspace.org/browse/DS-464 > and https://wiki.duraspace.org/display/DSPACE/Document+Type+Based+Submission > , but they are very old and it is very hard to integrate one of them in our > 1.8.0 DSpace. Along with this problematic integration we also need some other > features to the submission process, which made the integration yet more > complicated. > These initiatives propose to define a type-based form and/or pages, but we > thought this would lead to a very complicated and redundant form definition, > provided most document types share a lot of common fields. To avoid this > replication, we propose to have a type-based field definition in the form > configuration (input-forms.xml). That is, defining the forms and pages fields > in the normal way, and only specify a type-restriction on those fields which > are specific for some kind of document. > The following excerpt is an example o a form definition: > > > > dc > type > Document type > > > > > > > > > > theses > director > Thesis director > theses > > > > > The visibility of the type-based field depends on the dc.type field's value. > This requires the dc.type metadata must be fullfilled before the rendering of > any page with any type-based field. > This approach allows you to mix fields, even though they are restricted to a > document type. Also, you can define multiple document types in the > element, separated with a colon (,). i.e > > dc > identifier.isbn > ISBN > theses,ebook > > Other improvements > Considering we have now a type-based submission, we need to be able to define > the same field for different document types, with different attributes. A > clear example of this in our repository is the ISBN metadata: theses may have > an ISBN metadata while books must have it. Also, the label and hint of these > fields could be different. To achieve this we avoided the limitation on field > duplicity, allowing to define the same field multiple times. > Another minor improvement proposed here was previously mentioned by Claudia > Jürgen in https://jira.duraspace.org/browse/DS-334. We agree with Claudia in > that the visibility and the required attribute are not related directly, so > we removed that validation. We consider that the mandatory restriction makes > sense only when the field is visible in a scope. Thus it is completely valid > to define a visibility scope along with a required attribute. > Attachments > Here you can find two attachments: a zip containing the modified classes, and > another zip containing the diff for all the modified classes (this diff was > made against the 1.8.0 version). > We attached diff files for you to have a quick overview of the changes made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___
[Dspace-devel] [DuraSpace JIRA] (DS-1190) Add Google Analytics tracking code to header-default.jsp
[ https://jira.duraspace.org/browse/DS-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor reassigned DS-1190: Assignee: Robin Taylor (was: Ivan Masár) > Add Google Analytics tracking code to header-default.jsp > > > Key: DS-1190 > URL: https://jira.duraspace.org/browse/DS-1190 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 3.0 > > > Allow the user to turn on GA tracking by configuration. -- 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-1190) Add Google Analytics tracking code to header-default.jsp
[ https://jira.duraspace.org/browse/DS-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Taylor resolved DS-1190. -- Resolution: Fixed Hi all, I hope you don't mind but given the impending feature freeze I created a another pull request and merged it. Many thanks for the code and discussion. Cheers, Robin. > Add Google Analytics tracking code to header-default.jsp > > > Key: DS-1190 > URL: https://jira.duraspace.org/browse/DS-1190 > Project: DSpace > Issue Type: Improvement > Components: JSPUI >Reporter: Robin Taylor >Assignee: Robin Taylor > Fix For: 3.0 > > > Allow the user to turn on GA tracking by configuration. -- 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
