Hi folks, At OMCA, we're looking at a widget developed for BAMPFA that turns dimensionSummary into a computed field. Here's a JIRA for the widget: https://issues.collectionspace.org/browse/BAMPFA-207 The one issue we're having with the decision to use the computed widget is that we'll lose the previously populated text summary data. So I wanted to ask if anyone out there (Ray, I could just email you, but wanted to ask publicly) using this widget has been able to figure out a work around to update the summary data. We've noticed that it populates when the record is saved. Did folks at BAMPFA run an update to trigger the automation, or was the summary populated when they migrated? this would be a fantastic contribution to the core software in a future release. Thanks again - really appreciate it! Al -- Al Bersch Collections Systems Manager Oakland Museum of California 1000 Oak Street, Oakland, CA 94607 abersch@museumca.org 510-318-8468

Hi Al, I agree that this is a really nice feature that we added for BAMPFA! I can say that when we migrated the measurement data from BAMPFA’s FileMaker system, we calculated and stored the summary text from the atomic height, width, depth, and diameter values they wanted to retain. We also appended a measurement note field that was in their system. If I recall correctly, Ray has implemented this as a batch process in CollectionSpace that fires when the cataloging record is saved. I think the batch process also concatenates in the Measured Part and the Measured Part Note field into the summary text, so you could have something like “sheet: 24 x 36 in.; from memory”. Are you able to re-migrate your data, or are you looking to update an existing system? Thanks, Chris > On Jun 1, 2016, at 4:25 PM, Al Bersch <abersch@museumca.org> wrote: > > Hi folks, > > At OMCA, we're looking at a widget developed for BAMPFA that turns dimensionSummary into a computed field. > > Here's a JIRA for the widget: https://issues.collectionspace.org/browse/BAMPFA-207 <https://issues.collectionspace.org/browse/BAMPFA-207> > > The one issue we're having with the decision to use the computed widget is that we'll lose the previously populated text summary data. So I wanted to ask if anyone out there (Ray, I could just email you, but wanted to ask publicly) using this widget has been able to figure out a work around to update the summary data. We've noticed that it populates when the record is saved. Did folks at BAMPFA run an update to trigger the automation, or was the summary populated when they migrated? > > this would be a fantastic contribution to the core software in a future release. > > Thanks again - really appreciate it! > > Al > > > -- > Al Bersch > Collections Systems Manager > Oakland Museum of California > 1000 Oak Street, Oakland, CA 94607 > abersch@museumca.org <mailto:abersch@museumca.org> > 510-318-8468 > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Al and Chris, This is actually not a batch job, it's computed in the UI. The nice thing is that the user sees the summary update in real time as they change values. The downside is that the computation is in JavaScript, which can be harder to incorporate into a bulk update or data migration workflow (though Node.js can be useful). My recollection is that the summary computation matches the one that was used in BAMPFA's legacy FileMaker system (or it's pretty close), so all we had to do was import their data into CSpace. We only had to worry about dimensions created or updated in CSpace after the migration. Ray On Wed, Jun 1, 2016 at 8:24 PM, Chris Hoffman <chris_h@berkeley.edu> wrote: > Hi Al, > > I agree that this is a really nice feature that we added for BAMPFA! I > can say that when we migrated the measurement data from BAMPFA’s FileMaker > system, we calculated and stored the summary text from the atomic height, > width, depth, and diameter values they wanted to retain. We also appended > a measurement note field that was in their system. > > If I recall correctly, Ray has implemented this as a batch process in > CollectionSpace that fires when the cataloging record is saved. I think > the batch process also concatenates in the Measured Part and the Measured > Part Note field into the summary text, so you could have something like > “sheet: 24 x 36 in.; from memory”. > > Are you able to re-migrate your data, or are you looking to update an > existing system? > > Thanks, > Chris > > > On Jun 1, 2016, at 4:25 PM, Al Bersch <abersch@museumca.org> wrote: > > Hi folks, > > At OMCA, we're looking at a widget developed for BAMPFA that turns > dimensionSummary into a computed field. > > Here's a JIRA for the widget: > https://issues.collectionspace.org/browse/BAMPFA-207 > > The one issue we're having with the decision to use the computed widget is > that we'll lose the previously populated text summary data. So I wanted to > ask if anyone out there (Ray, I could just email you, but wanted to ask > publicly) using this widget has been able to figure out a work around to > update the summary data. We've noticed that it populates when the record is > saved. Did folks at BAMPFA run an update to trigger the automation, or was > the summary populated when they migrated? > > this would be a fantastic contribution to the core software in a future > release. > > Thanks again - really appreciate it! > > Al > > > -- > Al Bersch > Collections Systems Manager > Oakland Museum of California > 1000 Oak Street, Oakland, CA 94607 > abersch@museumca.org > 510-318-8468 > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >

Hi Ray and Chris, Thanks so much for getting back to me. We've since realized that my question about updating may be moot: we were expecting the widget to overwrite the existing values once the field behavior was changed (presumably, with an empty field that could then be populated with dimensions summary once the dimensions were saved). However, it looks like the old data is overwritten only when the field is saved. If our old manual summary data will remain until updated, that's fine. It's more just an issue if the field is blank until updating. I've now made a JIRA for this: https://issues.collectionspace.org/browse/OMCA-24, in case future conversations arise, or this one continues... thanks again, Al On Wed, Jun 1, 2016 at 10:45 PM, Ray Lee <rhlee@berkeley.edu> wrote: > Al and Chris, > This is actually not a batch job, it's computed in the UI. The nice thing > is that the user sees the summary update in real time as they change > values. The downside is that the computation is in JavaScript, which can be > harder to incorporate into a bulk update or data migration workflow (though > Node.js can be useful). > > My recollection is that the summary computation matches the one that was > used in BAMPFA's legacy FileMaker system (or it's pretty close), so all we > had to do was import their data into CSpace. We only had to worry about > dimensions created or updated in CSpace after the migration. > > Ray > > > On Wed, Jun 1, 2016 at 8:24 PM, Chris Hoffman <chris_h@berkeley.edu> > wrote: > >> Hi Al, >> >> I agree that this is a really nice feature that we added for BAMPFA! I >> can say that when we migrated the measurement data from BAMPFA’s FileMaker >> system, we calculated and stored the summary text from the atomic height, >> width, depth, and diameter values they wanted to retain. We also appended >> a measurement note field that was in their system. >> >> If I recall correctly, Ray has implemented this as a batch process in >> CollectionSpace that fires when the cataloging record is saved. I think >> the batch process also concatenates in the Measured Part and the Measured >> Part Note field into the summary text, so you could have something like >> “sheet: 24 x 36 in.; from memory”. >> >> Are you able to re-migrate your data, or are you looking to update an >> existing system? >> >> Thanks, >> Chris >> >> >> On Jun 1, 2016, at 4:25 PM, Al Bersch <abersch@museumca.org> wrote: >> >> Hi folks, >> >> At OMCA, we're looking at a widget developed for BAMPFA that turns >> dimensionSummary into a computed field. >> >> Here's a JIRA for the widget: >> https://issues.collectionspace.org/browse/BAMPFA-207 >> >> The one issue we're having with the decision to use the computed widget >> is that we'll lose the previously populated text summary data. So I wanted >> to ask if anyone out there (Ray, I could just email you, but wanted to ask >> publicly) using this widget has been able to figure out a work around to >> update the summary data. We've noticed that it populates when the record is >> saved. Did folks at BAMPFA run an update to trigger the automation, or was >> the summary populated when they migrated? >> >> this would be a fantastic contribution to the core software in a future >> release. >> >> Thanks again - really appreciate it! >> >> Al >> >> >> -- >> Al Bersch >> Collections Systems Manager >> Oakland Museum of California >> 1000 Oak Street, Oakland, CA 94607 >> abersch@museumca.org >> 510-318-8468 >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> > -- Al Bersch Collections Systems Manager Oakland Museum of California 1000 Oak Street, Oakland, CA 94607 abersch@museumca.org 510-318-8468