## Templates - Phase 2 - QA analysis | high level plan | estimations
https://ateliere.atlassian.net/browse/CD-10740
https://ateliere.atlassian.net/browse/CD-10741

**Ramp-up | KT:**
- media item + virtual asset metadata referencing
- NTP referencing

**1. Package template - parent referencing**
- parent referencing for **file** deliverable only
- error handling

**QA Estimation: 1.5 week**

----
**2. Media items - descriptive metadata referencing**
https://ateliere.atlassian.net/browse/CD-9721
https://ateliere.atlassian.net/browse/CD-11198

* in metadata templates
* for files referenced by tag attributes
* for files referenced by file attributes
* for files referenced by tag (entity.tags)
* in package templates
* for files referenced by tag attributes
* for files referenced by file attributes
* for files referenced by tag (entity.tags)
* error handling
* for metadata templates - in jobs
* for deliverable naming format - in jobs (we don't have validations right now for deliverable naming format)
* name format help (package templates)

**QA Estimation: 1.5 weeks**

---
**3. Virtual asset referencing**
https://ateliere.atlassian.net/browse/CD-9720
https://ateliere.atlassian.net/browse/CD-11199

entity.virtualAsset['video'].attributes['global']['original file name']

entity.parent[n].virtualAsset['video'].attributes['global']['original file name']

entity.virtualAsset['video'].media['original file name']

* in metadata templates
* in package templates
* error handling
* name format help (package templates)

**QA Estimation: 2 weeks**

---
**4. NTP referencing** - ***Hybrik/Media Convert***

**4.1. Syntax usage in NTP profiles:**
- Title properties & metadata attributes (current + parents)
- Media item technical metadata (by tag attribute|file attributes|tags)
- Media item descriptive metadata (current + parents)
- Virtual asset metadata + media (current + parents)

QA Estimation: 3 weeks

**4.2. Error handling**

QA Estimation: 3 weeks

**4.3. DRM**

QA Estimation: 1 week

**4.4. Converting old inputs** - regression for NTP (old input referencing) - can be done together with 4.1.

QA Estimation: 1 week

**4.5. S3 de-archival mechanism**
QA Estimation: 1 week

**4.5. Migration**
- drm
- profiles (json)
QA Estimation: 3 MD

---
**5. Naming conventions for files/packages/delivery path**
*need more info*
https://ateliere.atlassian.net/wiki/spaces/ZP/pages/3465478182/Templates+-+extended+referencing+capabilities#Organization-settings-%7C-Naming-Convention

---
Q&A
---

- epic name must be changed, tickets updated/changed

**Package Template: parent referencing**
1. ticket must be updated with the latest specs, or add link to specs section for this topic.
2. which deliverable types are affected?
**Answer**: deliverable file type
4. for error handling - which are the expected errors/warnings for each situation(missing tagged file, missing parent etc)? how to fix job at parent level? (fix modal is displayed only for current title)
**Answer**: "missing file" error, specifying the tag title (name or id)
**To be updated with the exact error message (Alina/Andrei)**
6. will the parent index be considered only for copy task or for descriptive metadata referencing for deliverables as well? - e.g. if we choose parent level 2, and we ask for `entity.tags['Series_artwork']['name']`- where do we search for the tagged file - in the current or parent title?
**Answer:** yes, not applicable in name format.

**Descriptive metadata & Virtual asset metadata/media**
1. where can be used descriptive metadata/virtual asset metadata
--> in both package template and metadata template? in specs - descriptive metadata is for metadata template and virtual asset metadata for package template
**Answer:** both package template and metadata template
2. how to do reference a virtul asset - by name? do we need to reference metadata only, or other technical metadata as well? (such as entity type, created date etc)
**Answer:** by name
4. for tag/file/reference attributes from files/media items - should we be able to reference the tehnical/descriptive metadata (and go deeper to multiple levels)?
e.g.
entity.tags['Feature'].attributes['global']['Tag_attribute'].attributes['global']['Description']
**Answer:** no limit when referencing attributes from files.

5. How do we reference the media - by name? (we can have multiple files with the same name, only the locator is unique)
`entity.virtualAsset['video'].media['original file name']`
**Answer:**
**NTP:**
1. we have this input in NTP profile, is there any change that we need in UI? or just replace title with entity? or remove entirely?
**Answer:** need to invest more time to analyse this functionality and decide how to approach it further.
2. for media media properties - are we keeping the same syntax/UI and use the file variabile? now that we added new syntax to reference by tag, are we going to use it here as well?

3. are we extending the technical metadata that can be referenced in NTP? for now we have a limited list (check tooltip from input)

4. same for descriptive metadata (as for 2) - now we have multiple ways to reference files, how it will be changed in order to be uniform across connect?

5. leftover from phase 1 - tooltip need to be updated for available output file attributes
https://ateliere.atlassian.net/browse/CD-10994

---
Examples:
- Native Hybrik - Meta File Tag Ref - 1 output - ProRes 1080p stereo
https://connect.staging.ownzones.dev/ml/transcoder-profiles/3c4c61a8-2dab-4914-9113-ee572a80bc35