Thanks for the explanation Tim. Everything makes sense to me now. Sorry for
the late reply.
On Friday, March 29, 2024 at 8:17:26 AM UTC+11 DSpace Technical Support
wrote:
Answered briefly inline below:
1.
1. In dspace 7.6.1, each item has an identifier called UUID and in the
database, item table we have the item_id column which is id of the items
from the dspace 5 or older. This is referred as legacy_id in dspace7
backend rest code.Is my understanding correct?
1.
- This change occurred in DSpace 6. As of DSpace 6, all objects have
UUIDs instead of "id" columns. Your understanding is correct.
2.
1. So, when an item is created in dspace 7.6.1, the 'item_id' column in
item table in the database will remain null. Is my understanding correct?
1.
- Yes, again as of DSpace 6 all objects have UUIDs. The old
"item_id" column should be empty for new items (old ones may still have
values). Eventually this column should be dropped.
2.
1. In dspace 7.6.1, we are currently using dspace REST API v6
(deprecated) to integrate an application with Dspace. So, the rest call
"POST /items/find-by-metadata-field " response doesn't have the name-value
pair "id":"Integer id" any more as in Dspace 5 instead we have uuid.
1.
- I believe this is correct but am not well versed in the older REST
API (v6). Essentially though, as of DSpace 6 all objects are identified
by
UUID instead of "id" fields
2.
1. Even though REST API v6 (deprecated)is used, will the "GET
/rest/status" returns <apiVersion> to be "7".
1.
- Yes, this is correct because the system itself is running version
7.
Please also keep in mind that the REST API v6 will be removed in DSpace 8.
You should work to migrate to the new REST API at some point.
Tim
On Tuesday, March 12, 2024 at 7:15:21 AM UTC-5 tsak...@gmail.com wrote:
Hi team,
We are in the process of upgrading dspace from version 5 to 7.6.1.
I have a few queries as listed below.
1. In dspace 7.6.1, each item has an identifier called UUID and in the
database, item table we have the item_id column which is id of the items
from the dspace 5 or older. This is referred as legacy_id in dspace7
backend rest code.
Is my understanding correct?
2. So, when an item is created in dspace 7.6.1, the 'item_id' column in
item table in the database will remain null. Is my understanding correct?
3. In dspace 7.6.1, we are currently using dspace REST API v6 (deprecated)
to integrate an application with Dspace. So, the rest call "POST
/items/find-by-metadata-field " response doesn't have the name-value pair
"id":"Integer id" any more as in Dspace 5 instead we have uuid.
Is my understanding correct?
4. Even though REST API v6 (deprecated)is used, will the "GET /rest/status"
returns <apiVersion> to be "7".
Is my understanding correct?
Can anyone please help me with my understanding which will be very helpful?
Thanks and Regards,
Akshay Karthik Thana Sekar
--
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 Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/f74561f6-dba0-48b2-84c8-965b45a9fcc0n%40googlegroups.com.
