Log Derived File
encode_log_derived_fileLog files derived from ENCODE data to create provenance records linking back to source experiments or files. Track data transformations by recording file path, source accessions, and tools used.
Instructions
Log a file you've derived from ENCODE data for provenance tracking.
Use this when you create new files from ENCODE data (e.g., running a pipeline, filtering peaks, merging samples). This creates a provenance record linking your derived file back to the original ENCODE source data.
WHEN TO USE: Use after creating files from ENCODE data (filtered peaks, merged signals). Creates provenance chain back to source. RELATED TOOLS: encode_get_provenance, encode_download_files
Args: file_path: Path to the derived file you created source_accessions: List of ENCODE accessions this file was derived from (experiment or file accessions, e.g., ["ENCSR133RZO", "ENCFF635JIA"]) description: What this derived file contains file_type: Type of file (e.g., "filtered_peaks", "merged_signal", "differential") tool_used: Tool/software used to create it (e.g., "bedtools intersect", "DESeq2") parameters: Parameters or command used
Returns: JSON with the provenance record ID.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| file_path | Yes | ||
| source_accessions | Yes | ||
| description | No | ||
| file_type | No | ||
| tool_used | No | ||
| parameters | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |