I am relatively new to Zope, but I plan to use it for an image database system that I need to make for scientific purposes. What I have in mind is to store the actual images externally in files (since there will be many and large files), and the info about the image (where collected, owner, codes etc etc) in a database like MySQL. Zope would form the interface. My first question is what would be a suitable way to go from here: use LocalFS or ExtImage for storage of many files (think of 50,000 or so)? I will need to be able to differentiate between users: ie not every user should have access to all files. Furthermore: if there are people that have already done something similar I would appreciate to learn from their experience. Through a web search I haven't been able to find such projects, at least not based on Zope. All best, Gabriel
On Tue, Nov 05, 2002 at 04:24:05PM -0500, gabecker@indiana.edu wrote:
Furthermore: if there are people that have already done something similar I would appreciate to learn from their experience. Through a web search I haven't been able to find such projects, at least not based on Zope.
No idea if they'd be willing to share information with you, but the Space Telescope Science Institute (renowned for the Hubble Space Telescope) use Zope and they handle large images. -- Martijn Pieters | Software Engineer mailto:mj@zope.com | Zope Corporation http://www.zope.com/ | Creators of Zope http://www.zope.org/ ---------------------------------------------
On Tue, Nov 05, 2002 at 04:43:51PM -0500, Martijn Pieters wrote:
On Tue, Nov 05, 2002 at 04:24:05PM -0500, gabecker@indiana.edu wrote:
Furthermore: if there are people that have already done something similar I would appreciate to learn from their experience. Through a web search I haven't been able to find such projects, at least not based on Zope.
No idea if they'd be willing to share information with you, but the Space Telescope Science Institute (renowned for the Hubble Space Telescope) use Zope and they handle large images.
Sorry, I ment to include a URL: http://www.stsci.edu -- Martijn Pieters | Software Engineer mailto:mj@zope.com | Zope Corporation http://www.zope.com/ | Creators of Zope http://www.zope.org/ ---------------------------------------------
I'll probably get shot for this, but a pure filesystem and MySQL implementation is better suited for PHP. If say, you wanted to store the image info in the ZODB, and the data elsewhere, then Zope is a good solution. Another nice thing about Zope you don't get with a language like PHP is much better managability of the presentation code. If that's important, then again, Zope is the way to go. -jim ----- Original Message ----- From: <gabecker@indiana.edu> To: <zope@zope.org> Sent: Tuesday, November 05, 2002 4:24 PM Subject: [Zope] advice needed
I am relatively new to Zope, but I plan to use it for an image database system that I need to make for scientific purposes. What I have in mind is to store the actual images externally in files (since there will be many and large files), and the info about the image (where collected, owner, codes etc etc) in a database like MySQL. Zope would form the interface.
My first question is what would be a suitable way to go from here: use LocalFS or ExtImage for storage of many files (think of 50,000 or so)? I will need to be able to differentiate between users: ie not every user should have access to all files.
Furthermore: if there are people that have already done something similar I would appreciate to learn from their experience. Through a web search I haven't been able to find such projects, at least not based on Zope.
All best, Gabriel
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Have you thought about storing the images as BLOBs in MySQL? I must admit I lack every experience how MySQL behaves under the load of many Long Objects, but in a small scale I've made good experiences till now with that (the concerning small application will go online the next days). Concerning the access restrictions, IMHO this would be handled the easiest way by roles and (in case of externel files or ZODB storage) different folders, if your special problem admits such an architecture. Martin gabecker@indiana.edu schrieb:
I am relatively new to Zope, but I plan to use it for an image database system that I need to make for scientific purposes. What I have in mind is to store the actual images externally in files (since there will be many and large files), and the info about the image (where collected, owner, codes etc etc) in a database like MySQL. Zope would form the interface.
My first question is what would be a suitable way to go from here: use LocalFS or ExtImage for storage of many files (think of 50,000 or so)? I will need to be able to differentiate between users: ie not every user should have access to all files.
Furthermore: if there are people that have already done something similar I would appreciate to learn from their experience. Through a web search I haven't been able to find such projects, at least not based on Zope.
All best, Gabriel
gabecker@indiana.edu writes:
I am relatively new to Zope, but I plan to use it for an image database system that I need to make for scientific purposes. What I have in mind is to store the actual images externally in files (since there will be many and large files), and the info about the image (where collected, owner, codes etc etc) in a database like MySQL. Zope would form the interface. Good!
My first question is what would be a suitable way to go from here: use LocalFS or ExtImage for storage of many files (think of 50,000 or so)? I will need to be able to differentiate between users: ie not every user should have access to all files. We went for "ExtImage" and up to now made good experience.
Dieter
participants (5)
-
Dieter Maurer -
gabecker＠indiana.edu -
Jim Kutter -
Martijn Pieters -
Martin Gebert