evergreen-reports:meetings:2011-10-12
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
evergreen-reports:meetings:2011-10-12 [2011/11/02 10:34] – [II. Review and approval of Aug. Minutes] jturner | evergreen-reports:meetings:2011-10-12 [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 15: | Line 15: | ||
==== III. Old Business and updates ==== | ==== III. Old Business and updates ==== | ||
+ | **1. PINES/GPLS Reports RFP update, if any** | ||
+ | * PINES has met with Emerald Data Networks, who will be developing the reports interface. | ||
+ | * Everything is at an early info-gathering stage | ||
+ | * PINES folks will be developing use case scenarios; Cristine will be working on this committee | ||
+ | * The plan is to get use case scenarios and functional requirements together by the end of Dec; development will begin in Jan; first interface review in Feb. The second formal review is planned for May with completion by Sept. 30. | ||
+ | * From a PINES email regarding this project: "This project will involve the design and development of a new interface for Evergreen reports. | ||
+ | * The interface will be developed specifically to PINES requirements, | ||
+ | * given the complexity of the underlying database schema, streamlining the interface would be a challenge. | ||
+ | * We will keep this on the agenda for future meetings to see how development proceeds. | ||
- | 1. PINES/GPLS Reports RFP update, if any | ||
- | 2. Documentation | + | **2. Documentation** |
* Please review what exists and submit what is needed to Jenny (jennifer.turner(at)mnsu.edu) | * Please review what exists and submit what is needed to Jenny (jennifer.turner(at)mnsu.edu) | ||
* Jeff Godin and jasperreports | * Jeff Godin and jasperreports | ||
- | | + | * Jeff has been experimenting with JasperReports and JasperServer as an alternative front end for Evergreen |
- | * Anything else from past meetings? | + | * TADL will be using it internally for most/all of their Evergreen reporting. It eliminates a lot of post-processing of report output. |
- | 3. New Business | + | * Hoping to have an external demo site up soon! In addition to a demo system to poke at, some sample report output might be of use. Screencasts might also be helpful. |
+ | * TADL is focusing on designing reports to meet their needs first, but with an eye toward what would need to take place for someone to make this work in an environment where not everyone has access to every report / bit of data, etc. | ||
+ | * Cristina still to add reports documentation to the Evergreen Community wiki page. | ||
- | 4. Format of future meetings: IRC, Adobe Connect, other? | + | **3. Evergreen reports training pre- or post-conference at Evergreen Annual Conference** |
+ | |||
+ | * Nothing new; at the last update, we were on the market for someone to run the training and to find out whether there' | ||
+ | * It would also be great to see a demo of what Jeff has been doing with Jasperreports. | ||
+ | |||
+ | **4. Anything else from past meetings? | ||
+ | |||
+ | * Nothing. | ||
+ | |||
+ | ==== New Business ==== | ||
+ | |||
+ | * Format of future meetings: IRC, Adobe Connect, other? | ||
==== Next meeting: November 9, 2011 ==== | ==== Next meeting: November 9, 2011 ==== |
evergreen-reports/meetings/2011-10-12.1320244477.txt.gz · Last modified: 2022/02/10 13:33 (external edit)