Per #31, DSpace 6 changed its ID structure to UUID's, which requires a database change on our side.
However, that change looks like it'd be backward compatible with what DSpace 5 needs (simple ints). If that's the only API change -- id becoming uuid -- then keeping them both as remote_id in the Omeka S table would only need a simple check for which is present in the returned data when I'm parsing it out.
Per #31, DSpace 6 changed its ID structure to UUID's, which requires a database change on our side.
However, that change looks like it'd be backward compatible with what DSpace 5 needs (simple
ints). If that's the only API change --idbecominguuid-- then keeping them both asremote_idin the Omeka S table would only need a simple check for which is present in the returned data when I'm parsing it out.