Deploying V1.3 on BGCSPACE

Instances:

CollectionSpace V1.3 has been deployed on two hosts for evaluation and testing.

bgcspace.berkeley.edu: V1.3 has been installed with the customizations that were developed on the ucjeps.collectionspace.org slice.

pahma-demo.collectionspace.org: V1.3 has been installed with the customizations from pahma.collectionspace.org.

Progress:

So far, the installations have been without problems.  The customized configuration files have been imported with only a minor amount of editing, and the few changes involved did not appear to be critical.

We are now working on getting the Java data loading programs ready for use with the 1.3 release.

Feb 25 to Mar 2

Data loaded so far

vocabularies: collection, phase, form, loanout status

persons: 8,780

organizations: 49,455

collection objects: 369,943

loans out: 3,903

relations: 23,974 (these are symmetrical so, realistically, cut the number in half)

The data loading programs had to be modified, so far, in the organizations loader and in the collection objects loader. The organization's display name and short  name and comments are now passed to the OrgAuthorityClientUtils in an instance of MainBodyGroup.  The collection objects title is now in a group struct and it is being passed to the CollectionObjectClient in a TitleGroupList.

There is a problem with field_loc_place which is not being accepted by the CollectioObjectClient. For now, I have just commented it out of the loader program. I wonder if this should be fieldcollectionplace?

The drop-down lists that are defined in cspace-config.xml are not working.

Mar 4

Updated collectionobjects_common, inserted field_loc_place into the fieldcollectionplace column. fieldcollectionplace displays as  "Field Collection Location Verbatim".

Search times are very slow and often do not return.