Hi,

I'm really trying to nail down the repeatable process to migrate and upgrade from v4.1 to v5.2, and while I've drafted a document in Confluence I will need to basically rewrite it due to continued testing and findings.

There is a mystery I can't solve which is that after migrated to v5.2 the Group records don't show their related Object records in the UI.  I can see the relationships exist in the Postgres table relations_common.  I can see the Group records themselves in the UI.  But there are not related Object records showing in the UI for them.  However from the Object records I can see related Group records in the UI.

In v5.2 I can create a new Group record and successfully relate it to a newly created Object record and see this correctly in the UI.

That same new Group record will allow me to create a new relationship record to a migrated Object record but won't subsequently display the Object record.  I confirm the row is added to relations_common in Postgres.  Interestingly the Object record will however show the related Group record !  Further, when trying to relate Group records to Object records there is no available checkbox beside any existing related Object records, so the UI knows that the relationship already exists and can't be added to related Objects.

Any ideas on how I should troubleshoot this?

Thank you,
Willi Wolf

Hi Willi,
What version of the UI is displayed in the footer?

When a relation is created between an object and a group, there should be two rows in relations_common: one where the subject is the collectionobject and the object is the group, and one where the subject is the group, and the object is the collectionobject. But it sounds like only one of the rows exists. Is that right?

Thanks,
Ray

��
Ray Lee
CollectionSpace Senior Developer
LYRASIS
ray.lee@lyrasis.org

From: Talk talk-bounces@lists.collectionspace.org on behalf of William Wolf ww@williwolf.net
Sent: Tuesday, February 11, 2020 12:24 PM
To: talk@lists.collectionspace.org
Subject: [Talk] migrate and upgrade 4.1 to 5.2 Groups

Hi,

I��m really trying to nail down the repeatable process to migrate and upgrade from v4.1 to v5.2, and while I��ve drafted a document in Confluence I will need to basically rewrite it due to continued testing and findings.

There is a mystery I can��t solve which is that after migrated to v5.2 the Group records don��t show their related Object records in the UI.  I can see the relationships exist in the Postgres table relations_common.  I can see the Group records themselves in the UI.  But there are not related Object records showing in the UI for them.  However from the Object records I can see related Group records in the UI.

In v5.2 I can create a new Group record and successfully relate it to a newly created Object record and see this correctly in the UI.

That same new Group record will allow me to create a new relationship record to a migrated Object record but won��t subsequently display the Object record.  I confirm the row is added to relations_common in Postgres.  Interestingly the Object record will however show the related Group record !  Further, when trying to relate Group records to Object records there is no available checkbox beside any existing related Object records, so the UI knows that the relationship already exists and can��t be added to related Objects.

Any ideas on how I should troubleshoot this?

Thank you,
Willi Wolf

Hi Ray,

Release 5.2
UI version 3.0.1
Fine and Contemporary Art profile version 1.0.2

Thank you!
Willi

-----Original Message-----
From: Ray Lee ray.lee@lyrasis.org
Sent: Tuesday, February 18, 2020 0:14
To: William Wolf ww@williwolf.net; talk@lists.collectionspace.org
Subject: Re: migrate and upgrade 4.1 to 5.2 Groups

Hi Willi,
What version of the UI is displayed in the footer?

When a relation is created between an object and a group, there should be two rows in relations_common: one where the subject is the collectionobject and the object is the group, and one where the subject is the group, and the object is the collectionobject. But it sounds like only one of the rows exists. Is that right?

Thanks,
Ray

═
Ray Lee
CollectionSpace Senior Developer
LYRASIS
ray.lee@lyrasis.org

From: Talk talk-bounces@lists.collectionspace.org on behalf of William Wolf ww@williwolf.net
Sent: Tuesday, February 11, 2020 12:24 PM
To: talk@lists.collectionspace.org
Subject: [Talk] migrate and upgrade 4.1 to 5.2 Groups

Hi,

I'm really trying to nail down the repeatable process to migrate and upgrade from v4.1 to v5.2, and while I've drafted a document in Confluence I will need to basically rewrite it due to continued testing and findings.

There is a mystery I can't solve which is that after migrated to v5.2 the Group records don't show their related Object records in the UI.  I can see the relationships exist in the Postgres table relations_common.  I can see the Group records themselves in the UI.  But there are not related Object records showing in the UI for them.  However from the Object records I can see related Group records in the UI.

In v5.2 I can create a new Group record and successfully relate it to a newly created Object record and see this correctly in the UI.

That same new Group record will allow me to create a new relationship record to a migrated Object record but won't subsequently display the Object record.  I confirm the row is added to relations_common in Postgres.  Interestingly the Object record will however show the related Group record !  Further, when trying to relate Group records to Object records there is no available checkbox beside any existing related Object records, so the UI knows that the relationship already exists and can't be added to related Objects.

Any ideas on how I should troubleshoot this?

Thank you,
Willi Wolf

I'll check on the two rows on relations_common and let you know what I see.  Thanks again.

-----Original Message-----
From: Ray Lee ray.lee@lyrasis.org
Sent: Tuesday, February 18, 2020 0:14
To: William Wolf ww@williwolf.net; talk@lists.collectionspace.org
Subject: Re: migrate and upgrade 4.1 to 5.2 Groups

Hi Willi,
What version of the UI is displayed in the footer?

When a relation is created between an object and a group, there should be two rows in relations_common: one where the subject is the collectionobject and the object is the group, and one where the subject is the group, and the object is the collectionobject. But it sounds like only one of the rows exists. Is that right?

Thanks,
Ray

═
Ray Lee
CollectionSpace Senior Developer
LYRASIS
ray.lee@lyrasis.org

From: Talk talk-bounces@lists.collectionspace.org on behalf of William Wolf ww@williwolf.net
Sent: Tuesday, February 11, 2020 12:24 PM
To: talk@lists.collectionspace.org
Subject: [Talk] migrate and upgrade 4.1 to 5.2 Groups

Hi,

I'm really trying to nail down the repeatable process to migrate and upgrade from v4.1 to v5.2, and while I've drafted a document in Confluence I will need to basically rewrite it due to continued testing and findings.

There is a mystery I can't solve which is that after migrated to v5.2 the Group records don't show their related Object records in the UI.  I can see the relationships exist in the Postgres table relations_common.  I can see the Group records themselves in the UI.  But there are not related Object records showing in the UI for them.  However from the Object records I can see related Group records in the UI.

In v5.2 I can create a new Group record and successfully relate it to a newly created Object record and see this correctly in the UI.

That same new Group record will allow me to create a new relationship record to a migrated Object record but won't subsequently display the Object record.  I confirm the row is added to relations_common in Postgres.  Interestingly the Object record will however show the related Group record !  Further, when trying to relate Group records to Object records there is no available checkbox beside any existing related Object records, so the UI knows that the relationship already exists and can't be added to related Objects.

Any ideas on how I should troubleshoot this?

Thank you,
Willi Wolf

Hi,

I've got all the records expected in table relations_common, but I see that all the values for the field 'Active' are missing.  I will add the value 't' in that field and that should fix my problem.

Thank you,
Willi

-----Original Message-----
From: Ray Lee ray.lee@lyrasis.org
Sent: Tuesday, February 18, 2020 0:14
To: William Wolf ww@williwolf.net; talk@lists.collectionspace.org
Subject: Re: migrate and upgrade 4.1 to 5.2 Groups

Hi Willi,
What version of the UI is displayed in the footer?

When a relation is created between an object and a group, there should be two rows in relations_common: one where the subject is the collectionobject and the object is the group, and one where the subject is the group, and the object is the collectionobject. But it sounds like only one of the rows exists. Is that right?

Thanks,
Ray

═
Ray Lee
CollectionSpace Senior Developer
LYRASIS
ray.lee@lyrasis.org

From: Talk talk-bounces@lists.collectionspace.org on behalf of William Wolf ww@williwolf.net
Sent: Tuesday, February 11, 2020 12:24 PM
To: talk@lists.collectionspace.org
Subject: [Talk] migrate and upgrade 4.1 to 5.2 Groups

Hi,

I'm really trying to nail down the repeatable process to migrate and upgrade from v4.1 to v5.2, and while I've drafted a document in Confluence I will need to basically rewrite it due to continued testing and findings.

There is a mystery I can't solve which is that after migrated to v5.2 the Group records don't show their related Object records in the UI.  I can see the relationships exist in the Postgres table relations_common.  I can see the Group records themselves in the UI.  But there are not related Object records showing in the UI for them.  However from the Object records I can see related Group records in the UI.

In v5.2 I can create a new Group record and successfully relate it to a newly created Object record and see this correctly in the UI.

That same new Group record will allow me to create a new relationship record to a migrated Object record but won't subsequently display the Object record.  I confirm the row is added to relations_common in Postgres.  Interestingly the Object record will however show the related Group record !  Further, when trying to relate Group records to Object records there is no available checkbox beside any existing related Object records, so the UI knows that the relationship already exists and can't be added to related Objects.

Any ideas on how I should troubleshoot this?

Thank you,
Willi Wolf

Update:
Adding the value 't' to the Active field in relations_common did nothing ☹
I have done some more experimenting and notice this:

The UI problem is only with the migrated Object records.

New Object record
An Object record newly created in v5.2 can be related to any Group record (migrated or new) and this relationship shows in the browser correctly, both from the Group record and from the Object record perspective.

Migrated Object record
In the Group record perspective the related migrated Object records are not shown. But from the Object record perspective the related Group records are shown. New relationships created between Group and any migrated Object record appear to be saved and exist in Postgres table relations_common, but are not shown in the UI Group record as related Object records. (However the UI does correctly work for the 'Relate existing' Objects feature. It shows checkboxes for unrelated Object records and no checkboxes for related Object records that migrated.)

Any ideas?

Thanks,
Willi

-----Original Message-----
From: William Wolf
Sent: Wednesday, February 19, 2020 14:34
To: Ray Lee ray.lee@lyrasis.org; talk@lists.collectionspace.org
Subject: RE: migrate and upgrade 4.1 to 5.2 Groups

Hi,

I've got all the records expected in table relations_common, but I see that all the values for the field 'Active' are missing.  I will add the value 't' in that field and that should fix my problem.

Thank you,
Willi

-----Original Message-----
From: Ray Lee ray.lee@lyrasis.org
Sent: Tuesday, February 18, 2020 0:14
To: William Wolf ww@williwolf.net; talk@lists.collectionspace.org
Subject: Re: migrate and upgrade 4.1 to 5.2 Groups

Hi Willi,
What version of the UI is displayed in the footer?

When a relation is created between an object and a group, there should be two rows in relations_common: one where the subject is the collectionobject and the object is the group, and one where the subject is the group, and the object is the collectionobject. But it sounds like only one of the rows exists. Is that right?

Thanks,
Ray

═
Ray Lee
CollectionSpace Senior Developer
LYRASIS
ray.lee@lyrasis.org

From: Talk talk-bounces@lists.collectionspace.org on behalf of William Wolf ww@williwolf.net
Sent: Tuesday, February 11, 2020 12:24 PM
To: talk@lists.collectionspace.org
Subject: [Talk] migrate and upgrade 4.1 to 5.2 Groups

Hi,

I’m really trying to nail down the repeatable process to migrate and upgrade from v4.1 to v5.2, and while I’ve drafted a document in Confluence I will need to basically rewrite it due to continued testing and findings.

There is a mystery I can’t solve which is that after migrated to v5.2 the Group records don’t show their related Object records in the UI.  I can see the relationships exist in the Postgres table relations_common.  I can see the Group records themselves in the UI.  But there are not related Object records showing in the UI for them.  However from the Object records I can see related Group records in the UI.

In v5.2 I can create a new Group record and successfully relate it to a newly created Object record and see this correctly in the UI.

That same new Group record will allow me to create a new relationship record to a migrated Object record but won’t subsequently display the Object record.  I confirm the row is added to relations_common in Postgres.  Interestingly the Object record will however show the related Group record !  Further, when trying to relate Group records to Object records there is no available checkbox beside any existing related Object records, so the UI knows that the relationship already exists and can’t be added to related Objects.

Any ideas on how I should troubleshoot this?

Thank you,
Willi Wolf

Hi,

I'm pasting the part of the cspace-services log that seems relevant:

2020-02-24 03:56:11,644 DEBUG [http-nio-8180-exec-9] [org.collectionspace.services.group.GroupResource:480] get for org.collectionspace.services.group.GroupResource with csid=50d11c8e-97d9-4474-82ea
2020-02-24 03:56:12,305 DEBUG [http-nio-8180-exec-5] [org.collectionspace.services.nuxeo.client.java.DocumentModelHandler:552] The CMIS query is: SELECT DOC.nuxeo:pathSegment, DOC.dc:title, REL.dc:title, REL.relations_common:objectCsid, REL.relations_common:subjectCsid FROM Media DOC JOIN Relation REL ON REL.relations_common:objectCsid = DOC.nuxeo:pathSegment WHERE REL.relations_common:subjectCsid = '50d11c8e-97d9-4474-82ea' AND REL.collectionspace_core:tenantId = '10' AND DOC.nuxeo:isVersion = false ORDER BY DOC.media_common:title
2020-02-24 03:56:12,305 DEBUG [http-nio-8180-exec-5] [org.collectionspace.services.nuxeo.client.java.NuxeoRepositoryClientImpl:1564] Executing CMIS query: SELECT DOC.nuxeo:pathSegment, DOC.dc:title, REL.dc:title, REL.relations_common:objectCsid, REL.relations_common:subjectCsid FROM Media DOC JOIN Relation REL ON REL.relations_common:objectCsid = DOC.nuxeo:pathSegment WHERE REL.relations_common:subjectCsid = '50d11c8e-97d9-4474-82ea' AND REL.collectionspace_core:tenantId = '10' AND DOC.nuxeo:isVersion = false ORDER BY DOC.media_common:titlewith pageSize: 2500 at offset: 0
2020-02-24 03:56:12,305 DEBUG [http-nio-8180-exec-5] [org.collectionspace.services.nuxeo.client.java.NuxeoRepositoryClientImpl:1161] Performing a CMIS query on Nuxeo repository named ahn
2020-02-24 03:56:12,360 DEBUG [http-nio-8180-exec-3] [org.collectionspace.services.servicegroup.ServiceGroupResource:480] get for org.collectionspace.services.servicegroup.ServiceGroupResource with csid=procedure
2020-02-24 03:56:12,366 DEBUG [http-nio-8180-exec-2] [org.collectionspace.services.report.ReportResource:120] The WHERE clause is: (ecm:currentLifeCycleState <> 'deleted' AND ecm:currentLifeCycleState <> 'locked_deleted' AND ecm:currentLifeCycleState <> 'replicated_deleted') AND reports_common:forDocTypes = 'Group' AND (reports_common:supportsSingleDoc != 0 OR reports_common:supportsGroup != 0)
2020-02-24 03:56:12,371 DEBUG [http-nio-8180-exec-8] [org.collectionspace.services.batch.BatchResource:111] The WHERE clause is: (ecm:currentLifeCycleState <> 'deleted' AND ecm:currentLifeCycleState <> 'locked_deleted' AND ecm:currentLifeCycleState <> 'replicated_deleted') AND batch_common:forDocTypes = 'Group' AND (batch_common:supportsSingleDoc != 0 OR batch_common:supportsGroup != 0)
2020-02-24 03:56:12,376 DEBUG [http-nio-8180-exec-8] [org.collectionspace.services.nuxeo.client.java.NuxeoRepositoryClientImpl:1230] Executing NXQL query: SELECT * FROM Batch WHERE collectionspace_core:tenantId = '10' AND ((ecm:currentLifeCycleState <> 'deleted' AND ecm:currentLifeCycleState <> 'locked_deleted' AND ecm:currentLifeCycleState <> 'replicated_deleted') AND batch_common:forDocTypes = 'Group' AND (batch_common:supportsSingleDoc != 0 OR batch_common:supportsGroup != 0)) AND ecm:isProxy = 0 AND ecm:isCheckedInVersion = 0 ORDER BY collectionspace_core:updatedAt DESC
2020-02-24 03:56:12,386 DEBUG [http-nio-8180-exec-2] [org.collectionspace.services.nuxeo.client.java.NuxeoRepositoryClientImpl:1230] Executing NXQL query: SELECT * FROM Report WHERE collectionspace_core:tenantId = '10' AND ((ecm:currentLifeCycleState <> 'deleted' AND ecm:currentLifeCycleState <> 'locked_deleted' AND ecm:currentLifeCycleState <> 'replicated_deleted') AND reports_common:forDocTypes = 'Group' AND (reports_common:supportsSingleDoc != 0 OR reports_common:supportsGroup != 0)) AND ecm:isProxy = 0 AND ecm:isCheckedInVersion = 0 ORDER BY collectionspace_core:updatedAt DESC
2020-02-24 03:56:12,394 DEBUG [http-nio-8180-exec-6] [org.collectionspace.services.nuxeo.client.java.DocumentModelHandler:552] The CMIS query is: SELECT DOC.nuxeo:pathSegment, DOC.dc:title, REL.dc:title, REL.relations_common:objectCsid, REL.relations_common:subjectCsid FROM CollectionObjectTenant10 DOC JOIN Relation REL ON REL.relations_common:objectCsid = DOC.nuxeo:pathSegment WHERE REL.relations_common:subjectCsid = '50d11c8e-97d9-4474-82ea' AND REL.relations_common:relationshipType = 'affects' AND REL.collectionspace_core:tenantId = '10' AND DOC.nuxeo:isVersion = false ORDER BY DOC.collectionspace_core:updatedAt DESC
2020-02-24 03:56:12,408 DEBUG [http-nio-8180-exec-6] [org.collectionspace.services.nuxeo.client.java.NuxeoRepositoryClientImpl:1564] Executing CMIS query: SELECT DOC.nuxeo:pathSegment, DOC.dc:title, REL.dc:title, REL.relations_common:objectCsid, REL.relations_common:subjectCsid FROM CollectionObjectTenant10 DOC JOIN Relation REL ON REL.relations_common:objectCsid = DOC.nuxeo:pathSegment WHERE REL.relations_common:subjectCsid = '50d11c8e-97d9-4474-82ea' AND REL.relations_common:relationshipType = 'affects' AND REL.collectionspace_core:tenantId = '10' AND DOC.nuxeo:isVersion = false ORDER BY DOC.collectionspace_core:updatedAt DESCwith pageSize: 5 at offset: 0
2020-02-24 03:56:12,408 DEBUG [http-nio-8180-exec-6] [org.collectionspace.services.nuxeo.client.java.NuxeoRepositoryClientImpl:1161] Performing a CMIS query on Nuxeo repository named ahn
2020-02-24 03:56:12,456 DEBUG [http-nio-8180-exec-3] [org.collectionspace.services.nuxeo.client.java.DocumentModelHandler:552] The CMIS query is: SELECT DOC.nuxeo:pathSegment, DOC.dc:title, REL.dc:title, REL.relations_common:objectCsid, REL.relations_common:subjectCsid FROM CollectionSpaceDocument DOC JOIN Relation REL ON REL.relations_common:objectCsid = DOC.nuxeo:pathSegment WHERE REL.relations_common:subjectCsid = '50d11c8e-97d9-4474-82ea' AND (REL.relations_common:objectDocumentType IN ('Loanin','Uoc','Group','Conditioncheck','Conservation','Valuationcontrol','ObjectExit','Loanout','Media','Acquisition','Intake','Exhibition','Movement')) AND REL.relations_common:relationshipType = 'affects' AND REL.collectionspace_core:tenantId = '10' AND DOC.nuxeo:isVersion = false ORDER BY DOC.collectionspace_core:updatedAt DESC
2020-02-24 03:56:12,460 DEBUG [http-nio-8180-exec-3] [org.collectionspace.services.nuxeo.client.java.NuxeoRepositoryClientImpl:1564] Executing CMIS query: SELECT DOC.nuxeo:pathSegment, DOC.dc:title, REL.dc:title, REL.relations_common:objectCsid, REL.relations_common:subjectCsid FROM CollectionSpaceDocument DOC JOIN Relation REL ON REL.relations_common:objectCsid = DOC.nuxeo:pathSegment WHERE REL.relations_common:subjectCsid = '50d11c8e-97d9-4474-82ea' AND (REL.relations_common:objectDocumentType IN ('Loanin','Uoc','Group','Conditioncheck','Conservation','Valuationcontrol','ObjectExit','Loanout','Media','Acquisition','Intake','Exhibition','Movement')) AND REL.relations_common:relationshipType = 'affects' AND REL.collectionspace_core:tenantId = '10' AND DOC.nuxeo:isVersion = false ORDER BY DOC.collectionspace_core:updatedAt DESCwith pageSize: 5 at offset: 0
2020-02-24 03:56:12,460 DEBUG [http-nio-8180-exec-3] [org.collectionspace.services.nuxeo.client.java.NuxeoRepositoryClientImpl:1161] Performing a CMIS query on Nuxeo repository named ahn

-----Original Message-----
From: William Wolf
Sent: Saturday, February 22, 2020 7:00
To: 'Ray Lee' ray.lee@lyrasis.org; 'talk@lists.collectionspace.org' talk@lists.collectionspace.org
Subject: RE: migrate and upgrade 4.1 to 5.2 Groups

Update:
Adding the value 't' to the Active field in relations_common did nothing ☹ I have done some more experimenting and notice this:

The UI problem is only with the migrated Object records.

New Object record
An Object record newly created in v5.2 can be related to any Group record (migrated or new) and this relationship shows in the browser correctly, both from the Group record and from the Object record perspective.

Migrated Object record
In the Group record perspective the related migrated Object records are not shown. But from the Object record perspective the related Group records are shown. New relationships created between Group and any migrated Object record appear to be saved and exist in Postgres table relations_common, but are not shown in the UI Group record as related Object records. (However the UI does correctly work for the 'Relate existing' Objects feature. It shows checkboxes for unrelated Object records and no checkboxes for related Object records that migrated.)

Any ideas?

Thanks,
Willi

-----Original Message-----
From: William Wolf
Sent: Wednesday, February 19, 2020 14:34
To: Ray Lee ray.lee@lyrasis.org; talk@lists.collectionspace.org
Subject: RE: migrate and upgrade 4.1 to 5.2 Groups

Hi,

I've got all the records expected in table relations_common, but I see that all the values for the field 'Active' are missing.  I will add the value 't' in that field and that should fix my problem.

Thank you,
Willi

-----Original Message-----
From: Ray Lee ray.lee@lyrasis.org
Sent: Tuesday, February 18, 2020 0:14
To: William Wolf ww@williwolf.net; talk@lists.collectionspace.org
Subject: Re: migrate and upgrade 4.1 to 5.2 Groups

Hi Willi,
What version of the UI is displayed in the footer?

When a relation is created between an object and a group, there should be two rows in relations_common: one where the subject is the collectionobject and the object is the group, and one where the subject is the group, and the object is the collectionobject. But it sounds like only one of the rows exists. Is that right?

Thanks,
Ray

═
Ray Lee
CollectionSpace Senior Developer
LYRASIS
ray.lee@lyrasis.org

From: Talk talk-bounces@lists.collectionspace.org on behalf of William Wolf ww@williwolf.net
Sent: Tuesday, February 11, 2020 12:24 PM
To: talk@lists.collectionspace.org
Subject: [Talk] migrate and upgrade 4.1 to 5.2 Groups

Hi,

I’m really trying to nail down the repeatable process to migrate and upgrade from v4.1 to v5.2, and while I’ve drafted a document in Confluence I will need to basically rewrite it due to continued testing and findings.

There is a mystery I can’t solve which is that after migrated to v5.2 the Group records don’t show their related Object records in the UI.  I can see the relationships exist in the Postgres table relations_common.  I can see the Group records themselves in the UI.  But there are not related Object records showing in the UI for them.  However from the Object records I can see related Group records in the UI.

In v5.2 I can create a new Group record and successfully relate it to a newly created Object record and see this correctly in the UI.

That same new Group record will allow me to create a new relationship record to a migrated Object record but won’t subsequently display the Object record.  I confirm the row is added to relations_common in Postgres.  Interestingly the Object record will however show the related Group record !  Further, when trying to relate Group records to Object records there is no available checkbox beside any existing related Object records, so the UI knows that the relationship already exists and can’t be added to related Objects.

Any ideas on how I should troubleshoot this?

Thank you,
Willi Wolf

Here are the two records in relations_common.  The first of the two was migrated and fails to show as a related object to the group.  The second of the two was created in v5.2 and does show as a related object to the group.

select * from relations_common where subjectcsid = '50d11c8e-97d9-4474-82ea';

              id                  |       subjectcsid       | relationshiptype | subjectdocumenttype |           subjecturi            |                                       objectrefname                                        | relationshipmetatype | predicatedisplayname | predicate |                          subjectrefname                          |       objectcsid        |                 objecturi                  | objectdocumenttype | active

--------------------------------------+-------------------------+------------------+---------------------+---------------------------------+--------------------------------------------------------------------------------------------+----------------------+----------------------+-----------+------------------------------------------------------------------+-------------------------+--------------------------------------------+--------------------+--------
b0b26888-2a9f-4d85-ac7e-9cf2d279dc37 | 50d11c8e-97d9-4474-82ea | affects          | Group              | /groups/50d11c8e-97d9-4474-82ea | urn:cspace:alexandernowik.org:collectionobjects:id(6821b517-4b13-4401-879b)'AHN.2016.A030' |                      |                      |          | urn:cspace:alexandernowik.org:groups:id(50d11c8e-97d9-4474-82ea) | 6821b517-4b13-4401-879b | /collectionobjects/6821b517-4b13-4401-879b | CollectionObject  | t
1c4e1468-bb14-4f16-b804-a30d967500ef | 50d11c8e-97d9-4474-82ea | affects          | Group              | /groups/50d11c8e-97d9-4474-82ea | urn:cspace:alexandernowik.org:collectionobjects:id(9fda3ca2-1404-4f38-b28f)'AHN.2020.TEST' |                      |                      |          | urn:cspace:alexandernowik.org:groups:id(50d11c8e-97d9-4474-82ea) | 9fda3ca2-1404-4f38-b28f | /collectionobjects/9fda3ca2-1404-4f38-b28f | CollectionObject  | t
(2 rows)

This is the the log when the Group record is selected in the UI:

2020-02-24 03:56:12,394 DEBUG [http-nio-8180-exec-6] [org.collectionspace.services.nuxeo.client.java.DocumentModelHandler:552] The CMIS query is: SELECT DOC.nuxeo:pathSegment, DOC.dc:title, REL.dc:title, REL.relations_common:objectCsid, REL.relations_common:subjectCsid FROM CollectionObjectTenant10 DOC JOIN Relation REL ON REL.relations_common:objectCsid = DOC.nuxeo:pathSegment WHERE REL.relations_common:subjectCsid = '50d11c8e-97d9-4474-82ea' AND REL.relations_common:relationshipType = 'affects' AND REL.collectionspace_core:tenantId = '10' AND DOC.nuxeo:isVersion = false ORDER BY DOC.collectionspace_core:updatedAt DESC
2020-02-24 03:56:12,408 DEBUG [http-nio-8180-exec-6] [org.collectionspace.services.nuxeo.client.java.NuxeoRepositoryClientImpl:1564] Executing CMIS query: SELECT DOC.nuxeo:pathSegment, DOC.dc:title, REL.dc:title, REL.relations_common:objectCsid, REL.relations_common:subjectCsid FROM CollectionObjectTenant10 DOC JOIN Relation REL ON REL.relations_common:objectCsid = DOC.nuxeo:pathSegment WHERE REL.relations_common:subjectCsid = '50d11c8e-97d9-4474-82ea' AND REL.relations_common:relationshipType = 'affects' AND REL.collectionspace_core:tenantId = '10' AND DOC.nuxeo:isVersion = false ORDER BY DOC.collectionspace_core:updatedAt DESCwith pageSize: 5 at offset: 0
2020-02-24 03:56:12,408 DEBUG [http-nio-8180-exec-6] [org.collectionspace.services.nuxeo.client.java.NuxeoRepositoryClientImpl:1161] Performing a CMIS query on Nuxeo repository named ahn
2020-02-24 03:56:12,456 DEBUG [http-nio-8180-exec-3] [org.collectionspace.services.nuxeo.client.java.DocumentModelHandler:552] The CMIS query is: SELECT DOC.nuxeo:pathSegment, DOC.dc:title, REL.dc:title, REL.relations_common:objectCsid, REL.relations_common:subjectCsid FROM CollectionSpaceDocument DOC JOIN Relation REL ON REL.relations_common:objectCsid = DOC.nuxeo:pathSegment WHERE REL.relations_common:subjectCsid = '50d11c8e-97d9-4474-82ea' AND (REL.relations_common:objectDocumentType IN ('Loanin','Uoc','Group','Conditioncheck','Conservation','Valuationcontrol','ObjectExit','Loanout','Media','Acquisition','Intake','Exhibition','Movement')) AND REL.relations_common:relationshipType = 'affects' AND REL.collectionspace_core:tenantId = '10' AND DOC.nuxeo:isVersion = false ORDER BY DOC.collectionspace_core:updatedAt DESC
2020-02-24 03:56:12,460 DEBUG [http-nio-8180-exec-3] [org.collectionspace.services.nuxeo.client.java.NuxeoRepositoryClientImpl:1564] Executing CMIS query: SELECT DOC.nuxeo:pathSegment, DOC.dc:title, REL.dc:title, REL.relations_common:objectCsid, REL.relations_common:subjectCsid FROM CollectionSpaceDocument DOC JOIN Relation REL ON REL.relations_common:objectCsid = DOC.nuxeo:pathSegment WHERE REL.relations_common:subjectCsid = '50d11c8e-97d9-4474-82ea' AND (REL.relations_common:objectDocumentType IN ('Loanin','Uoc','Group','Conditioncheck','Conservation','Valuationcontrol','ObjectExit','Loanout','Media','Acquisition','Intake','Exhibition','Movement')) AND REL.relations_common:relationshipType = 'affects' AND REL.collectionspace_core:tenantId = '10' AND DOC.nuxeo:isVersion = false ORDER BY DOC.collectionspace_core:updatedAt DESCwith pageSize: 5 at offset: 0

Hi Willi,
You said you tried setting the active column to true in relations_common. Did you restart cspace after that? If not, try that first.

What does this request to the REST API show?
/cspace-services/collectionobjects?rtSbj=50d11c8e-97d9-4474-82ea&rtPredicate=affects

Ray

═
Ray Lee
CollectionSpace Senior Developer
LYRASIS
ray.lee@lyrasis.org

From: William Wolf ww@williwolf.net
Sent: Saturday, February 22, 2020 6:59 AM
To: Ray Lee; talk@lists.collectionspace.org
Subject: RE: migrate and upgrade 4.1 to 5.2 Groups

Update:
Adding the value 't' to the Active field in relations_common did nothing ☹
I have done some more experimenting and notice this:

The UI problem is only with the migrated Object records.

New Object record
An Object record newly created in v5.2 can be related to any Group record (migrated or new) and this relationship shows in the browser correctly, both from the Group record and from the Object record perspective.

Migrated Object record
In the Group record perspective the related migrated Object records are not shown. But from the Object record perspective the related Group records are shown. New relationships created between Group and any migrated Object record appear to be saved and exist in Postgres table relations_common, but are not shown in the UI Group record as related Object records. (However the UI does correctly work for the 'Relate existing' Objects feature. It shows checkboxes for unrelated Object records and no checkboxes for related Object records that migrated.)

Any ideas?

Thanks,
Willi

-----Original Message-----
From: William Wolf
Sent: Wednesday, February 19, 2020 14:34
To: Ray Lee ray.lee@lyrasis.org; talk@lists.collectionspace.org
Subject: RE: migrate and upgrade 4.1 to 5.2 Groups

Hi,

I've got all the records expected in table relations_common, but I see that all the values for the field 'Active' are missing.  I will add the value 't' in that field and that should fix my problem.

Thank you,
Willi

-----Original Message-----
From: Ray Lee ray.lee@lyrasis.org
Sent: Tuesday, February 18, 2020 0:14
To: William Wolf ww@williwolf.net; talk@lists.collectionspace.org
Subject: Re: migrate and upgrade 4.1 to 5.2 Groups

Hi Willi,
What version of the UI is displayed in the footer?

When a relation is created between an object and a group, there should be two rows in relations_common: one where the subject is the collectionobject and the object is the group, and one where the subject is the group, and the object is the collectionobject. But it sounds like only one of the rows exists. Is that right?

Thanks,
Ray

═
Ray Lee
CollectionSpace Senior Developer
LYRASIS
ray.lee@lyrasis.org

From: Talk talk-bounces@lists.collectionspace.org on behalf of William Wolf ww@williwolf.net
Sent: Tuesday, February 11, 2020 12:24 PM
To: talk@lists.collectionspace.org
Subject: [Talk] migrate and upgrade 4.1 to 5.2 Groups

Hi,

I’m really trying to nail down the repeatable process to migrate and upgrade from v4.1 to v5.2, and while I’ve drafted a document in Confluence I will need to basically rewrite it due to continued testing and findings.

There is a mystery I can’t solve which is that after migrated to v5.2 the Group records don’t show their related Object records in the UI.  I can see the relationships exist in the Postgres table relations_common.  I can see the Group records themselves in the UI.  But there are not related Object records showing in the UI for them.  However from the Object records I can see related Group records in the UI.

In v5.2 I can create a new Group record and successfully relate it to a newly created Object record and see this correctly in the UI.

That same new Group record will allow me to create a new relationship record to a migrated Object record but won’t subsequently display the Object record.  I confirm the row is added to relations_common in Postgres.  Interestingly the Object record will however show the related Group record !  Further, when trying to relate Group records to Object records there is no available checkbox beside any existing related Object records, so the UI knows that the relationship already exists and can’t be added to related Objects.

Any ideas on how I should troubleshoot this?

Thank you,
Willi Wolf