Issue with OAI Import in DSpace 7.5: Metadata Not Indexed and Error on XML View
33 views
Skip to first unread message
Vanya Chou
Jul 30, 2024, 7:28:49 AM7/30/24
to DSpace Technical Support
Hello!
DSpace 7.5.
When performing an OAI import, some metadata fails to be processed. The log shows a missing line "....0000 indexed" (as shown in the example below with a black background).
When viewing the XML of that metadata (like 852) on the website, an error message appears: "The given id does not exist."
However, the metadata can be queried normally through the DSpace interface. For some metadata, deleting and re-adding it resolves the issue, but for others, re-adding does not succeed. How can I fix it? Thanks.
DSpace 7.5.
When performing an OAI import, some metadata fails to be processed. The log shows a missing line "....0000 indexed" (as shown in the example below with a black background).
When viewing the XML of that metadata (like 852) on the website, an error message appears: "The given id does not exist."
However, the metadata can be queried normally through the DSpace interface. For some metadata, deleting and re-adding it resolves the issue, but for others, re-adding does not succeed. How can I fix it? Thanks.
Item A with handle 1829 is about to be indexed
Item A with handle 1829 indexed
Item B with handle 852 is about to be indexed
Item C with handle 513 is about to be indexed
Item C with handle 513 indexed
DSpace Technical Support
Aug 5, 2024, 12:12:38 PM8/5/24
to DSpace Technical Support
Hi,
I suspect there's an error occurring behind the scenes which causes the metadata to fail to be imported into the OAI index. This error is likely to be in the "dspace.log" on the backend (since OAI runs from the backend). If you reindex (run "./dspace oai import"), you may find that an error is displaying in your dspace.log that describes *why* these items are not able to be indexed. Without that information, it'd be difficult to debug this issue, as it's unclear to me why some items would be skipped/failing.
I suspect there's an error occurring behind the scenes which causes the metadata to fail to be imported into the OAI index. This error is likely to be in the "dspace.log" on the backend (since OAI runs from the backend). If you reindex (run "./dspace oai import"), you may find that an error is displaying in your dspace.log that describes *why* these items are not able to be indexed. Without that information, it'd be difficult to debug this issue, as it's unclear to me why some items would be skipped/failing.
Tim
Reply all
Reply to author
Forward
0 new messages