DSpace
  1. DSpace
  2. DS-466

Add ability to export/import entire Community/Collection/Item structure (for easier backups, migrations, etc.)

    Details

    • Type: New Feature New Feature
    • Status: Closed Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Fixed
    • Fix Version/s: 1.7.0
    • Component/s: DSpace API
    • Labels:
      None
    • Attachments:
      0
    • Comments:
      4

      Description

      This comes out of a requirement for DSpace integration with DuraCloud (http://www.duraspace.org/duracloud.php). One of these requirements is to be able to essentially "backup" local DSpace contents into the cloud (as a type of offsite backup), and "restore" those contents at a later time.

      Essentially, we'd like a way to be able to export the entire hierarchy (i.e. bitstreams, metadata and relationships between Communities/Collections/Items) into a relatively standard format (e.g. METS or similar structured packaging format). This entire hierarchy should also be able to be re-imported into DSpace in the same format, to allow for "roundtripping" of that content (essentially a restore of that content in the same or different DSpace installation).

      Perceived benefits to DSpace community:
      * Would allow folks to more easily move entire Communities or Collections between DSpace instances.
      * Would allow for a potentially more consistent backup of this hierarchy (e.g. to DuraCloud, or just to your own local backup system), rather than relying on synchronizing a backup of your DB (metadata/relationships) and assetstore (bitstreams).
      * Would provide a way for people to more easily get their data out of DSpace (whatever the purpose may be).
      * Would provide a relatively standard format for people to migrate entire hierarchies (Communities/Collections) into DSpace (from another system).

      Known Issues:
      * Exporting/Importing the Community/Collection/Item hierarchy technically doesn't cover all the "content" held in DSpace. There are also Groups, EPeople and permissions/rights (which would get you closer to a full export/import of all DSpace content). However, concentrating on just the hierarchy of Community/Collection/Item seems like a good first step.

      This is related to (and a partial subset of) MIT's AIP Prototype: http://jira.dspace.org/jira/browse/DS-465 However, the AIP prototype currently does not make it very easy to re-import the exported AIPs for Communities or Collections. So, this feature would extend on the AIP prototype's current packagers/crosswalks to allow for an full export and import of an entire DSpace hierarchy, or just a set of Communities, Collections or Items.

      My current plan is to build off of the subset of the AIP prototype (essentially the packagers, crosswalks and related changes) which begins to allow for this roundtripping of Communities and Collections. I'll be adding a new SVN sandbox area for this work (so that others can help out, if it interests them). If anyone has comments, suggestions or feedback on this idea, or would like to be involved in this project, definitely let me know (or add comments to this issue).

      This work is being prototyped in the SVN Sandbox at:
      http://scm.dspace.org/svn/repo/sandbox/aip-external-1_6-prototype/

      More details on this project available on the Wiki at:
      http://wiki.dspace.org/confluence/display/DSPACE/AipBackupRestorePrototype

        Issue Links

          Activity

          Tim Donohue made changes -
          Field Original Value New Value
          Link This issue is related to DS-465 [ DS-465 ]
          Hide
          Tim Donohue added a comment -
          Added reference to the prototype's SVN Sandbox location in description above:
          http://scm.dspace.org/svn/repo/sandbox/aip-external-1_6-prototype/
          Show
          Tim Donohue added a comment - Added reference to the prototype's SVN Sandbox location in description above: http://scm.dspace.org/svn/repo/sandbox/aip-external-1_6-prototype/
          Tim Donohue made changes -
          Description This comes out of a requirement for DSpace integration with DuraCloud (http://www.duraspace.org/duracloud.php). One of these requirements is to be able to essentially "backup" local DSpace contents into the cloud (as a type of offsite backup), and "restore" those contents at a later time.

          Essentially, we'd like a way to be able to export the entire hierarchy (i.e. bitstreams, metadata and relationships between Communities/Collections/Items) into a relatively standard format (e.g. METS or similar structured packaging format). This entire hierarchy should also be able to be re-imported into DSpace in the same format, to allow for "roundtripping" of that content (essentially a restore of that content in the same or different DSpace installation).

          Perceived benefits to DSpace community:
          * Would allow folks to more easily move entire Communities or Collections between DSpace instances.
          * Would allow for a potentially more consistent backup of this hierarchy (e.g. to DuraCloud, or just to your own local backup system), rather than relying on synchronizing a backup of your DB (metadata/relationships) and assetstore (bitstreams).
          * Would provide a way for people to more easily get their data out of DSpace (whatever the purpose may be).
          * Would provide a relatively standard format for people to migrate entire hierarchies (Communities/Collections) into DSpace (from another system).

          Known Issues:
          * Exporting/Importing the Community/Collection/Item hierarchy technically doesn't cover all the "content" held in DSpace. There are also Groups, EPeople and permissions/rights (which would get you closer to a full export/import of all DSpace content). However, concentrating on just the hierarchy of Community/Collection/Item seems like a good first step.

          This is related to (and a partial subset of) MIT's AIP Prototype: http://jira.dspace.org/jira/browse/DS-465 However, the AIP prototype currently does not make it very easy to re-import the exported AIPs for Communities or Collections. So, this feature would extend on the AIP prototype's current packagers/crosswalks to allow for an full export and import of an entire DSpace hierarchy, or just a set of Communities, Collections or Items.

          My current plan is to build off of the subset of the AIP prototype (essentially the packagers, crosswalks and related changes) which begins to allow for this roundtripping of Communities and Collections. I'll be adding a new SVN sandbox area for this work (so that others can help out, if it interests them). If anyone has comments, suggestions or feedback on this idea, or would like to be involved in this project, definitely let me know (or add comments to this issue).
          This comes out of a requirement for DSpace integration with DuraCloud (http://www.duraspace.org/duracloud.php). One of these requirements is to be able to essentially "backup" local DSpace contents into the cloud (as a type of offsite backup), and "restore" those contents at a later time.

          Essentially, we'd like a way to be able to export the entire hierarchy (i.e. bitstreams, metadata and relationships between Communities/Collections/Items) into a relatively standard format (e.g. METS or similar structured packaging format). This entire hierarchy should also be able to be re-imported into DSpace in the same format, to allow for "roundtripping" of that content (essentially a restore of that content in the same or different DSpace installation).

          Perceived benefits to DSpace community:
          * Would allow folks to more easily move entire Communities or Collections between DSpace instances.
          * Would allow for a potentially more consistent backup of this hierarchy (e.g. to DuraCloud, or just to your own local backup system), rather than relying on synchronizing a backup of your DB (metadata/relationships) and assetstore (bitstreams).
          * Would provide a way for people to more easily get their data out of DSpace (whatever the purpose may be).
          * Would provide a relatively standard format for people to migrate entire hierarchies (Communities/Collections) into DSpace (from another system).

          Known Issues:
          * Exporting/Importing the Community/Collection/Item hierarchy technically doesn't cover all the "content" held in DSpace. There are also Groups, EPeople and permissions/rights (which would get you closer to a full export/import of all DSpace content). However, concentrating on just the hierarchy of Community/Collection/Item seems like a good first step.

          This is related to (and a partial subset of) MIT's AIP Prototype: http://jira.dspace.org/jira/browse/DS-465 However, the AIP prototype currently does not make it very easy to re-import the exported AIPs for Communities or Collections. So, this feature would extend on the AIP prototype's current packagers/crosswalks to allow for an full export and import of an entire DSpace hierarchy, or just a set of Communities, Collections or Items.

          My current plan is to build off of the subset of the AIP prototype (essentially the packagers, crosswalks and related changes) which begins to allow for this roundtripping of Communities and Collections. I'll be adding a new SVN sandbox area for this work (so that others can help out, if it interests them). If anyone has comments, suggestions or feedback on this idea, or would like to be involved in this project, definitely let me know (or add comments to this issue).

          This work is being prototyped in the SVN Sandbox at:
          http://scm.dspace.org/svn/repo/sandbox/aip-external-1_6-prototype/
          Hide
          Tim Donohue added a comment -
          Added link to wiki page describing project.
          Show
          Tim Donohue added a comment - Added link to wiki page describing project.
          Tim Donohue made changes -
          Description This comes out of a requirement for DSpace integration with DuraCloud (http://www.duraspace.org/duracloud.php). One of these requirements is to be able to essentially "backup" local DSpace contents into the cloud (as a type of offsite backup), and "restore" those contents at a later time.

          Essentially, we'd like a way to be able to export the entire hierarchy (i.e. bitstreams, metadata and relationships between Communities/Collections/Items) into a relatively standard format (e.g. METS or similar structured packaging format). This entire hierarchy should also be able to be re-imported into DSpace in the same format, to allow for "roundtripping" of that content (essentially a restore of that content in the same or different DSpace installation).

          Perceived benefits to DSpace community:
          * Would allow folks to more easily move entire Communities or Collections between DSpace instances.
          * Would allow for a potentially more consistent backup of this hierarchy (e.g. to DuraCloud, or just to your own local backup system), rather than relying on synchronizing a backup of your DB (metadata/relationships) and assetstore (bitstreams).
          * Would provide a way for people to more easily get their data out of DSpace (whatever the purpose may be).
          * Would provide a relatively standard format for people to migrate entire hierarchies (Communities/Collections) into DSpace (from another system).

          Known Issues:
          * Exporting/Importing the Community/Collection/Item hierarchy technically doesn't cover all the "content" held in DSpace. There are also Groups, EPeople and permissions/rights (which would get you closer to a full export/import of all DSpace content). However, concentrating on just the hierarchy of Community/Collection/Item seems like a good first step.

          This is related to (and a partial subset of) MIT's AIP Prototype: http://jira.dspace.org/jira/browse/DS-465 However, the AIP prototype currently does not make it very easy to re-import the exported AIPs for Communities or Collections. So, this feature would extend on the AIP prototype's current packagers/crosswalks to allow for an full export and import of an entire DSpace hierarchy, or just a set of Communities, Collections or Items.

          My current plan is to build off of the subset of the AIP prototype (essentially the packagers, crosswalks and related changes) which begins to allow for this roundtripping of Communities and Collections. I'll be adding a new SVN sandbox area for this work (so that others can help out, if it interests them). If anyone has comments, suggestions or feedback on this idea, or would like to be involved in this project, definitely let me know (or add comments to this issue).

          This work is being prototyped in the SVN Sandbox at:
          http://scm.dspace.org/svn/repo/sandbox/aip-external-1_6-prototype/
          This comes out of a requirement for DSpace integration with DuraCloud (http://www.duraspace.org/duracloud.php). One of these requirements is to be able to essentially "backup" local DSpace contents into the cloud (as a type of offsite backup), and "restore" those contents at a later time.

          Essentially, we'd like a way to be able to export the entire hierarchy (i.e. bitstreams, metadata and relationships between Communities/Collections/Items) into a relatively standard format (e.g. METS or similar structured packaging format). This entire hierarchy should also be able to be re-imported into DSpace in the same format, to allow for "roundtripping" of that content (essentially a restore of that content in the same or different DSpace installation).

          Perceived benefits to DSpace community:
          * Would allow folks to more easily move entire Communities or Collections between DSpace instances.
          * Would allow for a potentially more consistent backup of this hierarchy (e.g. to DuraCloud, or just to your own local backup system), rather than relying on synchronizing a backup of your DB (metadata/relationships) and assetstore (bitstreams).
          * Would provide a way for people to more easily get their data out of DSpace (whatever the purpose may be).
          * Would provide a relatively standard format for people to migrate entire hierarchies (Communities/Collections) into DSpace (from another system).

          Known Issues:
          * Exporting/Importing the Community/Collection/Item hierarchy technically doesn't cover all the "content" held in DSpace. There are also Groups, EPeople and permissions/rights (which would get you closer to a full export/import of all DSpace content). However, concentrating on just the hierarchy of Community/Collection/Item seems like a good first step.

          This is related to (and a partial subset of) MIT's AIP Prototype: http://jira.dspace.org/jira/browse/DS-465 However, the AIP prototype currently does not make it very easy to re-import the exported AIPs for Communities or Collections. So, this feature would extend on the AIP prototype's current packagers/crosswalks to allow for an full export and import of an entire DSpace hierarchy, or just a set of Communities, Collections or Items.

          My current plan is to build off of the subset of the AIP prototype (essentially the packagers, crosswalks and related changes) which begins to allow for this roundtripping of Communities and Collections. I'll be adding a new SVN sandbox area for this work (so that others can help out, if it interests them). If anyone has comments, suggestions or feedback on this idea, or would like to be involved in this project, definitely let me know (or add comments to this issue).

          This work is being prototyped in the SVN Sandbox at:
          http://scm.dspace.org/svn/repo/sandbox/aip-external-1_6-prototype/

          More details on this project available on the Wiki at:
          http://wiki.dspace.org/confluence/display/DSPACE/AipBackupRestorePrototype
          Tim Donohue made changes -
          Workflow jira [ 10777 ] DSpace Workflow [ 11469 ]
          Hide
          Tim Donohue added a comment -
          Added Trunk Patches and descriptions of all changes to a new wiki page:

          https://wiki.duraspace.org/display/DSPACE/AipCoreAPIChanges

          This wiki page details all changes necessary to support this AIP Backup/Restore functionality -- it also includes all patches to existing code (the patches are attached to the wiki page). The majority of the changes include refactoring of the Crosswalks and Packagers to support AIPs (and normal backup/restore tasks). There are other minor changes that were necessary to the core API, as well as SWORD and LNI -- but, hopefull none of those will be controversial.

          I'm now looking for others to begin to review these changes (or checkout the code itself from the Sandbox SVN to review it).
          I think this code is ready to begin to migrate/merge into Trunk in the very near future (assuming others agree).

          More information on running/using this new AIP Backup Restore functionality is available off the wiki page:

          https://wiki.duraspace.org/display/DSPACE/AipBackupRestorePrototype
          Show
          Tim Donohue added a comment - Added Trunk Patches and descriptions of all changes to a new wiki page: https://wiki.duraspace.org/display/DSPACE/AipCoreAPIChanges This wiki page details all changes necessary to support this AIP Backup/Restore functionality -- it also includes all patches to existing code (the patches are attached to the wiki page). The majority of the changes include refactoring of the Crosswalks and Packagers to support AIPs (and normal backup/restore tasks). There are other minor changes that were necessary to the core API, as well as SWORD and LNI -- but, hopefull none of those will be controversial. I'm now looking for others to begin to review these changes (or checkout the code itself from the Sandbox SVN to review it). I think this code is ready to begin to migrate/merge into Trunk in the very near future (assuming others agree). More information on running/using this new AIP Backup Restore functionality is available off the wiki page: https://wiki.duraspace.org/display/DSPACE/AipBackupRestorePrototype
          Tim Donohue
          13/Aug/10 8:10 PM
          View full commit
          Migrating current AIP Backup/Restore code (DS-466) from 'aip-external-1_6-prototype' Branch into Trunk! See https://wiki.duraspace.org/display/DSPACE/AipBackupRestorePrototype for much more details on this work, and how to export/import AIPs. WARNING -- This changes the PackageIngester and PackageDisseminator interfaces. Any of your local, custom Packagers will require refactoring to support the updated interfaces (obviously all DSpace out-of-the-box Packagers have already been refactored). git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5265 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue made changes -
          Link This issue is related to DS-647 [ DS-647 ]
          Tim Donohue
          16/Aug/10 4:12 PM
          View full commit
          Minor comment change to dspace.cfg -- because of SWORD code refactoring in DS-466 SWORD no longer requires the 'upload.temp.dir' setting when 'sword.keep-original-package' is enabled. git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5266 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Hide
          Tim Donohue added a comment -
          Resolving this issue, as primary code is now committed to Trunk (as of rev 5265).

          Documentation on how to use & configure this new feature is available on the Wiki at:
          https://wiki.duraspace.org/display/DSPACE/AipBackupRestore

          However, I still require help on fully testing the LNI refactoring, as detailed in issue DS-647
          Show
          Tim Donohue added a comment - Resolving this issue, as primary code is now committed to Trunk (as of rev 5265). Documentation on how to use & configure this new feature is available on the Wiki at: https://wiki.duraspace.org/display/DSPACE/AipBackupRestore However, I still require help on fully testing the LNI refactoring, as detailed in issue DS-647
          Tim Donohue made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Documentation Status Needed In Comments
          Tim Donohue
          02/Sep/10 7:48 PM
          View full commit
          Enhanced existing Unit Tests, based on DS-466 (AIP work) code changes. Mostly, this ensures that the new create() methods with a specified handle are being tested for each of the main content classes. git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5330 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue made changes -
          Project Import Thu Oct 14 14:40:23 UTC 2010 [ 1287067223065 ]
          Tim Donohue
          26/Oct/10 8:43 PM
          View full commit
          AIP work (DS-466): Resolve a potential instability bug when exporting/restoring groups. We will never export groups which contain internal identifiers (e.g. COLLECTION_<ID>_ADMIN) to an AIP. If those groups' internal identifiers cannot be successfully translated to a Handle (external identifier), then they will not be exported in AIPs. The reason is that if they are ever re-imported they may cause conflicts with an existing group, or overwrite the members of an existing group. (NOTE: the only way in which these groups' internal IDs could not be translated to an external identifier would be if they Community or Collection they referred to was previously deleted from the system -- in which case the group should no longer be in use.) This commit also contains some minor code cleanup. git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5659 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue
          27/Oct/10 7:34 PM
          View full commit
          Minor bug fix to configurations for the new RoleCrosswalk (for AIP work, see DS-466). The RoleCrosswalk plugin was registered in dspace.cfg as both a DisseminationCrosswalk and a StreamDisseminationCrosswalk. It is only a valid DisseminationCrosswalk (not a Stream one), so the second config was removed. git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5672 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue
          28/Oct/10 2:43 PM
          View full commit
          AIP work (DS-466) bug fix. Ensure 'manifest-only' exports are valid METS files by building a non-null URL for Community/Collection logo bitstreams to be referenced. As Manifest-only exports don't include content files, we need to reference them by semi-stable URLs -- in this case, we'll reference logos via the '/retrieve/[id]' path, as that will work for both JSPUI and XMLUI. git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5680 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue
          28/Oct/10 2:46 PM
          View full commit
          AIP work (DS-466) cleanup. Only disseminate non-null values for EPeople into the 'DSPACE-ROLES' xml stream. This just ensures we keep the XML content a little bit smaller in size, and cuts down on empty XML tags. git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5681 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue
          29/Oct/10 4:50 PM
          View full commit
          DS-712 : DSpace Fails to Check if a Handle is already assigned before assigning a new handle The resolution to this problem is not to for DSpace to query all handles when assigning a new one (which can be taxing for large installs). Rather this fix changes the 'update-sequences.sql' scripts (for both Postgres & Oracle) such that the Handle sequence number will always be updated to ensure DSpace will assign a unique handle on the next handle request. I've also documented in the AIP backup/restore docs (DS-466) that update-sequence.sql script should always be run after a full AIP restore (which is the primary scenario where DSpace may encounter handle assignment issues). git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5691 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue
          29/Oct/10 9:18 PM
          View full commit
          Adding a minor option to the AIP Disseminator (DS-466). It now comes with an optional "includeBundles" flag, which can be used to limit which Bundles are exported into an Item's AIP. This option would allow people to choose to, for example, not export the TEXT bundle into AIPs (as its contents could be recreated later on). This option has been documented in the AIP Backup & Restore docs: https://wiki.duraspace.org/display/DSDOC/AipBackupRestore git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5695 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue
          29/Oct/10 10:09 PM
          View full commit
          Adding another minor option to the AIP Disseminator (DS-466). There's now also an 'updatedAfter' flag, which allows for a very basic form of 'incremental backup'. When this flag is used, an ISO-8601 date must be specified. When used, the AIP Disseminator will only export Item AIPs for items that have changed since that date (it will still always export all Community & Collection AIPs, as there's no last-modified date for them). This new option has also been already documented in the AIP Backup & Restore docs at: https://wiki.duraspace.org/display/DSDOC/AipBackupRestore git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5696 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue
          22/Nov/10 4:14 PM
          View full commit
          DS-466 AIP Backup & Restore was unable to backup or restore a Collection's Item Template. This issue was reported via DuraCloud pilot. This code now ensures that Item Template can be backed up and restored properly. Code and generated METS has been validated and tested and seems to be working perfectly. git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5886 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue
          22/Nov/10 4:17 PM
          View full commit
          DS-466 Fixing minor bug in 'item-mapping' logic of AbstractPackageIngester. It was making the improper assumption that ingestAll() will *always* cause a new object to be ingested. However, this is not the case if an object already existed, and the Packager is running in "restore, but keep existing" (-r -k) mode. Fixed the code so that it first verifies if an object was successfully ingested before performing extra item-mapping cleanup work. git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5887 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue
          22/Nov/10 8:10 PM
          View full commit
          DS-466: Fix minor bug in count of packages disseminated. Before adding a package to list of those disseminated, make sure it isn't already listed. This only occurs for mapped item packages, which may be listed multiple places and were accidently being counted multiple times. git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5890 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue
          22/Nov/10 8:13 PM
          View full commit
          DS-466: Similar to last commit, ensure ingested items are not counted multiple times. git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5891 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue
          22/Nov/10 8:31 PM
          View full commit
          DS-466 : Fixed bug where METSManifest was wrongly throwing an error if an Item AIP's METS file didn't include a <fileSec>. METS files which describe an Item may not include a <fileSec> if they contain no files (i.e. DSpace allows Items to exist which have no bundles/bitstreams attached -- this is a rare scenario, but AIP ingester needs to be able to support it). This bug was discovered during DuraCloud pilot testing. git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5892 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue
          22/Nov/10 8:53 PM
          View full commit
          DS-466 : Just realized the code fixed in r5887 appears in two places -- both in ingestAll() and in replaceAll(). It was fixed in ingestAll() in r5887. This commit also ensures it is fixed in replaceAll() method. git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5893 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue
          22/Nov/10 9:53 PM
          View full commit
          DS-466 : Small bug fix. Changed METS disseminator to *always* include a relative file path reference to expected location of child METS files/AIPs. Previously it would only include this path during a recursive dissemination. However, without this file path reference, DSpace currently can *never* restore any child objects (as we don't have a tool to crawl AIPs/METS to find an AIP via just a Handle reference). So, for now, we need to always include a relative file path. Another small issue found via Duracloud testing. git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5894 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue
          24/Nov/10 6:52 PM
          View full commit
          DS-466: Removing duplicative logic in AbstractMETSIngester's replace() method. replace() method used to try to determine the parent DSpaceObject before calling ingestObject() method. However, the ingestObject() method already does this by calling getParentObject(). So, replace() included logic which already exists in getParentObject(). That same logic was being run twice in a row, when it only needs to be run once. This change has been tested and is working properly. git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5906 9c30dcfa-912a-0410-8fc2-9e0234be79fd
          Tim Donohue made changes -
          Link This issue is related to DS-772 [ DS-772 ]
          Tim Donohue made changes -
          Workflow DSpace Workflow [ 15379 ] DSpace JIRA Workflow [ 23405 ]
          Status Resolved [ 5 ] Closed [ 6 ]

            People

            • Assignee:
              Tim Donohue
              Reporter:
              Tim Donohue
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: