Loading decisions
When loading digital objects, the following issues need to be addressed as part of the load process:
Where are the digital objects found?
Can the database access them? (security)
Is there sufficient storage to handle them?
If archiving is enabled, is there sufficient storage for the archives?
Will there be different types of digital objects (audio, video, images, documents)?
For each type, what are the processing rules? (watermark, cropping, rotation)
For each type, what derivatives are needed?
For the processing, which server should it be performed?
If the digital objects are loaded singularly, how long will the load take to run? Will it run in a realistic time frame?
Should the load be broken up into separate tasks, which can be run independently and in parallel?
Are the digital objects going to be stored in the database or kept in the filesystem?
Depending on what the objectives are for having the digital object determines the answers to the previous questions. This, in turn, impacts...
