**METADATA TEMPLATES REFERENCING PHASE1**

### [CD-10748] Metadata Template - title properties

1. [BE] Metadata template preview does not return title properties for {{entity.parent.parent.parent.name}} (3) and more.
Returns data for {{entity.parent.parent.name}} (2) and lower.
Also, properties are returned, in Jobs, even for: {{entity.parent.parent.parent.parent.parent.parent.parent.parent.parent.parent.parent.parent.parent.name}} (13)

- [ ] DEV
- [x] QA - check comments - was not in scope for this phase, **no action item**

2. [**CD-10829**][BE] Properties **updatedBy, updatedAt, createdBy, createdAt,** are not populated with data for any title, for both Jobs and template Preview.

- [x] DEV - **JIRA ticket Ready for QA**
- [x] QA

---

### [CD-10749] Metadata Template - title metadata

1. [BE] The Date metadata property will not appear in the XML after the job finishes
[Date Fields](https://i.imgur.com/XElhTMm.png)
[XML output](https://i.imgur.com/6FLjNcV.png)
[Postman](https://i.imgur.com/MQXnPCf.png)

- [ ] DEV
- [x] QA - We found that the metadata property had some extra spaces between word, that will not shown in the metadata properties UI, from the entity type, **no action item.**

2. [**CD-10830**][BE] Boolean default value is empty for Global attributes, not False.
[Job](https://connect.char.ownzones.dev/metadata-templates/jobs/9f3ce563-cbf8-42d6-916e-e612f84b53af)
[Entity](https://connect.char.ownzones.dev/metadata-templates/entity-types/4acbae02-69da-4caa-9e86-ed5b764ec14f)
[Metadata Template](https://connect.char.ownzones.dev/metadata-templates/metadata-templates/f0b92ca5-87b7-4ea2-b740-3826a457e712)
[Metadata Output](https://connect.char.ownzones.dev/metadata-templates/files/4a7b48b3-e468-4c37-b26d-ad7225c548a3)

- [x] DEV - **not an issue, closed**
- [x] QA

3. [**CD-10841**][BE] Error "Cannot read property 'parentId' of null" is returned when a job is run that has a request for a metadata property from a parent title, and the title is deleted.
[Postman](https://i.imgur.com/Xhd5Hcy.png)

Note: I tried to remove the parent title from the child and then run the job. The message returned was: "The following title(s) do not have a parent in its hierarchy"

- [x] DEV - **JIRA ticket Ready for QA**
- [x] QA - issue is fixed on char

4. Invalid job retuned when the user requires information from an non existing parent (job - https://connect.char.ownzones.dev/char-org/jobs/12f546a2-1880-4407-b480-92d78a9fa3ae)
Also no validation message is shown

- [x] DEV - From BE's point of view, we return the Fatal error 'The following title(s) do not have a parent in its hierarchy'. The UI code deployed on char is not handling this error yet. (https://i.imgur.com/pTZa6PS.png)
- [x] QA - **re-validate after latest deploy on FE - done, all well**

---
### [CD-10750][QA] Metadata Templates - files referencing and properties

1. [**CD-10882**] Properties from Streams, Format, BoundingBox, etc. don’t return any value, but throw errors on the job page.

Job Example:https://connect.char.ownzones.dev/metadata-templates/jobs/de9859de-f859-4bd4-999c-2c6d5101231a

Metadata Template Example: https://connect.char.ownzones.dev/metadata-templates/metadata-templates/31e41b0f-e98e-4014-b12c-42aa05866092

Output:https://connect.char.ownzones.dev/metadata-templates/files/83824d26-581a-4bb9-90eb-53dd19e57fba

- [x] DEV - **JIRA ticket CD-10882 Ready for QA** (fixed issues and added comments in ticket for those validations that are due to incorrect referencing)
- [x] QA

2. {{entity.tags['Movie']['designations']}} does not return any value

Job Example:https://connect.char.ownzones.dev/metadata-templates/jobs/de9859de-f859-4bd4-999c-2c6d5101231a

Metadata Template Example: https://connect.char.ownzones.dev/metadata-templates/metadata-templates/31e41b0f-e98e-4014-b12c-42aa05866092

- [x] DEV - 'designations' is not implemented, cannot be used (issue fixed in JIRA ticket CD-10882)
- [x] QA

3. [**CD-10927**] **mediainfo properties** json, **bounding box** json, return **null** when used in name format, package template
* {{entity.tags['Movie Child13']['properties']['boundingBox'] | json}} should return: {"height":1080}
* {{entity.tags['Movie Child13']['mediainfoProperties'] | json}} should return: {"media":{"_ref":"https://tf-s3-ownzones-char.s3.amazonaws.com/metatemp/deliverables/Child13_MediaConvert-ProRes_HD_e58b8a55-d58c-4575-8aab-cc6f6aeb306c_pcm_s24le_2_prores_bt709_260_169_23976_1920_1080.mov"}}

- [x] DEV - **JIRA ticket on BE, CD-10927, in QA Review** Deployed on Char.
Deployed on Char.
Examples and limitation for json filter documented here:
https://ateliere.atlassian.net/wiki/spaces/ZP/pages/3779526730/Template+Reference+syntax#Limitation-for-json-filter
- [x] QA - Bogdan to validate

4. [**CD-10938**] entity.attributes['locale']['Tag'].**properties.definition** is not working in templates
- [ ] DEV - **JIRA ticket on BE, CD-10938, in Progress**
- [ ] QA

5. [**CD-10939**] entity.attributes['locale']['Tag'].**tracks** is not working in templates
- [x] DEV - **JIRA ticket on BE, CD-10939, in QA Review** Deployed on Char.
- [ ] QA - Teddy to validate
___

### [CD-10762][QA] Job validation errors/warnings ###

1. Misleading information in the warning section.
[Misleading info](https://i.imgur.com/DNt2RyQ.png)

- [x] DEV - Fix dev done & deployed on Char. Ticket [CD-10874](https://ateliere.atlassian.net/browse/CD-10874).
- [x] QA

Action point BE: To remove 'Missing tag for file reference field "Templates Localized Tag Image" in template "Ngr File and tags Templates"' message. - **CD-10874**

2. Missing the "Fix" button from the job page
[Missing Fix Button](https://i.imgur.com/QpnwndV.png)
(job: https://connect.char.ownzones.dev/char-org/jobs/361cc864-a54a-40c0-80a0-a9d79bcc74bf)

- [x] DEV
- [x] QA

Action point FE: **CD-10875**

3. Warnings appearing duplicated when there are no errors.
Job: https://connect.char.ownzones.dev/char-org/jobs/b31501b5-ab61-419b-a408-7484e91b5600
Fix to be done in BE.
- [x] DEV - Fix dev done & deployed on Char. Ticket [CD-10886](https://ateliere.atlassian.net/browse/CD-10886).
- [x] QA

Action point BE: **CD-10886**

4. [**CD-10921**]Warnings will appear on the build workflow, although there are no warnings during job analysis.
[Valid job](https://i.imgur.com/MpGfXhn.png)
[Warning messages](https://i.imgur.com/iFayO0r.png)
Job: https://connect.char.ownzones.dev/char-org/jobs/b31501b5-ab61-419b-a408-7484e91b5600

- [x] DEV - Fix dev done & deployed on Char. Ticket [CD-10921](https://ateliere.atlassian.net/browse/CD-10921).
- [x] QA - verified by QA, fixed.

5. [**CD-10942**]Conditions:
+ Attribute doesn’t fulfill validation rules (The “Name” attribute has “Rest” value but the requires a minimum length of 10 characters.)
- Not Required in metadata set (field is marked as not required in entity type)
+ Available in template

Current behavior on [Staging env]( https://connect.staging.ownzones.dev/ml/jobs/877fdbc1-2e81-4b37-90f1-cf68a8c1183e) Job Status: Invalid

Actual behavior on [Char env]( https://connect.char.ownzones.dev/char-org/jobs/e6026c54-2855-4499-b37a-05adfa05c374) Job Status: Valid with warning

- [ ] DEV - Ticket [CD-10942] to be fixed after CF
- [ ] QA

6. [[CD-10953](https://ateliere.atlassian.net/browse/CD-10953)] When a job has both **Errors** and **Warnings** the **Fix** button appears for both sections.
However, as soon as the **Errors** are fixed, the button disappears from the **Warning** section as well.
If the job has only **Warnings** then the button doesn't appear at all.

Fix is present-both **Errors** and **Warnings** are present:

Fix is missing-only **Warnings** are present:

Job example: https://connect.char.ownzones.dev/char-org/jobs/86446202-3023-422d-aa31-49817b9a4b72

- [x] FE - Ready to be deployed on char
- [x] QA

7. **( [[CD-10959](https://ateliere.atlassian.net/browse/CD-10959)] )** When there's an issue with a metadata attribute that can be fixed but another (unfixable) one is also present, both are in the same group and the **Fix** button is present.
However, the **Fix modal** can only fix the issues from the title set in the job thus only one validation error remains when it is opened, potentially misleading the operator.

**In this example, the unfixable error is about the attribute value missing from the referenced title.**

What the operator sees in the job (2 errors for 2 different titles):

What the operator sees in the **Fix modal** (1 error from the job's title):

After fixing the issue from the current title, the **Fix** button disappears and the error from the referenced title remains:

Job example: https://connect.char.ownzones.dev/char-org/jobs/185ba4d7-c9a1-4d11-9e72-181227e8ad6d
**To be added on the improvement list.**
A ticket was reported for easier tracking: https://ateliere.atlassian.net/browse/CD-10959

8. The title does not have a hyperlink for parent level validation errors.


Job example: https://connect.char.ownzones.dev/char-org/jobs/c1d9d572-406e-4b0e-a1c1-64cdc63ed40b

https://ateliere.atlassian.net/browse/CD-10969
- [ ] [DEV]
- [ ] [QA]

**To be analysed during regression.Ticket **
___

### [CD-10751] [QA] Metadata Templates - NTP deliverables references

#### Observations:
1. Cannot use **.designations** when extracting information from an NTP output as no tags can be set on the outputs themselves.
i.e. Cannot test the following **package.deliverables['transcode1'].outputs['output1'][0].designations**
- Comment: to be added in Confluence as a limitation, **no action item.**
2. Cannot use **.userProperties** when extracting information from an NTP output as no user properties can be set on the outputs themselves.
i.e. Cannot test the following **package.deliverables['transcode1'].outputs['output1'][0].userProperties.**
- Comment: to be added in Confluence as a limitation, **no action item.**
#### Issues:

1. NTP Meta templates do not generate any values when using **{{package.deliverables['transcode1'].outputs['output1'][0].tracks}}**

Package template used: https://connect.char.ownzones.dev/char-org/package-templates/6f318099-f4d8-467d-849c-e6c3e6243083

Note: It works when using the alternative method with **{{package.deliverables['transcode1'].outputs['output1'][0].properties.streams}}**


- [x] BE - **future improvement**
- [x] QA

2. An older issue affects the generation of deliverable file ID's when no additional properties are indicated. https://ateliere.atlassian.net/browse/CD-10725
i.e. Using **{{package.deliverables['transcode1'].outputs['output1'][0]}}** generates **[object Object]** as an output instead of the file ID.
**- Comment: not an issue.**

3. Regarding the replacement of the **{{title.name}}** with **{{entity.name}}** this affects the metadata/package templates but not the NTP as well.
In the NTP the operator stil needs to use **{# title.name #}** and it works fine.
Trying to replace **title** with **entity** in the NTP will generate a validation error when attempting to create a job.
- **Comment: this will be covered in Phase 2.**



However, when using the older one, with **title** it works fine.


- [ ] BE
- [x] QA - to be checked in phase 2

4. Using liquidJS logic extract some parameters and use them further with a custom variable generated a validation issue in the Job: **Unable to resolve the remaining syntax file1definition**


For example, the operator used **file1definition** variable for a custom logic:

This works fine when used in the job as it produces the following:

Meta template example: https://connect.char.ownzones.dev/char-org/metadata-templates/50f9797b-8480-4e5c-ae4d-6ecd936c88a2
Job example: https://connect.char.ownzones.dev/char-org/jobs/7bbde3fb-7984-4f38-a1d7-a6e33dd306a6

- [x] DEV BE - **JIRA ticket [CD-10870] Ready for QA**
In this ticket was also fixed the issue with paramaters in 'for' operations: [Now, reversed, offset, limit are supported](https://ateliere.atlassian.net/wiki/spaces/ZP/pages/3779526730/Template+Reference+syntax#%5BhardBreak%5DFor-Loop)
- [x] QA

5. Can we, please, rephrase the hierarchy validation message due to spelling mistakes?
Currently it appears as **The following title(s) do not have a parent in its hierarchy**
The spelling is incorrect and it should appear either as:
a) The following title(s) does not have a parent in its hierarchy
or
b) The following title(s) do not have a parent in their hierarchy

- [x] BE - **CD-10876** Done & deployed on Char.
- [x] QA

6. Using the .properties.streams syntax makes the array output appear as a string of objects.

Input string: **package.deliverables['transcode1'].outputs['output1'][0].properties.streams**
Output:
**[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]**

Meta template example: https://connect.char.ownzones.dev/char-org/metadata-templates/50f9797b-8480-4e5c-ae4d-6ecd936c88a2
Job example: https://connect.char.ownzones.dev/char-org/jobs/7bbde3fb-7984-4f38-a1d7-a6e33dd306a6

- [x] BE
- [x] QA - not an issue

### [CD-10752][QA] Package Templates | deliverable name format - general properties

#### Issues:
1. When indicating the **locatorUrl** and **mimetype** additional properties in a deliverable name format, the following happens:
a) Everything that was hardcoded before (free text) is ignored
b) Everything that was hardcoded after (free text) is maintained
c) The value extracted doesn't match the value that is extracted in the metadata template

i.e.
Using either
Name format: Tag_locator_{{entity.tags['Video_deliv_attributes']['locatorUrl']}}.mov

or
Name formatTag_locator_{{entity.tags['Video_deliv_attributes']['mimetype']}}.mov

Will result in:

If the same strings are used in a metadata template, the output is the following (71=mimetype and 72=locatorUrl):

Job example: https://connect.char.ownzones.dev/char-org/jobs/185ba4d7-c9a1-4d11-9e72-181227e8ad6d
Package template example: https://connect.char.ownzones.dev/char-org/package-templates/93f241f6-b9c5-4fbe-a3fe-58d4637fad55
- [x] BE - JIRA ticket [CD-10907]
- will not be done, the edge case to be documented in Confluence.
https://ateliere.atlassian.net/browse/CD-10907
- [x] QA

2. Using a referenced attribute for a deliverable name doesn't extract it at all.
I.e. Name format: Global_ref_{{entity.attributes['global’][‘Ref_global’].attributes['global’][‘String_global’]}}.jpg


Makes the file look like this:

However, it works fine in a metadata template:

Job example: https://connect.char.ownzones.dev/char-org/jobs/185ba4d7-c9a1-4d11-9e72-181227e8ad6d
Package template example: https://connect.char.ownzones.dev/char-org/package-templates/93f241f6-b9c5-4fbe-a3fe-58d4637fad55
- [x] BE - In this job, {{entity.attributes['global’][‘Ref_global’].attributes['global’][‘String_global’]}} is not a valid reference. The title referenced 'Native meta file output test - Teddy (Meta templates checks)' is https://connect.char.ownzones.dev/char-org/titles/41310624-0bd1-4279-a9a6-ca920a526779?tab=metadataSets
It does not have an attribute named String_global, globally.
It works fine in the metadata template because there are valid references, e.g. {{entity.attributes['global']['Ref_global'].attributes['global']['Native_test']}} -> Title 'Native meta file output test - Teddy (Meta templates checks)' have an attribute named Native_test, globally.
I tested with a File Deliverable Name Format 'Global_ref_{{entity.attributes['global']['Ref_global'].attributes['global']['Native_test']}}.jpg' and works fine.
- [x] QA - indeed

3. Attempting to use {{title.slug}} in a deliverable name format doesn't extract any information from the title.
It works when used in the package naming convention, from the organisation's settings though.

Package template:
https://connect.char.ownzones.dev/char-org/package-templates/f8a8b5fd-4d48-4feb-bc77-d5be57a352bf
Job:
https://connect.char.ownzones.dev/char-org/jobs/86446202-3023-422d-aa31-49817b9a4b72

[CD-10928][BE] 'slug' title property is not working in templates
- [x] DEV - **JIRA ticket on BE, CD-10928 in Ready for merge**
Deployed on Char. Now {{entity.slug}}, {{entity.parent.slug}}, etc, is working in templates (both metadata templates and package templates -> deliverable name format)
- [x] QA

#### General issue:
1. When an incorrect or unsupported syntax is used, the validation message returns that variable with a comma instead of a stop sign (if present).
i.e. Using **{{punct.nu.virgula}}** in the template returns the validation message specifying **Unable to resolve the remaining syntax: punct,nu,virgula**

The Warning shows:

The package template contains:

Due to these commas replacing the stop signs, the operator can copy the error and search for it in the template, ending with nothing found as the presented string was altered from what the operator actually used.
- [X] BE - Ticket [CD-10890](https://ateliere.atlassian.net/browse/CD-10890) was created.
- [ ] QA