Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
One of the new ACRL statistics we need to gather for our library
digitization archives is the size of the overall collection(s). I
couldn't seem to find this statistic readily available without going to
each item record, noting the file size, adding them all up, and
converting to Mb (because many are in Kb). Surely, there's an easier way
and I just missed it . . . anybody?
*Kelley A. Weber* *Mabee
Library, Washburn University*
Business Librarian 1700 SW
Reference/Instruction Librarian Topeka, KS 66621
Institutional Repository Librarian 785/670-1503
Please consider the environment before printing
From: Dorothea Salo <dorothea.salo@gm...> - 2009-09-17 15:40:23
2009/9/17 Kelley Weber <kelley.weber@...>:
> One of the new ACRL statistics we need to gather for our library
> digitization archives is the size of the overall collection(s). I couldn't
> seem to find this statistic readily available without going to each item
> record, noting the file size, adding them all up, and converting to Mb
> (because many are in Kb). Surely, there's an easier way and I just missed it
> . . . anybody?
When I had to work this out for the same reason last year, I gave ARL
the size of the assetstore directory on the server. If I'd wanted to
be persnickety, I'd have thrown in the size of the database as well,
but that probably doesn't amount to much more than a rounding error.
The "du" command is what to start with, but I don't recall offhand
what flags to use. "man du" should help sort it out.
Dorothea Salo dsalo@...
Digital Repository Librarian AIM: mindsatuw
University of Wisconsin
Rm 218, Memorial Library
The used space in the assetstore will come close, but will also
include extracted plain text, thumbnails, deletia, workspace, etc.
'du' may be including the sizes of the directories too.
Maybe something like this:
JOIN bundle2bitstream USING (bitstream_id)
JOIN item2bundle USING (bundle_id)
JOIN item USING (item_id)
WHERE bundle_id IN (SELECT bundle_id FROM bundle WHERE name = 'ORIGINAL')
AND NOT withdrawn;
But that could be broken by schema changes some day (for example,
Mark H. Wood, Lead System Programmer mwood@...
Friends don't let friends publish revisable-form documents.