Whoo-ee! The previous News posting was about some great new upgrades in devlopment for LIDA, and this posting is even more new stuff on the way! Well, actually one new stuff. (Can “stuff” be singular? You can have “oodles” of something, but can you have just one oodle?)
The previous post (Jan. 22) was about LISTs filtering and creating New Blank data files, both of which are exciting upgrades.
This post is about a concept “only” about 85% certain that it will make it into LIDA; much will depend on the reaction of our Beta Test team to the idea.
THE BACKGROUND: Several different testers have asked if it would be possible to add various different kinds of files into LIDA. Some have asked for the ability to include program notes, some have asked if it would be possible to include images, such as a JPG of the cover page of a listing, some have asked if we could include Word documents or PDF files.
Initially, I was reluctant to include any of these in the LIDA Data File for two main reasons. First, it would require a major restructuring of the data file, and at this point that could become a huge hassle. But more concerning would be the fact that doing this would increase the size of the data file manyfold.
Those of you who have helped with the beta test have noted that our test file (which is an import of a live file from someone who manages a music library) has more than 23,000 records in it. Can you imagine the size of the data file if we were to include a JPG image of the cover sheet of each listing, with that file being anywere between 300k and 5MB in size?Both of these considerations made me very reluctant to jump into this as an upgrade to LIDA.
HOWEVER, the idea machine has struck again! Most people (everyone?) who wants to include these items in LIDA already has them in their file system.
Some of you know I also build websites. These days, I build most sites using WordPress, and the way WordPress handles embedded media (such as exactly what we’re talking about here) is they do NOT put this media into their database; they simply store it in its regular file format, then reference it when they need it.
So why can’t LIDA do the same thing?
Yep. That was the light bulb that came on when the idea factory went into action.
Instead of storing all these media files inside LIDA, why can’t we just store REFERENCES to those files?
I believe we can.
This concept definitely bears more concept development, and could certainly use some discussion among the beta test team, but for now, it sounds like we are definitely looking in the right neighborhood.I’m going to let the idea (and the discussion) percolate for a few days while I finish up the previous two upgrades mentioned, then we will see about making this happen.
As always, please give us feedback below on your thoughts on this concept.