Embedding Graphics in Jaspersoft Report Files

One of the features of Jaspersoft Reports is the ability to include static graphics — logos, for instance — in the completed reports. These graphic files are normally listed in the JRXML configuration file by reference — meaning that what is stored in the configuration is a file name and not the graphic itself. Most times the configuration file and the ancillary graphics files are uploaded to a JasperReports Server for execution. In the environment that I’m working in, CollectionSpace, the report generator is embedded in the application without the JasperReports Server endpoint. The JRXML files must be compiled into the application, which makes keeping track of the ancillary graphics files somewhat troublesome.

Ideally, I would like to embed the graphics into the JRXML file itself, similar to what is done in with the data URI schema in HTML and CSS files to reduce the connection latency between client and server. This is possible, but the instructions and hints you find out on the internet to do it are out of date or incomplete. The instructions below are correct for Jaspersoft Studio version 6.2.0.

Separating Configuration from Code in CollectionSpace

For the past few months I’ve been working on a project to migrate a museum’s collection registry to CollectionSpace. CollectionSpace is a “free, open-source, web-based software application for the description, management, and dissemination of museum collections information.”1 CollectionSpace is multitenant software — one installation of the software can serve many tenants. The software package’s structure, though, means that the configuration for one tenant is mixed in with the code for all tenants on the server (e.g, the application layer, services layer, and user interface layer configuration are stored deep in the source code tree). This bothers me from a maintainability standpoint. Sure, Git’s richly featured merge functionality helps, but it seems unnecessarily complex to intertwine the two in this way. So I developed a structure that puts a tenant’s configuration in a separate source code repository and a series of procedures to bring the two together at application-build time.

Footnotes

  1. From the answer to the first question of the CollectionSpace frequently asked questions. []

The Who, What, When, Where and Why of Library Discovery (text as intended for presentation)


Me and my Jester's Cap


Last week I was at the NISO Forum: The Future of Library Resource Discovery with a great group of colleagues as we challenged ourselves to think about the role of discovery services in the information-seeking habits of our patrons. In the closing keynote, I was projecting what library resource discovery interface might look like five years from now, and I was weaving in comments and ideas that had bubbled up in the in-person conversation and the Twitter channel. And yes, I did wear a jester’s cap for the presentation.

Included below is the text of the presentation as intended to be given on October 6, 2015, at the Mt. Washington Conference Center in Baltimore, Maryland. (I did stray from the text in a few places, but not in any significant way.) At the bottom is a postscript based on a conversation I had afterwards about the role of mobile devices in library resource discovery.

Registration Now Open for a Fall Forum on the Future of Library Discovery

Helping patrons find the information they need is an important part of the library profession, and in the past decade the profession has seen the rise of dedicated “discovery systems” to address that need. The National Information Standards Organization (NISO) is active at the intersection of libraries, content suppliers, and service providers in smoothing out the wrinkles between these parties:

Announcing “The Future of Library Resource Discovery” — a NISO Two-day Forum in October in Baltimore

Cover page from the NISO white paper "The Future of Library Resource Discovery"

Cover page from the NISO white paper “The Future of Library Resource Discovery”


In early October, NISO will be hosting a two-day forum on the future of resource discovery in libraries. This is an in-person meeting to extend the work of Marshall Breeding’s paper on the same topic that was published earlier this year:

  • Full paper, PDF, 53 pages
  • Summary from Information Standards Quarterly, Spring 2015, 27(1): pp. 24-30.

Thursday Threads: Battles over strong encryption, IPv4 addresses exhausted while IPv6 surges

Receive DLTJ Thursday Threads:

by E-mail

by RSS

Delivered by FeedBurner

Two articles in each of two threads this week:

Feel free to send this to others you think might be interested in the topics. If you find these threads interesting and useful, you might want to add the Thursday Threads RSS Feed to your feed reader or subscribe to e-mail delivery using the form to the right. If you would like a more raw and immediate version of these types of stories, watch my Pinboard bookmarks (or subscribe to its feed in your feed reader). Items posted to are also sent out as tweets; you can follow me on Twitter. Comments and tips, as always, are welcome.

Thursday Threads: New and Interesting from ALA Exhibits

Receive DLTJ Thursday Threads:

by E-mail

by RSS

Delivered by FeedBurner

I’m just home from the American Library Association meeting in San Francisco, so this week’s threads are just a brief view of new and interesting things I found on the exhibit floor.

NOTE! Funding for my current position at LYRASIS ran out at the end of June, so I am looking for new opportunities and challenges for my skills. Check out my resume/c.v. and please let me know of job opportunities in library technology, open source, and/or community engagement.

Thursday Threads: Data Management Plans, Better Q/A Sessions, App for Bird Identification

Receive DLTJ Thursday Threads:

by E-mail

by RSS

Delivered by FeedBurner

This week’s threads:

NOTE! Funding for my current position at LYRASIS runs out at the end of June, so I am looking for new opportunities and challenges for my skills. Check out my resume/c.v. and please let me know of job opportunities in library technology, open source, and/or community engagement.

Changes to “Emanuel African Methodist Episcopal Church” Wikipedia Page, Visualized

Edited after initial publication to add: My thoughts are with the people in and around Charleston, South Carolina, this evening. What is making it out of the media fog to me tonight is your compassion for each other. Please be well as you absorb, internalize, and recover from this shocking display of inhumanity. 

This afternoon, Ed Summers tweeted:

Thursday Threads: Let’s Encrypt is coming, Businesses want you coming to the office, OR2015 Summary

Receive DLTJ Thursday Threads:

by E-mail

by RSS

Delivered by FeedBurner

This week’s threads: