Your comments are invited on a proposed contribution to CollectionSpace v4.1 regarding the addition of a "Run Batch Process" menu to records. ** Please reply to the Talk list by end of day this Friday, September 26, 2014. ** A fourth contribution that we've found useful at UC Berkeley, and are proposing to add to v4.1, is to add a "Run Batch Process" menu. This menu will appear in the right sidebar when you're viewing and editing records, below the "Run Report" menu. (A screenshot of this menu is attached.) You can customize the name of this menu for your museum, as you can with many labels throughout CollectionSpace. You can also customize the location where it appears onscreen - or even hide it, if you wish. The "Run Batch Process" menu works much like the "Run Reports" menu: it allows you to run any batch jobs available to you in your current context. If there are no relevant batch jobs available, there will be no selectable options in that menu. For more details on batch job capability in CollectionSpace, please see the additional information below. Aron Roberts Research IT UC Berkeley -- Batch jobs are one of several ways that you can extend CollectionSpace for your museum's users - adding desired behaviors via your own, custom code - without touching a single line of CollectionSpace's code. They were introduced to CollectionSpace in 2012. You can invoke batch jobs by sending HTTP GET or POST requests to the Batch Service, via the Services REST APIs. The "Run Batch Job" menu extends the ability to run batch jobs to anyone logged into the CollectionSpace application (given the appropriate permissions), thus providing that capability to far more people. You can find documentation on the Batch Service's REST APIs: http://wiki.collectionspace.org/display/DOC/Batch+Job+Service+RESTful+APIs And there's also an overview of several ways to extend CollectionSpace, including via batch jobs: http://wiki.collectionspace.org/display/DOC/Extending+CollectionSpace <https://issues.collectionspace.org/browse/UCJEPS-444>