Thanks. Bill Tanzen also pointed out the resouce_type_id to me off list.
I've been working quite a bit with the 3.1 database lately and didn't
take in that part of the change in table structure.
Chris
On 15-04-03 07:19 AM, helix84 wrote:
> Hi Chris,
>
> I'm not sure I understand your problem.
Hi Chris,
I'm not sure I understand your problem. Since DSpace 5, you are
guaranteed unique rows in the metadatavalue table using the composite
key (resource_id, resource_type_id) where resource_type_id is one of
the constants:
https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-api/src/main/j
In our instance of 5.1, resource IDs are being reused when new groups
are created. We've created new groups that have reused the ID numbers
of already existing communities. The newly created groups do not appear
in the list of all groups.
The problem is that an ID for a group is guaranteed un
3 matches
Mail list logo
