You can import an existing eCTD into an application and give it a new sequence or assembly prefix.
When performing an import of an existing eCTD, the import progress is reported in the
server.log file. The
Job Request Details also show messages about each sequence that is imported. The administrator can monitor the server log to follow the overall progress of the import and see more detailed messages, such as timestamps and Oracle information.
To import an eCTD application:
-
Click a link for the application into which you want to import an eCTD application.
The
Application Attributes page opens.
-
Click
to open the
Import eCTD to Application window.
-
Click
Browse, locate and select the eCTD application folder to import, then click
OK.
-
In the
Sequence Name Prefix
box, enter a prefix to use for sequences.
-
In the
Assembly Name Prefix
box, enter a prefix to use for the assembly name.
- To import only XML leafs found in the eCTD XML, without importing references to the content files, select
Import Leaf Elements Only. This prevents
Calyx RIM from creating and assigning content document elements below each leaf during the import. It can also improve import speed significantly, as the content files are not necessary for subsequent sequence publishing. This option captures all lifecycle operations correctly, and it prevents republishing of submissions already published. If extracts and renditions are needed for the imported documents, you can run create renditions and extractions from each assembly.
- To include orphan leaf elements in the import, select the
Import Orphan Leaf Elements
option. This informs the
Calyx RIM system that some of the eCTD XML could be incorrect in that it might contain references to leaf IDs or files that do not exist in the current view of the application. This can occur, for example, if an identical leaf is replaced twice, or if a deleted leaf is replaced. During a normal import,
Calyx RIM fails when it finds these instances. However, if the Import Orphan Leaf Elements checkbox is selected,
Calyx RIM ignores orphan leaf instances and creates new leaf elements instead.
- Automatically, each imported leaf element is assigned with the
Published leaf status, or any other leaf status that has the
Internal System Status set to
"PUBLISHED".
-
Click
Next.
The
Summary page indicates the import has been scheduled.
-
Click
Finish.
For performance reasons, the status of the import is logged to the
server.log file on the Application server (rather than to the job requests).