talk@lists.collectionspace.org

WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org

View all threads

collection-object application configuration changing the Create New form?

CN
Chad Nelson
Tue, Mar 3, 2015 4:05 PM

Hi All,

I've added some very basic local configuration to the collection-object/cataloging procedure to add a few fields.

https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2
[https://avatars0.githubusercontent.com/u/10663125?v=3&s=400]https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2

First pass at cataloging procedure · 7dc10bc · CollectionSpace-Deployments/application · GitHub
This is a repository that contains Collection Space application layer code.
Read more...https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2

https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c
[https://avatars0.githubusercontent.com/u/10663125?v=3&s=400]https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c

First pass at adding cataloging · 5197c7d · CollectionSpace-Deployments/ui · GitHub
ui - This is a repository that contains Collection Space user interface layer code.
Read more...https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c

And If I go directly to the cataloging page, I see my changes working es expected, shown at the bottom here:
[cid:0f85e2cf-0530-4dfd-b311-ab6702b4b6ba]

But what totally confused me is that the Create New Records form has changed, losing the section specifically for Cataloging Records, and instead adding cataloging to the list of Procedural records, as well as swapping columns. Compare the updated form [cid:7a7627bd-6705-46f0-83ec-1b4f326bd73c] ?

with  the standard (4.1) form:
[cid:097ad377-7e67-4c58-a71a-a0fb94f383d3]

Anyone seen behavior like this before? I've isolated it to being related to making changes in the Application layer (i.e. if I only make those changes, the problem appears), but I'm wondering if it a function of the way the UI handles configuration? Any pointers on debugging the UI would be greatly appreciated.

Thanks

Chad

Hi All, I've added some very basic local configuration to the collection-object/cataloging procedure to add a few fields. https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2 [https://avatars0.githubusercontent.com/u/10663125?v=3&s=400]<https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2> First pass at cataloging procedure · 7dc10bc · CollectionSpace-Deployments/application · GitHub This is a repository that contains Collection Space application layer code. Read more...<https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2> https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c [https://avatars0.githubusercontent.com/u/10663125?v=3&s=400]<https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c> First pass at adding cataloging · 5197c7d · CollectionSpace-Deployments/ui · GitHub ui - This is a repository that contains Collection Space user interface layer code. Read more...<https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c> And If I go directly to the cataloging page, I see my changes working es expected, shown at the bottom here: [cid:0f85e2cf-0530-4dfd-b311-ab6702b4b6ba] But what totally confused me is that the Create New Records form has changed, losing the section specifically for Cataloging Records, and instead adding cataloging to the list of Procedural records, as well as swapping columns. Compare the updated form [cid:7a7627bd-6705-46f0-83ec-1b4f326bd73c] ? with the standard (4.1) form: [cid:097ad377-7e67-4c58-a71a-a0fb94f383d3] Anyone seen behavior like this before? I've isolated it to being related to making changes in the Application layer (i.e. if I only make those changes, the problem appears), but I'm wondering if it a function of the way the UI handles configuration? Any pointers on debugging the UI would be greatly appreciated. Thanks Chad
RL
Ray Lee
Tue, Mar 3, 2015 8:41 PM

Hi Chad,
In mmi-collectionobject.xml you have:

<record id="collection-object" is-extension="true" type="record,procedure">

This overlays base-collectionobject.xml, which has:

<record id="collection-object" in-findedit="yes" cms-type="default" generate-services-schema="true">

So in the merged record, you end up with type="record,procedure" added to
the <record>. You don't wan't that, because it tells the app layer that
collectionobjects are procedures. So it moves into the Procedural Records
section in the UI, and the Cataloging Records section disappears, because
now there are no cataloging records. I'm guessing other things will go
wrong as well.

The HTML for the Create New page is goofy, so when the Cataloging Records
column disappears, things reflow in an unexpected way. I've also seen weird
things happen when the heights of the columns change as you add and remove
record types.

Ray

On Tue, Mar 3, 2015 at 8:05 AM, Chad Nelson chad.nelson@lyrasis.org wrote:

Hi All,

I've added some very basic local configuration to the
collection-object/cataloging procedure to add a few fields.

https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2

https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2
First pass at cataloging procedure · 7dc10bc ·
CollectionSpace-Deployments/application · GitHub
This is a repository that contains Collection Space application layer
code.
Read more...
https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2

https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c

https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c
First pass at adding cataloging · 5197c7d ·
CollectionSpace-Deployments/ui · GitHub
ui - This is a repository that contains Collection Space user interface
layer code.
Read more...
https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c
And If I go directly to the cataloging page, I see my changes working
es expected, shown at the bottom here:

But what totally confused me is that the Create New Records form has
changed, losing the section specifically for Cataloging Records, and
instead adding cataloging to the list of Procedural records, as well as
swapping columns. Compare the updated form ​

with  the standard (4.1) form:

Anyone seen behavior like this before? I've isolated it to being related
to making changes in the Application layer (i.e. if I only make those
changes, the problem appears), but I'm wondering if it a function of the
way the UI handles configuration? Any pointers on debugging the UI would be
greatly appreciated.

Thanks

Chad


Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Hi Chad, In mmi-collectionobject.xml you have: <record id="collection-object" is-extension="true" type="record,procedure"> This overlays base-collectionobject.xml, which has: <record id="collection-object" in-findedit="yes" cms-type="default" generate-services-schema="true"> So in the merged record, you end up with type="record,procedure" added to the <record>. You don't wan't that, because it tells the app layer that collectionobjects are procedures. So it moves into the Procedural Records section in the UI, and the Cataloging Records section disappears, because now there are no cataloging records. I'm guessing other things will go wrong as well. The HTML for the Create New page is goofy, so when the Cataloging Records column disappears, things reflow in an unexpected way. I've also seen weird things happen when the heights of the columns change as you add and remove record types. Ray On Tue, Mar 3, 2015 at 8:05 AM, Chad Nelson <chad.nelson@lyrasis.org> wrote: > Hi All, > > > I've added some very basic local configuration to the > collection-object/cataloging procedure to add a few fields. > > > > https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2 > > <https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2> > First pass at cataloging procedure · 7dc10bc · > CollectionSpace-Deployments/application · GitHub > This is a repository that contains Collection Space application layer > code. > Read more... > <https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2> > > > https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c > > <https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c> > First pass at adding cataloging · 5197c7d · > CollectionSpace-Deployments/ui · GitHub > ui - This is a repository that contains Collection Space user interface > layer code. > Read more... > <https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c> > And If I go directly to the cataloging page, I see my changes working > es expected, shown at the bottom here: > > But what totally confused me is that the Create New Records form has > changed, losing the section specifically for Cataloging Records, and > instead adding cataloging to the list of Procedural records, as well as > swapping columns. Compare the updated form ​ > > with the standard (4.1) form: > > Anyone seen behavior like this before? I've isolated it to being related > to making changes in the Application layer (i.e. if I only make those > changes, the problem appears), but I'm wondering if it a function of the > way the UI handles configuration? Any pointers on debugging the UI would be > greatly appreciated. > > > Thanks > > Chad > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >
CN
Chad Nelson
Wed, Mar 4, 2015 7:13 PM

Hi Ray,

OK, that makes sense. I hadn't really grokked the difference between record objects and procedural objects.

Thanks again.

Chad


From: Ray Lee rhlee@berkeley.edu
Sent: Tuesday, March 03, 2015 3:41 PM
To: Chad Nelson
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] collection-object application configuration changing the Create New form?

Hi Chad,
In mmi-collectionobject.xml you have:

<record id="collection-object" is-extension="true" type="record,procedure">

This overlays base-collectionobject.xml, which has:

<record id="collection-object" in-findedit="yes" cms-type="default" generate-services-schema="true">

So in the merged record, you end up with type="record,procedure" added to the <record>. You don't wan't that, because it tells the app layer that collectionobjects are procedures. So it moves into the Procedural Records section in the UI, and the Cataloging Records section disappears, because now there are no cataloging records. I'm guessing other things will go wrong as well.

The HTML for the Create New page is goofy, so when the Cataloging Records column disappears, things reflow in an unexpected way. I've also seen weird things happen when the heights of the columns change as you add and remove record types.

Ray

On Tue, Mar 3, 2015 at 8:05 AM, Chad Nelson <chad.nelson@lyrasis.orgmailto:chad.nelson@lyrasis.org> wrote:

Hi All,

I've added some very basic local configuration to the collection-object/cataloging procedure to add a few fields.

https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2
[https://avatars0.githubusercontent.com/u/10663125?v=3&s=400]https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2

First pass at cataloging procedure · 7dc10bc · CollectionSpace-Deployments/application · GitHub
This is a repository that contains Collection Space application layer code.
Read more...https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2

https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c
[https://avatars0.githubusercontent.com/u/10663125?v=3&s=400]https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c

First pass at adding cataloging · 5197c7d · CollectionSpace-Deployments/ui · GitHub
ui - This is a repository that contains Collection Space user interface layer code.
Read more...https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c

And If I go directly to the cataloging page, I see my changes working es expected, shown at the bottom here:
[cid:0f85e2cf-0530-4dfd-b311-ab6702b4b6ba]

But what totally confused me is that the Create New Records form has changed, losing the section specifically for Cataloging Records, and instead adding cataloging to the list of Procedural records, as well as swapping columns. Compare the updated form [cid:7a7627bd-6705-46f0-83ec-1b4f326bd73c] ?

with  the standard (4.1) form:
[cid:097ad377-7e67-4c58-a71a-a0fb94f383d3]

Anyone seen behavior like this before? I've isolated it to being related to making changes in the Application layer (i.e. if I only make those changes, the problem appears), but I'm wondering if it a function of the way the UI handles configuration? Any pointers on debugging the UI would be greatly appreciated.

Thanks

Chad


Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Hi Ray, OK, that makes sense. I hadn't really grokked the difference between record objects and procedural objects. Thanks again. Chad ________________________________ From: Ray Lee <rhlee@berkeley.edu> Sent: Tuesday, March 03, 2015 3:41 PM To: Chad Nelson Cc: talk@lists.collectionspace.org Subject: Re: [Talk] collection-object application configuration changing the Create New form? Hi Chad, In mmi-collectionobject.xml you have: <record id="collection-object" is-extension="true" type="record,procedure"> This overlays base-collectionobject.xml, which has: <record id="collection-object" in-findedit="yes" cms-type="default" generate-services-schema="true"> So in the merged record, you end up with type="record,procedure" added to the <record>. You don't wan't that, because it tells the app layer that collectionobjects are procedures. So it moves into the Procedural Records section in the UI, and the Cataloging Records section disappears, because now there are no cataloging records. I'm guessing other things will go wrong as well. The HTML for the Create New page is goofy, so when the Cataloging Records column disappears, things reflow in an unexpected way. I've also seen weird things happen when the heights of the columns change as you add and remove record types. Ray On Tue, Mar 3, 2015 at 8:05 AM, Chad Nelson <chad.nelson@lyrasis.org<mailto:chad.nelson@lyrasis.org>> wrote: Hi All, I've added some very basic local configuration to the collection-object/cataloging procedure to add a few fields. https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2 [https://avatars0.githubusercontent.com/u/10663125?v=3&s=400]<https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2> First pass at cataloging procedure · 7dc10bc · CollectionSpace-Deployments/application · GitHub This is a repository that contains Collection Space application layer code. Read more...<https://github.com/CollectionSpace-Deployments/application/commit/7dc10bc5d3214e76b75ddef2ee835a46e87894b2> https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c [https://avatars0.githubusercontent.com/u/10663125?v=3&s=400]<https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c> First pass at adding cataloging · 5197c7d · CollectionSpace-Deployments/ui · GitHub ui - This is a repository that contains Collection Space user interface layer code. Read more...<https://github.com/CollectionSpace-Deployments/ui/commit/5197c7da3adfc2840444f3ad3a9aa5eaf4bdb22c> And If I go directly to the cataloging page, I see my changes working es expected, shown at the bottom here: [cid:0f85e2cf-0530-4dfd-b311-ab6702b4b6ba] But what totally confused me is that the Create New Records form has changed, losing the section specifically for Cataloging Records, and instead adding cataloging to the list of Procedural records, as well as swapping columns. Compare the updated form [cid:7a7627bd-6705-46f0-83ec-1b4f326bd73c] ? with the standard (4.1) form: [cid:097ad377-7e67-4c58-a71a-a0fb94f383d3] Anyone seen behavior like this before? I've isolated it to being related to making changes in the Application layer (i.e. if I only make those changes, the problem appears), but I'm wondering if it a function of the way the UI handles configuration? Any pointers on debugging the UI would be greatly appreciated. Thanks Chad _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org