talk@lists.collectionspace.org
WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsbinary storage
Hi everybody,
On our new (and functional!) CSpace install, I'm starting to get information entered. I uploaded a PDF scan of a document as a Media Handling record. I notice that it's being stored in apache-tomcat-7.0.57/temp/[long hex code]/filename.pdf
Is this normal? Documentation suggests it should be in a different place.
Eric Ray
Curator of Collections and Exhibits
Museum of the Coastal Bend at Victoria College
2200 E. Red River, Victoria, TX 77901
361-572-6468 | eric.ray@victoriacollege.edumailto:eric.ray@victoriacollege.edu
Eric,
The file you're seeing in apache-tomcat-7.0.57/temp is just a temporary copy of the file and can be removed. The real storage location is in the apache-tomcat-7.0.57/nuxeo-server/data directory. Inside the data directory, you'll see a set of folders/directories for each tenant. Inside each of those folders is another "data" directory.
An MD5 hash of the file is used as the basis for the final location which is two directory levels deep. The highest level directory is named using the first two hexadecimal digits of the MD5 hash and the lowest (second) level directory is named using the 2nd and 3rd hexadecimal digits of the hash.
This technique vastly reduces the chance of a duplicate copy of a binary from ever being stored.
-Richard
From: Talk talk-bounces@lists.collectionspace.org on behalf of RAY, Eric Eric.Ray@victoriacollege.edu
Sent: Tuesday, May 10, 2016 10:12 AM
To: talk@lists.collectionspace.org
Subject: [Talk] binary storage
Hi everybody,
On our new (and functional!) CSpace install, I'm starting to get information entered. I uploaded a PDF scan of a document as a Media Handling record. I notice that it's being stored in apache-tomcat-7.0.57/temp/[long hex code]/filename.pdf
Is this normal? Documentation suggests it should be in a different place.
Eric Ray
Curator of Collections and Exhibits
Museum of the Coastal Bend at Victoria College
2200 E. Red River, Victoria, TX 77901
361-572-6468 | eric.ray@victoriacollege.edumailto:eric.ray@victoriacollege.edu
That's what I was led to believe as well, but my nuxeo-server/data folder doesn't have a sub directory for my active tenant, just for default/fcart/lifesci_domain.
When I try find $CSPACE_JEESERVER_HOME -name *.pdf , all I get is the PDF in the temp directory, and three unrelated PDFs in cspace/config and webapps/docs
From: Richard Millet [mailto:richard.millet@lyrasis.org]
Sent: Tuesday, May 10, 2016 12:25 PM
To: RAY, Eric Eric.Ray@victoriacollege.edu
Cc: talk@lists.collectionspace.org
Subject: Re: binary storage
Eric,
The file you're seeing in apache-tomcat-7.0.57/temp is just a temporary copy of the file and can be removed. The real storage location is in the apache-tomcat-7.0.57/nuxeo-server/data directory. Inside the data directory, you'll see a set of folders/directories for each tenant. Inside each of those folders is another "data" directory.
An MD5 hash of the file is used as the basis for the final location which is two directory levels deep. The highest level directory is named using the first two hexadecimal digits of the MD5 hash and the lowest (second) level directory is named using the 2nd and 3rd hexadecimal digits of the hash.
This technique vastly reduces the chance of a duplicate copy of a binary from ever being stored.
-Richard
From: Talk <talk-bounces@lists.collectionspace.orgmailto:talk-bounces@lists.collectionspace.org> on behalf of RAY, Eric <Eric.Ray@victoriacollege.edumailto:Eric.Ray@victoriacollege.edu>
Sent: Tuesday, May 10, 2016 10:12 AM
To: talk@lists.collectionspace.orgmailto:talk@lists.collectionspace.org
Subject: [Talk] binary storage
Hi everybody,
On our new (and functional!) CSpace install, I'm starting to get information entered. I uploaded a PDF scan of a document as a Media Handling record. I notice that it's being stored in apache-tomcat-7.0.57/temp/[long hex code]/filename.pdf
Is this normal? Documentation suggests it should be in a different place.
Eric Ray
Curator of Collections and Exhibits
Museum of the Coastal Bend at Victoria College
2200 E. Red River, Victoria, TX 77901
361-572-6468 | eric.ray@victoriacollege.edumailto:eric.ray@victoriacollege.edu
It won't be saved with a PDF extension. Instead, the file name is the MD5 hash. If you want to access the file directly, you can make a copy of it and rename it. Otherwise, you can get the file from the CollectionSpace web app or by using the RESTFul API.
From: RAY, Eric Eric.Ray@victoriacollege.edu
Sent: Tuesday, May 10, 2016 10:28 AM
To: Richard Millet
Cc: talk@lists.collectionspace.org
Subject: RE: binary storage
That's what I was led to believe as well, but my nuxeo-server/data folder doesn't have a sub directory for my active tenant, just for default/fcart/lifesci_domain.
When I try find $CSPACE_JEESERVER_HOME -name *.pdf , all I get is the PDF in the temp directory, and three unrelated PDFs in cspace/config and webapps/docs
From: Richard Millet [mailto:richard.millet@lyrasis.org]
Sent: Tuesday, May 10, 2016 12:25 PM
To: RAY, Eric Eric.Ray@victoriacollege.edu
Cc: talk@lists.collectionspace.org
Subject: Re: binary storage
Eric,
The file you're seeing in apache-tomcat-7.0.57/temp is just a temporary copy of the file and can be removed. The real storage location is in the apache-tomcat-7.0.57/nuxeo-server/data directory. Inside the data directory, you'll see a set of folders/directories for each tenant. Inside each of those folders is another "data" directory.
An MD5 hash of the file is used as the basis for the final location which is two directory levels deep. The highest level directory is named using the first two hexadecimal digits of the MD5 hash and the lowest (second) level directory is named using the 2nd and 3rd hexadecimal digits of the hash.
This technique vastly reduces the chance of a duplicate copy of a binary from ever being stored.
-Richard
From: Talk <talk-bounces@lists.collectionspace.orgmailto:talk-bounces@lists.collectionspace.org> on behalf of RAY, Eric <Eric.Ray@victoriacollege.edumailto:Eric.Ray@victoriacollege.edu>
Sent: Tuesday, May 10, 2016 10:12 AM
To: talk@lists.collectionspace.orgmailto:talk@lists.collectionspace.org
Subject: [Talk] binary storage
Hi everybody,
On our new (and functional!) CSpace install, I'm starting to get information entered. I uploaded a PDF scan of a document as a Media Handling record. I notice that it's being stored in apache-tomcat-7.0.57/temp/[long hex code]/filename.pdf
Is this normal? Documentation suggests it should be in a different place.
Eric Ray
Curator of Collections and Exhibits
Museum of the Coastal Bend at Victoria College
2200 E. Red River, Victoria, TX 77901
361-572-6468 | eric.ray@victoriacollege.edumailto:eric.ray@victoriacollege.edu
Ok, thanks for that - it appears my binaries are being stored in the default folder rather than a separate folder for my tenant. I'm OK with that now that I know where they live. Thanks!
From: Richard Millet [mailto:richard.millet@lyrasis.org]
Sent: Tuesday, May 10, 2016 12:31 PM
To: RAY, Eric Eric.Ray@victoriacollege.edu
Cc: talk@lists.collectionspace.org
Subject: Re: binary storage
It won't be saved with a PDF extension. Instead, the file name is the MD5 hash. If you want to access the file directly, you can make a copy of it and rename it. Otherwise, you can get the file from the CollectionSpace web app or by using the RESTFul API.
From: RAY, Eric <Eric.Ray@victoriacollege.edumailto:Eric.Ray@victoriacollege.edu>
Sent: Tuesday, May 10, 2016 10:28 AM
To: Richard Millet
Cc: talk@lists.collectionspace.orgmailto:talk@lists.collectionspace.org
Subject: RE: binary storage
That's what I was led to believe as well, but my nuxeo-server/data folder doesn't have a sub directory for my active tenant, just for default/fcart/lifesci_domain.
When I try find $CSPACE_JEESERVER_HOME -name *.pdf , all I get is the PDF in the temp directory, and three unrelated PDFs in cspace/config and webapps/docs
From: Richard Millet [mailto:richard.millet@lyrasis.org]
Sent: Tuesday, May 10, 2016 12:25 PM
To: RAY, Eric <Eric.Ray@victoriacollege.edumailto:Eric.Ray@victoriacollege.edu>
Cc: talk@lists.collectionspace.orgmailto:talk@lists.collectionspace.org
Subject: Re: binary storage
Eric,
The file you're seeing in apache-tomcat-7.0.57/temp is just a temporary copy of the file and can be removed. The real storage location is in the apache-tomcat-7.0.57/nuxeo-server/data directory. Inside the data directory, you'll see a set of folders/directories for each tenant. Inside each of those folders is another "data" directory.
An MD5 hash of the file is used as the basis for the final location which is two directory levels deep. The highest level directory is named using the first two hexadecimal digits of the MD5 hash and the lowest (second) level directory is named using the 2nd and 3rd hexadecimal digits of the hash.
This technique vastly reduces the chance of a duplicate copy of a binary from ever being stored.
-Richard
From: Talk <talk-bounces@lists.collectionspace.orgmailto:talk-bounces@lists.collectionspace.org> on behalf of RAY, Eric <Eric.Ray@victoriacollege.edumailto:Eric.Ray@victoriacollege.edu>
Sent: Tuesday, May 10, 2016 10:12 AM
To: talk@lists.collectionspace.orgmailto:talk@lists.collectionspace.org
Subject: [Talk] binary storage
Hi everybody,
On our new (and functional!) CSpace install, I'm starting to get information entered. I uploaded a PDF scan of a document as a Media Handling record. I notice that it's being stored in apache-tomcat-7.0.57/temp/[long hex code]/filename.pdf
Is this normal? Documentation suggests it should be in a different place.
Eric Ray
Curator of Collections and Exhibits
Museum of the Coastal Bend at Victoria College
2200 E. Red River, Victoria, TX 77901
361-572-6468 | eric.ray@victoriacollege.edumailto:eric.ray@victoriacollege.edu