Hello all, Here's another question: We're trying to figure out the best framework for reporting from CSpace. Jesse thought that there might be efforts underway to include some of UCB's reporting webapps in the next release. Does anyone know if that's the case, and if so, what the plan is? Or, is there a recommended current framework for reporting? Thanks all, Al -- Al Bersch Collections Systems Manager Oakland Museum of California 1000 Oak Street, Oakland, CA 94607 abersch@museumca.org 510-318-8468

Hi Al, We at UCB are talking with Megan and Richard about contributing some of the other customizations we have, especially to help set up one of the community profiles (for herbaria). There are a couple things on the reporting side that we'd be happy to help you set up. For iReports, we were frustrated by the inability to allow the user to provide parameters to the report via the CSpace UI. So we've developed a Django web app that allows a user to select an iReport and then type in the parameters they need to query (e.g., a date range, or a scientific name). The "bigger" solution is the public portal we have developed, also in Django. Here's an example: http://ucjeps.berkeley.edu/specimens/ This involves running a query each night that extracts data that can be loaded as a Solr data source, and then the Django app is a nice search interface that uses Solr and also points back to CSpace via the API. We've found this is a powerful tool for more complex (and faster) searches. There's a "Download CSV" button that people can use as well. We've wanted to contribute these to CSpace Core, but have been too busy to engage on this sufficiently. However, the code is available in github, and some of it is pretty well documented. We'd be happy to explain it to anyone interested! And we'd love to treat it as a community resource that others could help improve. Thanks, Chris On Mar 3, 2015, at 9:59 AM, Al Bersch <abersch@museumca.org> wrote: > Hello all, > > Here's another question: > > We're trying to figure out the best framework for reporting from CSpace. Jesse thought that there might be efforts underway to include some of UCB's reporting webapps in the next release. Does anyone know if that's the case, and if so, what the plan is? Or, is there a recommended current framework for reporting? > > Thanks all, > > 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

Hi Chris, Thanks for getting back to me, and offering to share/explain your work. The public portal is great. I know we'd like to implement something similar for our online collections, eventually. For now, we'd be interested in looking at the web app for adding parameters to queries in iReport. I think the first step might be for us to play around with iReport. Let me get back to you! Can you point me to the code for the iReport webapp in github? thanks again - Al On Tue, Mar 3, 2015 at 10:13 AM, Chris Hoffman <chris_h@berkeley.edu> wrote: > Hi Al, > > We at UCB are talking with Megan and Richard about contributing some of > the other customizations we have, especially to help set up one of the > community profiles (for herbaria). There are a couple things on the > reporting side that we'd be happy to help you set up. For iReports, we > were frustrated by the inability to allow the user to provide parameters to > the report via the CSpace UI. So we've developed a Django web app that > allows a user to select an iReport and then type in the parameters they > need to query (e.g., a date range, or a scientific name). > > The "bigger" solution is the public portal we have developed, also in > Django. Here's an example: > http://ucjeps.berkeley.edu/specimens/ > > This involves running a query each night that extracts data that can be > loaded as a Solr data source, and then the Django app is a nice search > interface that uses Solr and also points back to CSpace via the API. We've > found this is a powerful tool for more complex (and faster) searches. > There's a "Download CSV" button that people can use as well. > > We've wanted to contribute these to CSpace Core, but have been too busy to > engage on this sufficiently. However, the code is available in github, and > some of it is pretty well documented. We'd be happy to explain it to > anyone interested! And we'd love to treat it as a community resource that > others could help improve. > > Thanks, > Chris > > > On Mar 3, 2015, at 9:59 AM, Al Bersch <abersch@museumca.org> wrote: > > Hello all, > > Here's another question: > > We're trying to figure out the best framework for reporting from CSpace. > Jesse thought that there might be efforts underway to include some of UCB's > reporting webapps in the next release. Does anyone know if that's the case, > and if so, what the plan is? Or, is there a recommended current framework > for reporting? > > Thanks all, > > 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 > > > -- Al Bersch Collections Systems Manager Oakland Museum of California 1000 Oak Street, Oakland, CA 94607 abersch@museumca.org 510-318-8468

Al, The "ireports webapp" may be found at: https://github.com/cspace-deployment/cspace_django_project/tree/master/ireports Note that it is part of a Django "project" (called cspace_django_project) that contains helper code for authenticating with the CSpace server (needed to get access to the reports on the server). There is documentation on customizing and setting up this code at: http://wiki.collectionspace.org/display/deploy/UC+Berkeley+web+applications But note that the documentation is still wet-behind-the-ears and needs to be read with a grain of salt. Do please let me know if I can help you get established with this. Good hunting, John On Tue, Mar 3, 2015 at 11:05 AM, Al Bersch <abersch@museumca.org> wrote: > Hi Chris, > > Thanks for getting back to me, and offering to share/explain your work. > The public portal is great. I know we'd like to implement something similar > for our online collections, eventually. For now, we'd be interested in > looking at the web app for adding parameters to queries in iReport. I think > the first step might be for us to play around with iReport. Let me get back > to you! > > Can you point me to the code for the iReport webapp in github? > > thanks again - > > Al > > On Tue, Mar 3, 2015 at 10:13 AM, Chris Hoffman <chris_h@berkeley.edu> > wrote: > >> Hi Al, >> >> We at UCB are talking with Megan and Richard about contributing some of >> the other customizations we have, especially to help set up one of the >> community profiles (for herbaria). There are a couple things on the >> reporting side that we'd be happy to help you set up. For iReports, we >> were frustrated by the inability to allow the user to provide parameters to >> the report via the CSpace UI. So we've developed a Django web app that >> allows a user to select an iReport and then type in the parameters they >> need to query (e.g., a date range, or a scientific name). >> >> The "bigger" solution is the public portal we have developed, also in >> Django. Here's an example: >> http://ucjeps.berkeley.edu/specimens/ >> >> This involves running a query each night that extracts data that can be >> loaded as a Solr data source, and then the Django app is a nice search >> interface that uses Solr and also points back to CSpace via the API. We've >> found this is a powerful tool for more complex (and faster) searches. >> There's a "Download CSV" button that people can use as well. >> >> We've wanted to contribute these to CSpace Core, but have been too busy >> to engage on this sufficiently. However, the code is available in github, >> and some of it is pretty well documented. We'd be happy to explain it to >> anyone interested! And we'd love to treat it as a community resource that >> others could help improve. >> >> Thanks, >> Chris >> >> >> On Mar 3, 2015, at 9:59 AM, Al Bersch <abersch@museumca.org> wrote: >> >> Hello all, >> >> Here's another question: >> >> We're trying to figure out the best framework for reporting from CSpace. >> Jesse thought that there might be efforts underway to include some of UCB's >> reporting webapps in the next release. Does anyone know if that's the case, >> and if so, what the plan is? Or, is there a recommended current framework >> for reporting? >> >> Thanks all, >> >> 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 >> >> >> > > > -- > 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 > >

Al, You also wish to have a look at the "7 unripe, raw, needy tools" for installing and maintaining these Django webapps and Solr: https://github.com/cspace-deployment/deployandrelease/blob/master/README.md John On Tue, Mar 3, 2015 at 12:13 PM, John B. LOWE <jblowe@berkeley.edu> wrote: > Al, > > The "ireports webapp" may be found at: > > > https://github.com/cspace-deployment/cspace_django_project/tree/master/ireports > > Note that it is part of a Django "project" (called cspace_django_project) > that contains helper code for authenticating with the CSpace server (needed > to get access to the reports on the server). > > There is documentation on customizing and setting up this code at: > > http://wiki.collectionspace.org/display/deploy/UC+Berkeley+web+applications > > But note that the documentation is still wet-behind-the-ears and needs to > be read with a grain of salt. Do please let me know if I can help you get > established with this. > > Good hunting, > > John > > On Tue, Mar 3, 2015 at 11:05 AM, Al Bersch <abersch@museumca.org> wrote: > >> Hi Chris, >> >> Thanks for getting back to me, and offering to share/explain your work. >> The public portal is great. I know we'd like to implement something similar >> for our online collections, eventually. For now, we'd be interested in >> looking at the web app for adding parameters to queries in iReport. I think >> the first step might be for us to play around with iReport. Let me get back >> to you! >> >> Can you point me to the code for the iReport webapp in github? >> >> thanks again - >> >> Al >> >> On Tue, Mar 3, 2015 at 10:13 AM, Chris Hoffman <chris_h@berkeley.edu> >> wrote: >> >>> Hi Al, >>> >>> We at UCB are talking with Megan and Richard about contributing some of >>> the other customizations we have, especially to help set up one of the >>> community profiles (for herbaria). There are a couple things on the >>> reporting side that we'd be happy to help you set up. For iReports, we >>> were frustrated by the inability to allow the user to provide parameters to >>> the report via the CSpace UI. So we've developed a Django web app that >>> allows a user to select an iReport and then type in the parameters they >>> need to query (e.g., a date range, or a scientific name). >>> >>> The "bigger" solution is the public portal we have developed, also in >>> Django. Here's an example: >>> http://ucjeps.berkeley.edu/specimens/ >>> >>> This involves running a query each night that extracts data that can be >>> loaded as a Solr data source, and then the Django app is a nice search >>> interface that uses Solr and also points back to CSpace via the API. We've >>> found this is a powerful tool for more complex (and faster) searches. >>> There's a "Download CSV" button that people can use as well. >>> >>> We've wanted to contribute these to CSpace Core, but have been too busy >>> to engage on this sufficiently. However, the code is available in github, >>> and some of it is pretty well documented. We'd be happy to explain it to >>> anyone interested! And we'd love to treat it as a community resource that >>> others could help improve. >>> >>> Thanks, >>> Chris >>> >>> >>> On Mar 3, 2015, at 9:59 AM, Al Bersch <abersch@museumca.org> wrote: >>> >>> Hello all, >>> >>> Here's another question: >>> >>> We're trying to figure out the best framework for reporting from CSpace. >>> Jesse thought that there might be efforts underway to include some of UCB's >>> reporting webapps in the next release. Does anyone know if that's the case, >>> and if so, what the plan is? Or, is there a recommended current framework >>> for reporting? >>> >>> Thanks all, >>> >>> 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 >>> >>> >>> >> >> >> -- >> 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 >> >> >

On the topic of iReport, just wanted to send out this reminder from Jasper: As of version 5.5.0, Jaspersoft Studio<https://community.jaspersoft.com/project/jaspersoft-studio> will be the official design client for JasperReports. iReport will remain as a supported product in maintenance-only mode until December 31, 2015, meaning we will continue to fix critical defects in upcoming releases but no new features will be added to the iReport client. Continue to maintain your existing reports with the newJaspersoft Studio<https://community.jaspersoft.com/project/jaspersoft-studio>! The program team will include this information in its planning as we talk about incorporating some of the UCB Django framework contributions. Megan Forbes CollectionSpace Community Outreach and Support Manager megan.forbes@lyrasis.org 800.999.8558 x 2917 Main 917.267.9676 Cell meganbforbes Skype ________________________________ From: Talk <talk-bounces@lists.collectionspace.org> on behalf of Al Bersch <abersch@museumca.org> Sent: Tuesday, March 3, 2015 2:05 PM To: Chris Hoffman Cc: talk Subject: Re: [Talk] Reporting Hi Chris, Thanks for getting back to me, and offering to share/explain your work. The public portal is great. I know we'd like to implement something similar for our online collections, eventually. For now, we'd be interested in looking at the web app for adding parameters to queries in iReport. I think the first step might be for us to play around with iReport. Let me get back to you! Can you point me to the code for the iReport webapp in github? thanks again - Al On Tue, Mar 3, 2015 at 10:13 AM, Chris Hoffman <chris_h@berkeley.edu<mailto:chris_h@berkeley.edu>> wrote: Hi Al, We at UCB are talking with Megan and Richard about contributing some of the other customizations we have, especially to help set up one of the community profiles (for herbaria). There are a couple things on the reporting side that we'd be happy to help you set up. For iReports, we were frustrated by the inability to allow the user to provide parameters to the report via the CSpace UI. So we've developed a Django web app that allows a user to select an iReport and then type in the parameters they need to query (e.g., a date range, or a scientific name). The "bigger" solution is the public portal we have developed, also in Django. Here's an example: http://ucjeps.berkeley.edu/specimens/ This involves running a query each night that extracts data that can be loaded as a Solr data source, and then the Django app is a nice search interface that uses Solr and also points back to CSpace via the API. We've found this is a powerful tool for more complex (and faster) searches. There's a "Download CSV" button that people can use as well. We've wanted to contribute these to CSpace Core, but have been too busy to engage on this sufficiently. However, the code is available in github, and some of it is pretty well documented. We'd be happy to explain it to anyone interested! And we'd love to treat it as a community resource that others could help improve. Thanks, Chris On Mar 3, 2015, at 9:59 AM, Al Bersch <abersch@museumca.org<mailto:abersch@museumca.org>> wrote: Hello all, Here's another question: We're trying to figure out the best framework for reporting from CSpace. Jesse thought that there might be efforts underway to include some of UCB's reporting webapps in the next release. Does anyone know if that's the case, and if so, what the plan is? Or, is there a recommended current framework for reporting? Thanks all, 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<tel:510-318-8468> _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto: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<mailto:abersch@museumca.org> 510-318-8468

Al, ...A quick note about the "portals"... The current "generalized web portal" (aka "GWP") code is in part of the PAHMA Django project ("pahma_project"). You can see the code at: https://github.com/cspace-deployment/pahma_project/tree/pahma_4.0-1/search (make sure you look at the pahma_4.0-1 branch -- this is the current development branch and has not yet been merged into master) It's deployed on our Dev servers and you could contact Michael Black about getting access. The code for the UCJEPS portal, which has been operating for over a year now, is at: https://github.com/cspace-deployment/ucjeps_project/tree/rev10/publicsearch It represents an earlier, "uncustomizable" version of the code, but of course you can see it in operation without a password at the link that Chris sent. Cheers, John On Tue, Mar 3, 2015 at 1:08 PM, John B. LOWE <jblowe@berkeley.edu> wrote: > Al, > > You also wish to have a look at the "7 unripe, raw, needy tools" for > installing and maintaining these Django webapps and Solr: > > > https://github.com/cspace-deployment/deployandrelease/blob/master/README.md > > John > > On Tue, Mar 3, 2015 at 12:13 PM, John B. LOWE <jblowe@berkeley.edu> wrote: > >> Al, >> >> The "ireports webapp" may be found at: >> >> >> https://github.com/cspace-deployment/cspace_django_project/tree/master/ireports >> >> Note that it is part of a Django "project" (called cspace_django_project) >> that contains helper code for authenticating with the CSpace server (needed >> to get access to the reports on the server). >> >> There is documentation on customizing and setting up this code at: >> >> >> http://wiki.collectionspace.org/display/deploy/UC+Berkeley+web+applications >> >> But note that the documentation is still wet-behind-the-ears and needs to >> be read with a grain of salt. Do please let me know if I can help you get >> established with this. >> >> Good hunting, >> >> John >> >> On Tue, Mar 3, 2015 at 11:05 AM, Al Bersch <abersch@museumca.org> wrote: >> >>> Hi Chris, >>> >>> Thanks for getting back to me, and offering to share/explain your work. >>> The public portal is great. I know we'd like to implement something similar >>> for our online collections, eventually. For now, we'd be interested in >>> looking at the web app for adding parameters to queries in iReport. I think >>> the first step might be for us to play around with iReport. Let me get back >>> to you! >>> >>> Can you point me to the code for the iReport webapp in github? >>> >>> thanks again - >>> >>> Al >>> >>

Coming back to this, sometime CSpace should be upgraded to use the newer versions of Jaspersoft Studio. Or does CSpace support the newest version? The documentation on the web site at http://wiki.collectionspace.org/display/DOC/How+to+add+and+run+reports says: > Ensure that you get at the minimum the 5.0.1 version, which is known to work with current CollectionSpace services. I was under the impression that we could only write reports in the version of Jaspersoft that matched something on the CollectionSpace server. Thanks, Chris On Mar 4, 2015, at 8:43 AM, Megan Forbes <megan.forbes@lyrasis.org> wrote: > On the topic of iReport, just wanted to send out this reminder from Jasper: > > As of version 5.5.0, Jaspersoft Studio will be the official design client for JasperReports. iReport will remain as a supported product in maintenance-only mode until December 31, 2015, meaning we will continue to fix critical defects in upcoming releases but no new features will be added to the iReport client. Continue to maintain your existing reports with the newJaspersoft Studio! > > The program team will include this information in its planning as we talk about incorporating some of the UCB Django framework contributions. > > Megan Forbes > CollectionSpace Community Outreach and Support Manager > megan.forbes@lyrasis.org > 800.999.8558 x 2917 Main > 917.267.9676 Cell > meganbforbes Skype > > > From: Talk <talk-bounces@lists.collectionspace.org> on behalf of Al Bersch <abersch@museumca.org> > Sent: Tuesday, March 3, 2015 2:05 PM > To: Chris Hoffman > Cc: talk > Subject: Re: [Talk] Reporting > > Hi Chris, > > Thanks for getting back to me, and offering to share/explain your work. The public portal is great. I know we'd like to implement something similar for our online collections, eventually. For now, we'd be interested in looking at the web app for adding parameters to queries in iReport. I think the first step might be for us to play around with iReport. Let me get back to you! > > Can you point me to the code for the iReport webapp in github? > > thanks again - > > Al > > On Tue, Mar 3, 2015 at 10:13 AM, Chris Hoffman <chris_h@berkeley.edu> wrote: > Hi Al, > > We at UCB are talking with Megan and Richard about contributing some of the other customizations we have, especially to help set up one of the community profiles (for herbaria). There are a couple things on the reporting side that we'd be happy to help you set up. For iReports, we were frustrated by the inability to allow the user to provide parameters to the report via the CSpace UI. So we've developed a Django web app that allows a user to select an iReport and then type in the parameters they need to query (e.g., a date range, or a scientific name). > > The "bigger" solution is the public portal we have developed, also in Django. Here's an example: > http://ucjeps.berkeley.edu/specimens/ > > This involves running a query each night that extracts data that can be loaded as a Solr data source, and then the Django app is a nice search interface that uses Solr and also points back to CSpace via the API. We've found this is a powerful tool for more complex (and faster) searches. There's a "Download CSV" button that people can use as well. > > We've wanted to contribute these to CSpace Core, but have been too busy to engage on this sufficiently. However, the code is available in github, and some of it is pretty well documented. We'd be happy to explain it to anyone interested! And we'd love to treat it as a community resource that others could help improve. > > Thanks, > Chris > > > On Mar 3, 2015, at 9:59 AM, Al Bersch <abersch@museumca.org> wrote: > >> Hello all, >> >> Here's another question: >> >> We're trying to figure out the best framework for reporting from CSpace. Jesse thought that there might be efforts underway to include some of UCB's reporting webapps in the next release. Does anyone know if that's the case, and if so, what the plan is? Or, is there a recommended current framework for reporting? >> >> Thanks all, >> >> 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 > > > > > -- > Al Bersch > Collections Systems Manager > Oakland Museum of California > 1000 Oak Street, Oakland, CA 94607 > abersch@museumca.org > 510-318-8468