|
|
This section details the
steps necessary to import a collection of both metadata and content.
The import process will
import the object (metadata + content), create any renditions required, and place
it on the Documentum lifecycle.
Once it’s approved, the
object will be published (via Documentum Site Caching Services).
See the Overview CIS Life Cycle Diagram for
detail.
·
Specify the renditions needed. Sample settings are: 1024, 256 and 64
·
Specify which rendition to be used as
default
·
Specify the next autonumber to be used (# of
digital objects in the collection+ 1)
·
Specify the caption text. Sample caption:
"Digitally
reproduced by USC Digital Archive C2005, First Families Postcards:
[filename]"
where [filename] is the name of the image file.
·
Determine location of staging area for
collection
·
Determine size of collection
·
Currently, CIS has been allocated 25 file systems
with 60GB each.
·
As of May 2005, we are at file system #16.
·
Use the following commands to check size:
df –h
/var/local/documentum/data/cisprod/content_storage_[xx]
where [xx] is the file system #
du –sh <…>/[collection]
·
create location (object: dm_location). DA > admin > storage >
locations
·
create file
storage (object: dm_filestore). DA > admin >
storage > file_storage
·
change directory to virtual staging area
cd
/auto/docu1-02/cismig
where
virtual
staging area is /auto/docu1-02/cismig
and
directory structure of cismig is as followed:
- cismig
|-- [collection]
|------ new
|---------- [batchId] (batchId = date
of staging)
|-------------- [contents …]
|------
replace
·
link to staging area:
ln – s
[actual staging area (see 1b)]
[virtual staging area /collection/{new/batchId/}]
note 1: after import, manually rename directory from <collection> to <collection>_done
to
prevent the import job from picking it up the next time around
note 2: the import job also renames the files in the collection from <filename> to <fileName>_done
note: do not run if other users are updating lifecycle (import jobs, add/modify
objects)
since
UpdateLifeCycle will uninstall all lifecycles in Documentum)
iDQL:
select * from dm_alias_set;
Application
Builder: open USC_CISR2 > view lifecycle > status must be set as “INSTALLED”
iDQL:
create …
·
iDQL: create …
·
sqlplus: select * from derivatives_s;
·
<collection>_digitizer to cismig (CIS
migration user)
·
<collection>_supercataloger to
·
cd /var/local/documentum/dmadmin
·
. ./runimport > ~/logs/[logFileName.log] &
·
tail –f ~/logs/[logFileName.log]
select i_full_format,
page_modifier, count(*) from dmr_content where any parent_id in (select
r_object_id from <CollectionName> where r_is_virtual_doc = 0) group by
i_full_format, page_modifier;
·
Java Project: ImportJob:
-
RequestRend64
-
RequestThumbnail (100)
-
RequestRend256
-
RequestRend1024
-
RequestSid
·
Use the following parameters
-
<docbroker>
<user> <password> <collection> tiff <# of rendition>
-
where
·
docbroker = cisprod
·
user = dmadmin
·
# of renditions = total number of renditions
tiff
64
thumbnail
256
1024
sid
·
Login to docu1 as dmadmin
·
Run
-
. ./runtextrend > logs/<filename>