Actually, without having run any of the helper scripts, an initial deposit in 
DSpace leaves in the assetstore a bitstream for the file and the accompanying 
license.

-- Van Ly 

dspace=> select * from bitstream;
 bitstream_id | bitstream_format_id |                name                | 
size_bytes |             checksum             | checksum_algorithm | 
description | user_format_description |                            source       
                      |               internal_id               | deleted | 
store_number | sequence_id 
--------------+---------------------+------------------------------------+------------+----------------------------------+--------------------+-------------+-------------------------+---------------------------------------------------------------+-----------------------------------------+---------+--------------+-------------
            1 |                   3 | Dspace-architecture-whitepaper.pdf |     
109472 | 3a4d1f4beb72d526852b994785c2f087 | MD5                |             |  
                       | 
/common/dspace-data/upload/Dspace-architecture-whitepaper.pdf | 
115815019145092108673282291954599930771 | f       |            0 |           1
            2 |                   2 | license.txt                        |      
   90 | fdc1c5203350a12ba913209150953506 | MD5                |             |   
                      | Written by org.dspace.content.Item                      
      | 86990559682600625622922454764247047595  | f       |            0 |      
     2
(2 rows)


-----Original Message-----
From: Van Ly
Sent: Thu 28/05/2009 10:30 AM
To: Stuart Lewis
Cc: DSpace-tech@lists.sourceforge.net
Subject: RE: [Dspace-tech] archive_directory & assetstore growth
 

> (Also, the asset store contains the extracted text copies of files you
> uploaded, but I wouldn't expect them to take up 3x the size of your
> new files).

A single document in the assetstore, the `DSpace Architectural
Futures: A White Paper' looks as follows #0, interestingly....the extracted 
text copy occupies less than ten percent of the original.

Thanks.

-- Van Ly

-- #0 --

[r...@dabih dspace-data]# tree assetstore
assetstore
|-- 11
|   `-- 58
|       `-- 15
|           `-- 115815019145092108673282291954599930771
`-- 86
    `-- 99
        `-- 05
            `-- 86990559682600625622922454764247047595

[r...@dabih dspace-data]# find assetstore |xargs file
assetstore:                                                  directory
assetstore/11:                                               directory
assetstore/11/58:                                            directory
assetstore/11/58/15:                                         directory
assetstore/11/58/15/115815019145092108673282291954599930771: PDF document, vers\
ion 1.3
assetstore/86:                                               directory
assetstore/86/99:                                            directory
assetstore/86/99/05:                                         directory
assetstore/86/99/05/86990559682600625622922454764247047595:  ASCII text

[r...@dabih dspace-data]# find assetstore -type f |xargs ls -h --size
116K assetstore/11/58/15/115815019145092108673282291954599930771  \
8.0K assetstore/86/99/05/86990559682600625622922454764247047595



-----Original Message-----
From: Stuart Lewis [mailto:s.le...@auckland.ac.nz]
Sent: Tue 26/05/2009 6:36 PM
To: Van Ly
Subject: RE: [Dspace-tech] archive_directory & assetstore growth
 
Hi Van Ly,
 
Have you tried running [dspace]/bin/cleanup to get rid of old stale bitstreams? 
 
(Also, the asset store contains the extracted text copies of files you 
uploaded, but I wouldn't expect them to take up 3x the size of your new files).
 
Cheers,
 
 
Stuart

________________________________

From: Van Ly [mailto:v...@library.usyd.edu.au]
Sent: Tue 26/05/2009 19:55
To: DSpace-tech@lists.sourceforge.net
Subject: [Dspace-tech] archive_directory & assetstore growth




Hi,

At the moment, I've an archive_directory of 51Gb occupying 89Gb of assetstore 
in DSpace.

The archive_directory is like the one shown in

 dspace-1.4.2-source/docs/application.html#itemimporter

and is a copy of all packages successfully imported in 1.4.2 DSpace with 8.1 
Postgresql.

When the archive_directory grew from 50-51Gb, that 1Gb difference grew the 
DSpace assetstore by 4Gb, is that supposed to happen? or are failed import 
attempts (and retries) responsible for leaving clutter in the assetstore? or 
are package replacement operations (and many repeats) responsible for leaving 
earlier duplicate copies of bitstreams behind?

I was expecting a successful 1Gb feed to DSpace would grow the assetstore by 
about 1Gb plus & minus a little bit.

Any `clue' is much appreciated.

-- Van Ly




------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to