My files are not being captured by SDMS with Per-File Templates - WKB2209
Article number: 2209
SYMPTOMS
- Files were placed in a scan path (ex:\\server1\shareddata \) for archiving by NuGenesis, but the files are not visible in WebVision
ENVIRONMENT
- NuGenesis 8 SDMS
- A file capture template line is configured with the "NuGenesis Per-File Template" (PFT) data adapter
- NOT to be confused with Per-Folder Templates, which is a different data adapter and beyond the scope of this article
CAUSE
The most common reason for per-file template files not being archived is that the companion file (*.nga) is missing or is not a valid XML file.
FIX or WORKAROUND
- Ensure that the files meet the basic archive criteria, as discussed in the article "My files are not being captured by SDMS".
- Each file to be captured with Per-File Templates must have a companion file with the file extension NGA. For example, for the file data1.esd, the companion file name is data1.esd.nga, and both files must exist in the scan path, in the same folder, for the files to be archived.
- SDMS does not build the NGA files. They must be built either by hand or by software, and they must conform to the XML Document Type Definition as specified in the NuGenesis LMS SDMS Data Adapters Release 2 Reference Guide section 13.7.
- The NGA files' encodings must match the file encoding declaration in the XML. If the file's XML specifies UTF-8 encoding and the file is saved in ASCII or UTF-16 encoding, the file cannot be parsed and the metadata will not be extracted.
- The XML specifies the full path to the DTD file. Ensure that the DTD file is in a network path that is accessible to the NuGenesis file Capture server.
ADDITIONAL INFORMATION
Per-File Template lines are most commonly used when file data must be captured by SDMS, with custom metadata tags, but SDMS does not have a Data Adapter available for the software product.
id2209, SDMS, SDMS8, SDMS8NU, SUPISDMS, SUPNG