Thanks to everyone who responded to the code contribution proposals. Having heard no arguments against, we propose to add the following to v4.1, due out in November: - Valuation control procedure (Walker, community vetted earlier this year) - Condition check procedure (Walker, community vetted earlier this year) - Alternating light and dark when repeating groups of fields (UCB) - Docking title bar (UCB) - Create new from existing uses template (UCB) - Run Batch added to UI (UCB) - Run Report opens report in a new tab/window (UCB) - Created & last modified dates displayed on records (UCB) If your organization has code it would like to contribute, please add it to the code contribution register on the project wiki (http://wiki.collectionspace.org/display/collectionspace/Code+Contribution+Register?) and send a note to the talk list. We're accepting contribution proposals for v4.2 now and will send out a note to the list summarizing them once v4.1 is out the door. Thanks, 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

Megan, Richard, and community: I just remembered a gap in the batch process running capability that I was planning to contribute for 4.1. See CSPACE-5985 <http://issues.collectionspace.org/browse/CSPACE-5985>, and the linked UCBG-253 <http://issues.collectionspace.org/browse/UCBG-253>. Currently, batch jobs, as I believe is the case with reports, can be run by any user, regardless of permissions. This seems like it's especially a problem with batch jobs, since they modify data, and potentially a lot of it. Should CSPACE-5985 <http://issues.collectionspace.org/browse/CSPACE-5985> be fixed before this contribution goes in? It would certainly mean pushing it out to 4.2. Thanks, Ray On Thu, Oct 2, 2014 at 6:03 AM, Megan Forbes <megan.forbes@lyrasis.org> wrote: > Thanks to everyone who responded to the code contribution proposals. > Having heard no arguments against, we propose to add the following to v4.1, > due out in November: > > > - Valuation control procedure (Walker, community vetted earlier this > year) > > - Condition check procedure (Walker, community vetted earlier this year) > > - Alternating light and dark when repeating groups of fields (UCB) > > - Docking title bar (UCB) > > - Create new from existing uses template (UCB) > > - Run Batch added to UI (UCB) > > - Run Report opens report in a new tab/window (UCB) > > - Created & last modified dates displayed on records (UCB) > > > If your organization has code it would like to contribute, please add it > to the code contribution register on the project wiki ( > http://wiki.collectionspace.org/display/collectionspace/Code+Contribution+Register​) > and send a note to the talk list. We're accepting contribution > proposals for v4.2 now and will send out a note to the list summarizing > them once v4.1 is out the door. > > > Thanks, > > 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 > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >

Nice catch, Ray. And this seems like a slam dunk-like easy decision, at least to me: let's defer adding the 'Run batch process' menu to (at least) v4.2, until we can provide more control over which users can run batch jobs, yes? Others' thoughts welcomed ... On Thu, Oct 2, 2014 at 6:15 PM, Ray Lee <rhlee@berkeley.edu> wrote: > Megan, Richard, and community: > I just remembered a gap in the batch process running capability that I was > planning to contribute for 4.1. See CSPACE-5985 > <http://issues.collectionspace.org/browse/CSPACE-5985>, and the linked > UCBG-253 <http://issues.collectionspace.org/browse/UCBG-253>. Currently, > batch jobs, as I believe is the case with reports, can be run by any user, > regardless of permissions. This seems like it's especially a problem with > batch jobs, since they modify data, and potentially a lot of it. Should > CSPACE-5985 <http://issues.collectionspace.org/browse/CSPACE-5985> be > fixed before this contribution goes in? It would certainly mean pushing it > out to 4.2. > > Thanks, > Ray > > > On Thu, Oct 2, 2014 at 6:03 AM, Megan Forbes <megan.forbes@lyrasis.org> > wrote: > >> Thanks to everyone who responded to the code contribution proposals. >> Having heard no arguments against, we propose to add the following to v4.1, >> due out in November: >> >> >> - Valuation control procedure (Walker, community vetted earlier this >> year) >> >> - Condition check procedure (Walker, community vetted earlier this year) >> >> - Alternating light and dark when repeating groups of fields (UCB) >> >> - Docking title bar (UCB) >> >> - Create new from existing uses template (UCB) >> >> - Run Batch added to UI (UCB) >> >> - Run Report opens report in a new tab/window (UCB) >> >> - Created & last modified dates displayed on records (UCB) >> >> >> If your organization has code it would like to contribute, please add >> it to the code contribution register on the project wiki ( >> http://wiki.collectionspace.org/display/collectionspace/Code+Contribution+Register​) >> and send a note to the talk list. We're accepting contribution >> proposals for v4.2 now and will send out a note to the list summarizing >> them once v4.1 is out the door. >> >> >> Thanks, >> >> 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 >> >> >> >> _______________________________________________ >> 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 > >