Move collection to a different community in DSpace 7.6
54 views
Skip to first unread message
Rebecca Odea
Dec 4, 2025, 6:01:44 PMDec 4
to DSpace Community
Has anyone managed to move a collection into a different community using any of these approaches?
- Command line tools (like community‑filiator — though it looks like that only works for communities).
- REST API
- Direct SQL (I know this is risky and could affect integrity/permissions).
- Export/Import
Would love to hear what’s worked for you!
- Command line tools (like community‑filiator — though it looks like that only works for communities).
- REST API
- Direct SQL (I know this is risky and could affect integrity/permissions).
- Export/Import
Would love to hear what’s worked for you!
Cheers, Rebecca
Jorge Gustavo Spertino
Dec 5, 2025, 8:29:54 AMDec 5
to Rebecca Odea, DSpace Community
Hi,
What I've done in a similar situation is:
1- Create the new destination collection in the corresponding community.
2- Export the metadata of the items from the source collection that I want to move.
3- (This isn't necessary, but I'm very conservative about it.) I delete all columns from that CSV file except for the ID and collection columns.
4- I use one or two of those items as a test, and delete the rest of the rows.
5- In those test rows (records), I change the collection number to the new collection in the corresponding column.
6- If I'm satisfied with the result, I continue with the remaining items.
7- I delete the original collection, which should now be empty.
This is just one method I'm sharing with you. I'm not sure it's the best, but it's what I've used. I hope it helps.
Best regards,
Jorge
What I've done in a similar situation is:
1- Create the new destination collection in the corresponding community.
2- Export the metadata of the items from the source collection that I want to move.
3- (This isn't necessary, but I'm very conservative about it.) I delete all columns from that CSV file except for the ID and collection columns.
4- I use one or two of those items as a test, and delete the rest of the rows.
5- In those test rows (records), I change the collection number to the new collection in the corresponding column.
6- If I'm satisfied with the result, I continue with the remaining items.
7- I delete the original collection, which should now be empty.
This is just one method I'm sharing with you. I'm not sure it's the best, but it's what I've used. I hope it helps.
Best regards,
Jorge
--
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups "DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-communi...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dspace-community/22eea3d6-48f0-4e85-bead-d191bc173004n%40googlegroups.com.
Jorge Gustavo Spertino
Dec 7, 2025, 9:28:30 AMDec 7
to Rebecca Odea, DSpace Community
*I forgot to mention the step of importing the modified CSV file before point 6.
Sorry,
Jorge
Reed, Marianne A.
Dec 7, 2025, 10:32:37 AMDec 7
to Jorge Gustavo Spertino, Rebecca Odea, DSpace Community
I've done the same, Jorge, and it works great. Deleting all of the other columns, including the headers, is wise! The metadata in the items moves wigh the item.
To view this discussion visit
https://groups.google.com/d/msgid/dspace-community/CALWxbnh7eT6oD8aGFBLco-PEEXw0E7pmbfzcPjt12QKKjff%2BJg%40mail.gmail.com.
Jorge Gustavo Spertino
Dec 7, 2025, 10:42:22 AMDec 7
to Reed, Marianne A., Rebecca Odea, DSpace Community
excellent, :-)
Rebecca Odea
Dec 17, 2025, 9:14:57 PM (11 days ago) Dec 17
to Jorge Gustavo Spertino, Reed, Marianne A., DSpace Community
Thanks so much Jorge and the team. Cheers, Rebecca
Reply all
Reply to author
Forward
0 new messages