DSpace 9.3 metadata-export returns fewer items than DSpace 7.6 for same data

[Martin So]

Hello,

I would like to ask for help about metadata-export in DSpace 9.3.

We have:

• Production: DSpace 7.6
• Development: DSpace 9.3

The development database was restored from production, so both environments should have the same data.

We run the same command in both environments:

bash

./dspace metadata-export -i d89fd0fe-7d8a-4850-85c5-c36687b25e1c -a -f /tmp/community-export.csv

Results:

• In DSpace 7.6, the export file is about 600 KB
• In DSpace 9.3, the export file is about 330 KB

We also tested export by collection instead of community.
This community has only one collection, and the collection export in 9.3 is still much smaller than in 7.6.

What we have checked:

• The dev database was copied from prod
• The same community / collection UUID is used
• The item count shown in the web UI is the same in both environments
• Some items that appear in the 7.6 export are missing from the 9.3 export
• But those missing items can still be found in the DSpace 9.3 web UI by UUID

So it seems the items exist and are visible in 9.3, but they are just not included in metadata-export.

I would like to ask:

1. Is there any known change in metadata-export behavior between DSpace 7.6 and 9.3?
2. Does metadata-export in 9.3 filter items differently, for example by archived / withdrawn / discoverable status?
3. Is this a known bug, or is there any additional argument/configuration needed in 9.3?

Any advice would be appreciated. Thank you.

Regards,
Martin

Librarian

HKUST

[Michael Plate]

Hi,

Am 17.07.26 um 11:37 schrieb Martin So:

> Hello,
>
> I would like to ask for help about metadata-export in DSpace 9.3.

[…]

presumably the setting

bulkedit.export.max.items

in dspace.cfg is your friend.
By default it is 500 items.

https://wiki.lyrasis.org/spaces/DSDOC9x/pages/379125980/Batch+Metadata+Editing+Configuration

Michael