CSpace Community: A quick update on the status of version 4.1 of the software. We're now officially in code freeze, and as of last week, a public beta, v4.1-B1, has been released. We currently anticipate a v4.1 final release during Fall 2014. Release notes for v4.1-B1 can be found on the project wiki: http://wiki.collectionspace.org/display/collectionspace/Release+4.1 Please note that v4.1-B1 has not gone through regression testing. We are holding off on the full QA and release process until the new tech team at LYRASIS, CollectionSpace's new organizational home, is in place. If you are a new implementer planning to go live in 2014, we strongly recommend that you implement with version 4.0, the last stable release. If you are planning to go live in 2015 or later and plan to target 4.1 for your rollout, or would like a current release to evaluate, V4.1-B1 is available for both of those purposes. If you choose to download and install v4.1-B1 and come across any issues, please file a Jira with an "affects version" of v4.1. The CollectionSpace issue tracker can be found here: http://issues.collectionspace.org<http://issues.collectionspace.org/> Please let me know if you have any questions. Best regards, Megan Megan Forbes CollectionSpace Community Outreach and Support Manager megan.forbes@lyrasis.org 800.999.8558 x 2917 Main 917.267.9676 Cell meganbforbes Skype [https://outlook.office365.com/owa/service.svc/s/GetFileAttachment?id=AQMkADI3MTNmNmI2LTUyZjItNGRjYwAtYTczMC1jMzUxNGQwNTNmZDIARgAAA5DGxfecGDtHpd%2FX9CB%2BYB4HAAsvd0H7F9JJpOCFJxIfnNgAAAIBDQAAAAsvd0H7F9JJpOCFJxIfnNgAAAIpygAAAAESABAAsH%2B1fL0FBkKO6spK01cnFw%3D%3D&X-OWA-CANARY=rkXzOYNgeEyqhfXepGlIH35HlhYWDNEI4yMYSb0gDN-eG7iT29zNufpAHfE4mRo6ZEhPMMtd1QU.]<http://www.lyrasis.org/>

Hi Megan, and talk, Thanks for the update. I'm wondering how we should proceed with our implementation at OMCA, and if you have any advice. We were initially advised to wait for 4.1, but our plan was to do an initial, test migration this summer in a month or so, with the goal of a final migration in the fall. What version do you suggest we use for our testing period? Will we put ourselves in a bind if we test with 4.0 and migrate to 4.1? Thanks again, Al On Thu, May 29, 2014 at 7:15 AM, Megan Forbes <megan.forbes@lyrasis.org> wrote: > CSpace Community: > > A quick update on the status of version 4.1 of the software. We're now > officially in code freeze, and as of last week, a public beta, v4.1-B1, > has been released. We currently anticipate a v4.1 final release during > Fall 2014. > > Release notes for v4.1-B1 can be found on the project wiki: > http://wiki.collectionspace.org/display/collectionspace/Release+4.1 > > Please note that v4.1-B1 has not gone through regression testing. We are holding > off on the full QA and release process until the new tech team at > LYRASIS, CollectionSpace's new organizational home, is in place. If you > are a new implementer planning to go live in 2014, we strongly recommend > that you implement with version 4.0, the last stable release. If you are > planning to go live in 2015 or later and plan to target 4.1 for your > rollout, or would like a current release to evaluate, V4.1-B1 is > available for both of those purposes. > > If you choose to download and install v4.1-B1 and come across any > issues, please file a Jira with an "affects version" of v4.1. The > CollectionSpace issue tracker can be found here: > http://issues.collectionspace.org > > > Please let me know if you have any questions. > > > Best regards, > > Megan > > > > Megan Forbes > CollectionSpace Community Outreach and Support Manager > *megan.forbes@lyrasis.org <megan.forbes@lyrasis.org>* > 800.999.8558 x 2917 Main > 917.267.9676 Cell > meganbforbes Skype > > <http://www.lyrasis.org/> > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > -- Al Bersch Digital Project Coordinator Oakland Museum of California 1000 Oak Street, Oakland, CA 94607 abersch@museumca.org 510-318-8468

Hi Al, Thanks for these good questions. If you target 4.0, you should have a fairly straightforward upgrade to 4.1, from what I understand of the differences between these releases. There are relatively few changes to configuration and no schema changes that I can recall. And if you need specific bugfixes in 4.1, they can be patched into 4.0. Ray Lee, our wizard-of-many-things who found, analyzed and fixed many key bugs, as reflected in contributions to the in-process 4.1 release, has done this patching for the UCB implementations, AFAIK. The timing of 4.1's final release depends largely on the availability of LYRASIS's team-to-be-hired. And we can and will keep you and the community updated on both, as that progresses. Aron P.S. Other comments and suggestions by the project team and implementers are welcomed here, as well! On Thu, May 29, 2014 at 11:05 AM, Al Bersch <abersch@museumca.org> wrote: > Hi Megan, and talk, > > Thanks for the update. I'm wondering how we should proceed with our > implementation at OMCA, and if you have any advice. We were initially > advised to wait for 4.1, but our plan was to do an initial, test migration > this summer in a month or so, with the goal of a final migration in the > fall. What version do you suggest we use for our testing period? Will we > put ourselves in a bind if we test with 4.0 and migrate to 4.1? > > Thanks again, > > Al > > > On Thu, May 29, 2014 at 7:15 AM, Megan Forbes <megan.forbes@lyrasis.org> > wrote: > >> CSpace Community: >> >> A quick update on the status of version 4.1 of the software. We're now >> officially in code freeze, and as of last week, a public beta, v4.1-B1, >> has been released. We currently anticipate a v4.1 final release during >> Fall 2014. >> >> Release notes for v4.1-B1 can be found on the project wiki: >> http://wiki.collectionspace.org/display/collectionspace/Release+4.1 >> >> Please note that v4.1-B1 has not gone through regression testing. We are holding >> off on the full QA and release process until the new tech team at >> LYRASIS, CollectionSpace's new organizational home, is in place. If you >> are a new implementer planning to go live in 2014, we strongly recommend >> that you implement with version 4.0, the last stable release. If you are >> planning to go live in 2015 or later and plan to target 4.1 for your >> rollout, or would like a current release to evaluate, V4.1-B1 is >> available for both of those purposes. >> >> If you choose to download and install v4.1-B1 and come across any >> issues, please file a Jira with an "affects version" of v4.1. The >> CollectionSpace issue tracker can be found here: >> http://issues.collectionspace.org >> >> >> Please let me know if you have any questions. >> >> >> Best regards, >> >> Megan >> >> >> >> Megan Forbes >> CollectionSpace Community Outreach and Support Manager >> *megan.forbes@lyrasis.org <megan.forbes@lyrasis.org>* >> 800.999.8558 x 2917 Main >> 917.267.9676 Cell >> meganbforbes Skype >> >> <http://www.lyrasis.org/> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> > > > -- > Al Bersch > Digital Project Coordinator > 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 > >

Ray, Do you have a list of patches that you've added to 4.0? I've heard that there is an important current location update patch and that there is a structured date data entry widget that is useful. Others, what is in 4.1 that isn't among the patches to 4.0 (that would make a patched 4.0 more stable than 4.1 beta)? Susan On Thu, May 29, 2014 at 11:16 AM, Aron Roberts <aronroberts@gmail.com> wrote: > Hi Al, > > Thanks for these good questions. If you target 4.0, you should have a > fairly straightforward upgrade to 4.1, from what I understand of the > differences between these releases. There are relatively few changes to > configuration and no schema changes that I can recall. > > And if you need specific bugfixes in 4.1, they can be patched into 4.0. > Ray Lee, our wizard-of-many-things who found, analyzed and fixed many key > bugs, as reflected in contributions to the in-process 4.1 release, has done > this patching for the UCB implementations, AFAIK. > > The timing of 4.1's final release depends largely on the availability of > LYRASIS's team-to-be-hired. And we can and will keep you and the community > updated on both, as that progresses. > > Aron > > P.S. Other comments and suggestions by the project team and implementers > are welcomed here, as well! > > On Thu, May 29, 2014 at 11:05 AM, Al Bersch <abersch@museumca.org> wrote: > >> Hi Megan, and talk, >> >> Thanks for the update. I'm wondering how we should proceed with our >> implementation at OMCA, and if you have any advice. We were initially >> advised to wait for 4.1, but our plan was to do an initial, test migration >> this summer in a month or so, with the goal of a final migration in the >> fall. What version do you suggest we use for our testing period? Will we >> put ourselves in a bind if we test with 4.0 and migrate to 4.1? >> >> Thanks again, >> >> Al >> >> >> On Thu, May 29, 2014 at 7:15 AM, Megan Forbes <megan.forbes@lyrasis.org> >> wrote: >> >>> CSpace Community: >>> >>> A quick update on the status of version 4.1 of the software. We're now >>> officially in code freeze, and as of last week, a public beta, v4.1-B1, >>> has been released. We currently anticipate a v4.1 final release during >>> Fall 2014. >>> >>> Release notes for v4.1-B1 can be found on the project wiki: >>> http://wiki.collectionspace.org/display/collectionspace/Release+4.1 >>> >>> Please note that v4.1-B1 has not gone through regression testing. We >>> are holding off on the full QA and release process until the new tech >>> team at LYRASIS, CollectionSpace's new organizational home, is in >>> place. If you are a new implementer planning to go live in 2014, we >>> strongly recommend that you implement with version 4.0, the last stable >>> release. If you are planning to go live in 2015 or later and plan to target >>> 4.1 for your rollout, or would like a current release to evaluate, >>> V4.1-B1 is available for both of those purposes. >>> >>> If you choose to download and install v4.1-B1 and come across any >>> issues, please file a Jira with an "affects version" of v4.1. The >>> CollectionSpace issue tracker can be found here: >>> http://issues.collectionspace.org >>> >>> >>> Please let me know if you have any questions. >>> >>> >>> Best regards, >>> >>> Megan >>> >>> >>> >>> Megan Forbes >>> CollectionSpace Community Outreach and Support Manager >>> *megan.forbes@lyrasis.org <megan.forbes@lyrasis.org>* >>> 800.999.8558 x 2917 Main >>> 917.267.9676 Cell >>> meganbforbes Skype >>> >>> <http://www.lyrasis.org/> >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >>> >> >> >> -- >> Al Bersch >> Digital Project Coordinator >> 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 > >

Susan, I started to compile a list of 4.1 bug fixes that I've patched into the UCB 4.0 branch, but then I realized that it's almost all of them. Most of the fixes made in 4.1 were driven by issues we encountered in UCB's 4.0 production systems, which we wanted to address quickly. To be clear, there's no official patched release of CollectionSpace 4.0. We've just been cherry-picking commits from master into our fork of the code. The 4.1 beta release notes <http://wiki.collectionspace.org/display/collectionspace/Release+4.1> that Aron wrote do an excellent job of describing the bugs and their impacts, so I recommend reading them to see which fixes are important to you. I would highlight the following as the most important for stability: First, bugs that may cause data corruption: - Display name updates are now performed deterministically, no longer missing some update targets (CSPACE-6333) <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Displaynameupdatesarenowperformeddeterministically,nolongermissingsomeupdatetargets(CSPACE-6333)> - Authority term records opened from search results now always appear in the correct vocabulary (CSPACE-6339) <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Authoritytermrecordsopenedfromsearchresultsnowalwaysappearinthecorrectvocabulary(CSPACE-6339)> - Floating decimal field values in the Place record are now validated (CSPACE-6323) <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-FloatingdecimalfieldvaluesinthePlacerecordarenowvalidated(CSPACE-6323)> - Changing the case of display names now successfully updates refName display names in collectionspace_core (CSPACE-6372) <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-ChangingthecaseofdisplaynamesnowsuccessfullyupdatesrefNamedisplaynamesincollectionspace_core(CSPACE-6372)> - Existi <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Existingvocabularytermsarenolongerduplicatedoroverwrittenduringauthoritiesinitialization(CSPACE-6302)>ng vocabulary terms are no longer duplicated or overwritten during authorities initialization (CSPACE-6302) <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Existingvocabularytermsarenolongerduplicatedoroverwrittenduringauthoritiesinitialization(CSPACE-6302)> - Deleted vocabulary terms are no longer inadvertently re-created during authorities initialization (CSPACE-6371) <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Deletedvocabularytermsarenolongerinadvertentlyre-createdduringauthoritiesinitialization(CSPACE-6371)> Next, bugs that kill performance in some situations: - Number of simultaneous Application layer connections to the Services layer has been significantly increased (CSPACE-6284) <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-NumberofsimultaneousApplicationlayerconnectionstotheServiceslayerhasbeensignificantlyincreased(CSPACE-6284)> - Resolution of slowdowns and out of memory conditions, where an authority term is referred to by large numbers of records (CSPACE-6286) <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Resolutionofslowdownsandoutofmemoryconditions,whereanauthoritytermisreferredtobylargenumbersofrecords(CSPACE-6286)> There are also performance related fixes that help when you have many media records, and many downloads of images from those records. You asked about current location: there were a couple changes to how current location is computed, which may or may not be important to you: - Computed current locations in Cataloging records can no longer be set to blank locations (CSPACE-6308) <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-ComputedcurrentlocationsinCatalogingrecordscannolongerbesettoblanklocations(CSPACE-6308)> - The most recent Movement (L/M/I) record is now identified by its modification date, not its creation date, for tiebreaking purposes (CSPACE-6307) <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-ThemostrecentMovement(L/M/I)recordisnowidentifiedbyitsmodificationdate,notitscreationdate,fortiebreakingpurposes(CSPACE-6307)> The structured date widget you mention, which parses the display date and automatically fills in the structured date fields, might be a contribution at some point, but it's not in 4.1. It currently only exists in the UCB fork. Ray On Thu, May 29, 2014 at 11:26 AM, Susan STONE <sstone@berkeley.edu> wrote: > Ray, > > Do you have a list of patches that you've added to 4.0? > > I've heard that there is an important current location update patch and > that there is a structured date data entry widget that is useful. > > Others, what is in 4.1 that isn't among the patches to 4.0 (that would > make a patched 4.0 more stable than 4.1 beta)? > > Susan > > > On Thu, May 29, 2014 at 11:16 AM, Aron Roberts <aronroberts@gmail.com> > wrote: > >> Hi Al, >> >> Thanks for these good questions. If you target 4.0, you should have a >> fairly straightforward upgrade to 4.1, from what I understand of the >> differences between these releases. There are relatively few changes to >> configuration and no schema changes that I can recall. >> >> And if you need specific bugfixes in 4.1, they can be patched into >> 4.0. Ray Lee, our wizard-of-many-things who found, analyzed and fixed many >> key bugs, as reflected in contributions to the in-process 4.1 release, has >> done this patching for the UCB implementations, AFAIK. >> >> The timing of 4.1's final release depends largely on the availability >> of LYRASIS's team-to-be-hired. And we can and will keep you and the >> community updated on both, as that progresses. >> >> Aron >> >> P.S. Other comments and suggestions by the project team and implementers >> are welcomed here, as well! >> >> On Thu, May 29, 2014 at 11:05 AM, Al Bersch <abersch@museumca.org> wrote: >> >>> Hi Megan, and talk, >>> >>> Thanks for the update. I'm wondering how we should proceed with our >>> implementation at OMCA, and if you have any advice. We were initially >>> advised to wait for 4.1, but our plan was to do an initial, test migration >>> this summer in a month or so, with the goal of a final migration in the >>> fall. What version do you suggest we use for our testing period? Will we >>> put ourselves in a bind if we test with 4.0 and migrate to 4.1? >>> >>> Thanks again, >>> >>> Al >>> >>> >>> On Thu, May 29, 2014 at 7:15 AM, Megan Forbes <megan.forbes@lyrasis.org> >>> wrote: >>> >>>> CSpace Community: >>>> >>>> A quick update on the status of version 4.1 of the software. We're now >>>> officially in code freeze, and as of last week, a public beta, >>>> v4.1-B1, has been released. We currently anticipate a v4.1 final >>>> release during Fall 2014. >>>> >>>> Release notes for v4.1-B1 can be found on the project wiki: >>>> http://wiki.collectionspace.org/display/collectionspace/Release+4.1 >>>> >>>> Please note that v4.1-B1 has not gone through regression testing. We >>>> are holding off on the full QA and release process until the new tech >>>> team at LYRASIS, CollectionSpace's new organizational home, is in >>>> place. If you are a new implementer planning to go live in 2014, we >>>> strongly recommend that you implement with version 4.0, the last >>>> stable release. If you are planning to go live in 2015 or later and >>>> plan to target 4.1 for your rollout, or would like a current release >>>> to evaluate, V4.1-B1 is available for both of those purposes. >>>> >>>> If you choose to download and install v4.1-B1 and come across any >>>> issues, please file a Jira with an "affects version" of v4.1. The >>>> CollectionSpace issue tracker can be found here: >>>> http://issues.collectionspace.org >>>> >>>> >>>> Please let me know if you have any questions. >>>> >>>> >>>> Best regards, >>>> >>>> Megan >>>> >>>> >>>> >>>> Megan Forbes >>>> CollectionSpace Community Outreach and Support Manager >>>> *megan.forbes@lyrasis.org <megan.forbes@lyrasis.org>* >>>> 800.999.8558 x 2917 Main >>>> 917.267.9676 Cell >>>> meganbforbes Skype >>>> >>>> <http://www.lyrasis.org/> >>>> >>>> _______________________________________________ >>>> Talk mailing list >>>> Talk@lists.collectionspace.org >>>> >>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>> >>>> >>> >>> >>> -- >>> Al Bersch >>> Digital Project Coordinator >>> 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 >> >> >

- Display name updates are now performed deterministically, no longer
missing some update targets (CSPACE-6333)
<http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Displaynameupdatesarenowperformeddeterministically,nolongermissingsomeupdatetargets(CSPACE-6333)>
- Authority term records opened from search results now always appear
in the correct vocabulary (CSPACE-6339)
<http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Authoritytermrecordsopenedfromsearchresultsnowalwaysappearinthecorrectvocabulary(CSPACE-6339)>
- Floating decimal field values in the Place record are now validated
(CSPACE-6323)
<http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-FloatingdecimalfieldvaluesinthePlacerecordarenowvalidated(CSPACE-6323)>
- Changing the case of display names now successfully updates refName
display names in collectionspace_core (CSPACE-6372)
<http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-ChangingthecaseofdisplaynamesnowsuccessfullyupdatesrefNamedisplaynamesincollectionspace_core(CSPACE-6372)>
- Existi
<http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Existingvocabularytermsarenolongerduplicatedoroverwrittenduringauthoritiesinitialization(CSPACE-6302)>ng
vocabulary terms are no longer duplicated or overwritten during authorities
initialization (CSPACE-6302)
<http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Existingvocabularytermsarenolongerduplicatedoroverwrittenduringauthoritiesinitialization(CSPACE-6302)>
- Deleted vocabulary terms are no longer inadvertently re-created
during authorities initialization (CSPACE-6371)
<http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Deletedvocabularytermsarenolongerinadvertentlyre-createdduringauthoritiesinitialization(CSPACE-6371)>

- Number of simultaneous Application layer connections to the Services
layer has been significantly increased (CSPACE-6284)
<http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-NumberofsimultaneousApplicationlayerconnectionstotheServiceslayerhasbeensignificantlyincreased(CSPACE-6284)>
- Resolution of slowdowns and out of memory conditions, where an
authority term is referred to by large numbers of records (CSPACE-6286)
<http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Resolutionofslowdownsandoutofmemoryconditions,whereanauthoritytermisreferredtobylargenumbersofrecords(CSPACE-6286)>

- Computed current locations in Cataloging records can no longer be
set to blank locations (CSPACE-6308)
<http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-ComputedcurrentlocationsinCatalogingrecordscannolongerbesettoblanklocations(CSPACE-6308)>
- The most recent Movement (L/M/I) record is now identified by its
modification date, not its creation date, for tiebreaking purposes
(CSPACE-6307)
<http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-ThemostrecentMovement(L/M/I)recordisnowidentifiedbyitsmodificationdate,notitscreationdate,fortiebreakingpurposes(CSPACE-6307)>

Ray, Thanks so much for taking the time to give a thorough and useful answer to my questions that will help us patch 4.0 if we go ahead with that version. I'm still wondering whether the 4.1 beta would necessarily be less robust than a patched 4.0, especially if we did our testing and review in 4.1 beta and were likely to be able to do the final migration into 4.1 when it is released. I guess we'd find out! I know the official policy is to implement 4.0 at this time. Susan On Fri, May 30, 2014 at 2:17 PM, Ray Lee <rhlee@berkeley.edu> wrote: > Susan, > I started to compile a list of 4.1 bug fixes that I've patched into the > UCB 4.0 branch, but then I realized that it's almost all of them. Most of > the fixes made in 4.1 were driven by issues we encountered in UCB's 4.0 > production systems, which we wanted to address quickly. > > To be clear, there's no official patched release of CollectionSpace 4.0. > We've just been cherry-picking commits from master into our fork of the > code. > > The 4.1 beta release notes > <http://wiki.collectionspace.org/display/collectionspace/Release+4.1> > that Aron wrote do an excellent job of describing the bugs and their > impacts, so I recommend reading them to see which fixes are important to > you. I would highlight the following as the most important for stability: > > First, bugs that may cause data corruption: > > > - Display name updates are now performed deterministically, no longer > missing some update targets (CSPACE-6333) > <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Displaynameupdatesarenowperformeddeterministically,nolongermissingsomeupdatetargets(CSPACE-6333)> > - Authority term records opened from search results now always appear > in the correct vocabulary (CSPACE-6339) > <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Authoritytermrecordsopenedfromsearchresultsnowalwaysappearinthecorrectvocabulary(CSPACE-6339)> > - Floating decimal field values in the Place record are now validated > (CSPACE-6323) > <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-FloatingdecimalfieldvaluesinthePlacerecordarenowvalidated(CSPACE-6323)> > - Changing the case of display names now successfully updates refName > display names in collectionspace_core (CSPACE-6372) > <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-ChangingthecaseofdisplaynamesnowsuccessfullyupdatesrefNamedisplaynamesincollectionspace_core(CSPACE-6372)> > - Existi > <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Existingvocabularytermsarenolongerduplicatedoroverwrittenduringauthoritiesinitialization(CSPACE-6302)>ng > vocabulary terms are no longer duplicated or overwritten during authorities > initialization (CSPACE-6302) > <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Existingvocabularytermsarenolongerduplicatedoroverwrittenduringauthoritiesinitialization(CSPACE-6302)> > - Deleted vocabulary terms are no longer inadvertently re-created > during authorities initialization (CSPACE-6371) > <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Deletedvocabularytermsarenolongerinadvertentlyre-createdduringauthoritiesinitialization(CSPACE-6371)> > > > Next, bugs that kill performance in some situations: > > > - Number of simultaneous Application layer connections to the Services > layer has been significantly increased (CSPACE-6284) > <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-NumberofsimultaneousApplicationlayerconnectionstotheServiceslayerhasbeensignificantlyincreased(CSPACE-6284)> > - Resolution of slowdowns and out of memory conditions, where an > authority term is referred to by large numbers of records (CSPACE-6286) > <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-Resolutionofslowdownsandoutofmemoryconditions,whereanauthoritytermisreferredtobylargenumbersofrecords(CSPACE-6286)> > > > There are also performance related fixes that help when you have many > media records, and many downloads of images from those records. > > You asked about current location: there were a couple changes to how > current location is computed, which may or may not be important to you: > > > - Computed current locations in Cataloging records can no longer be > set to blank locations (CSPACE-6308) > <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-ComputedcurrentlocationsinCatalogingrecordscannolongerbesettoblanklocations(CSPACE-6308)> > - The most recent Movement (L/M/I) record is now identified by its > modification date, not its creation date, for tiebreaking purposes > (CSPACE-6307) > <http://wiki.collectionspace.org/display/collectionspace/Release+4.1#Release4.1-ThemostrecentMovement(L/M/I)recordisnowidentifiedbyitsmodificationdate,notitscreationdate,fortiebreakingpurposes(CSPACE-6307)> > > > The structured date widget you mention, which parses the display date and > automatically fills in the structured date fields, might be a contribution > at some point, but it's not in 4.1. It currently only exists in the UCB > fork. > > Ray > > > > On Thu, May 29, 2014 at 11:26 AM, Susan STONE <sstone@berkeley.edu> wrote: > >> Ray, >> >> Do you have a list of patches that you've added to 4.0? >> >> I've heard that there is an important current location update patch and >> that there is a structured date data entry widget that is useful. >> >> Others, what is in 4.1 that isn't among the patches to 4.0 (that would >> make a patched 4.0 more stable than 4.1 beta)? >> >> Susan >> >> >> On Thu, May 29, 2014 at 11:16 AM, Aron Roberts <aronroberts@gmail.com> >> wrote: >> >>> Hi Al, >>> >>> Thanks for these good questions. If you target 4.0, you should have a >>> fairly straightforward upgrade to 4.1, from what I understand of the >>> differences between these releases. There are relatively few changes to >>> configuration and no schema changes that I can recall. >>> >>> And if you need specific bugfixes in 4.1, they can be patched into >>> 4.0. Ray Lee, our wizard-of-many-things who found, analyzed and fixed many >>> key bugs, as reflected in contributions to the in-process 4.1 release, has >>> done this patching for the UCB implementations, AFAIK. >>> >>> The timing of 4.1's final release depends largely on the availability >>> of LYRASIS's team-to-be-hired. And we can and will keep you and the >>> community updated on both, as that progresses. >>> >>> Aron >>> >>> P.S. Other comments and suggestions by the project team and implementers >>> are welcomed here, as well! >>> >>> On Thu, May 29, 2014 at 11:05 AM, Al Bersch <abersch@museumca.org> >>> wrote: >>> >>>> Hi Megan, and talk, >>>> >>>> Thanks for the update. I'm wondering how we should proceed with our >>>> implementation at OMCA, and if you have any advice. We were initially >>>> advised to wait for 4.1, but our plan was to do an initial, test migration >>>> this summer in a month or so, with the goal of a final migration in the >>>> fall. What version do you suggest we use for our testing period? Will we >>>> put ourselves in a bind if we test with 4.0 and migrate to 4.1? >>>> >>>> Thanks again, >>>> >>>> Al >>>> >>>> >>>> On Thu, May 29, 2014 at 7:15 AM, Megan Forbes <megan.forbes@lyrasis.org >>>> > wrote: >>>> >>>>> CSpace Community: >>>>> >>>>> A quick update on the status of version 4.1 of the software. We're >>>>> now officially in code freeze, and as of last week, a public beta, >>>>> v4.1-B1, has been released. We currently anticipate a v4.1 final >>>>> release during Fall 2014. >>>>> >>>>> Release notes for v4.1-B1 can be found on the project wiki: >>>>> http://wiki.collectionspace.org/display/collectionspace/Release+4.1 >>>>> >>>>> Please note that v4.1-B1 has not gone through regression testing. We >>>>> are holding off on the full QA and release process until the new tech >>>>> team at LYRASIS, CollectionSpace's new organizational home, is in >>>>> place. If you are a new implementer planning to go live in 2014, we >>>>> strongly recommend that you implement with version 4.0, the last >>>>> stable release. If you are planning to go live in 2015 or later and >>>>> plan to target 4.1 for your rollout, or would like a current release >>>>> to evaluate, V4.1-B1 is available for both of those purposes. >>>>> >>>>> If you choose to download and install v4.1-B1 and come across any >>>>> issues, please file a Jira with an "affects version" of v4.1. The >>>>> CollectionSpace issue tracker can be found here: >>>>> http://issues.collectionspace.org >>>>> >>>>> >>>>> Please let me know if you have any questions. >>>>> >>>>> >>>>> Best regards, >>>>> >>>>> Megan >>>>> >>>>> >>>>> >>>>> Megan Forbes >>>>> CollectionSpace Community Outreach and Support Manager >>>>> *megan.forbes@lyrasis.org <megan.forbes@lyrasis.org>* >>>>> 800.999.8558 x 2917 Main >>>>> 917.267.9676 Cell >>>>> meganbforbes Skype >>>>> >>>>> <http://www.lyrasis.org/> >>>>> >>>>> _______________________________________________ >>>>> Talk mailing list >>>>> Talk@lists.collectionspace.org >>>>> >>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>>> >>>>> >>>> >>>> >>>> -- >>>> Al Bersch >>>> Digital Project Coordinator >>>> 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 >>> >>> >> >