[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 head 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. metadatalt;link rel=schema.DCTERMS href=http://purl.org/dc/terms/; /gt;lt;link rel=schema.DC href=http://purl.org/dc/elements/1.1/; /gt;lt;meta name=DC.creator content=dfgdgd, dfgdf 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 -- 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-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 id type=number58/id 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-924) ItemImport should allow you to import to a workspace
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] Created: (DS-925) ItemImport does not delete items that weren't placed into the archive
ItemImport does not delete items that weren't placed into the archive - Key: DS-925 URL: https://jira.duraspace.org/browse/DS-925 Project: DSpace Issue Type: Bug Reporter: Graham Triggs -- 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] Updated: (DS-925) ItemImport does not delete items that weren't placed into the archive
[ https://jira.duraspace.org/browse/DS-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs updated DS-925: - Documentation Status: Not Required (was: Needed) Component/s: DSpace API Description: If you don't import items directly into the archive, then the delete function (when given a map file) does not remove the items from DSpace. The code currently just gets the collections for an item, then deletes the item from all collections. It doesn't take into account the possibility of workspace / workflow wrappers. And whilst it doesn't actually remove any items, it does report as if it had. Affects Version/s: 1.5.0 1.5.1 1.5.2 1.6.0 1.6.1 1.6.2 1.7.0 1.7.1 ItemImport does not delete items that weren't placed into the archive - Key: DS-925 URL: https://jira.duraspace.org/browse/DS-925 Project: DSpace Issue Type: Bug Components: DSpace API Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0, 1.7.1 Reporter: Graham Triggs If you don't import items directly into the archive, then the delete function (when given a map file) does not remove the items from DSpace. The code currently just gets the collections for an item, then deletes the item from all collections. It doesn't take into account the possibility of workspace / workflow wrappers. And whilst it doesn't actually remove any items, it does report as if it had. -- 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. submitter type=bean size=12 emailrobin.tay...@ed.ac.uk/email firstNameRobin/firstName fullNameRobin Taylor/fullName handle/ id type=number1/id languageen/language lastNameTaylor/lastName namerobin.tay...@ed.ac.uk/name netId/ requireCertificate type=booleanfalse/requireCertificate selfRegistered type=booleanfalse/selfRegistered type type=number7/type /submitter -- 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-tabpanelfocusedCommentId=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
Re: [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
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, On Thu, Jun 16, 2011 at 5:59 PM, Robin Taylor (DuraSpace JIRA) no-re...@duraspace.org wrote: 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 -- *Vibhaj Rajan Junior Undergraduate Department of Computer Engineering Institute of Technology BHU Varanasi +91 92 3531 2784 * -- 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-tabpanelfocusedCommentId=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] Closed: (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:all-tabpanel ] Tim Donohue closed DS-926. -- Resolution: Answered I'm going to go ahead and close this issue mark it as answered. I think Vibhaj Rajan is correct in that the REST API is following the best practices for REST URLs: http://microformats.org/wiki/rest/urls If there are any additional concerns, we can always re-open this issue as necessary. 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] Closed: (DS-917) Dspace 1.7.1 recent submission in latest item it display previous item which inputed previous time
[ https://jira.duraspace.org/browse/DS-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Donohue closed DS-917. -- Documentation Status: Not Required (was: Needed) Resolution: Answered Assignee: Tim Donohue Hi ATUL, This bug was actually fixed in DSpace 1.7.2. There was a problem in DSpace 1.7.1 where the recent submissions listing was accidentally being cached (and didn't update properly). For more information, please see https://jira.duraspace.org/browse/DS-871 So, we'd recommend upgrading to 1.7.2 in order to resolve this recent submission caching issue. Let us know if you have further questions. - Tim Dspace 1.7.1 recent submission in latest item it display previous item which inputed previous time --- Key: DS-917 URL: https://jira.duraspace.org/browse/DS-917 Project: DSpace Issue Type: Bug Reporter: ATUL Assignee: Tim Donohue Priority: Major My Dspace 1.7.1 have not display recent submission in latest item it display previous item which inputed previos time -- 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
