The Meta Overlay generating a blank entry that should not be present

[swcurran]

I used the attached OCA Source file and when I generated the OCA Bundle (using https://browser.oca.argo.colossi.network/#/), the resulting Meta Overlay had a JSON entry of "" : "". Such entries should be suppressed in the output. The file was created by downloading the OCA Template from the OCA Browser, and then pasting in (values only) into the fields.

ocatest.xlsx

For example, the "en-CA" Meta Overlay has this content:

{
   "capture_base":"EKpcSmz06sJs0b4g24e0Jc7OerbJrGN2iMVEnwLYKBS8",
   "digest":"ERzcTK4SQCYv204QOm0r3wotG5JeMKvl0tcrC5TxMD14",
   "type":"spec/overlays/meta/1.0",
   "language":"en-CA",
   "name":"Person Credential",
   "description":"A Canadian schema used for the identity of a person",
   "":"",
   "issuer":"Government of British Columbia",
   "issuer_description":"Government of British Columbia",
   "issuer_url":"https://www.gov.bc.ca/"
}

[pknowl]

@swcurran - The issue is with the construction of the OCA parsing spreadsheet. You have to treat the child and the parent schemas separately (i.e., as two parsing spreadsheets). I've created the two files for you try on your side. You'll see that there is a new column "CB-RS" in the second OCA parsing spreadsheet containing the SAID of the child schema.

ocatest_child.xlsx ocatest_parent.xlsx

Note that generating default layouts via the OCA Browser (https://browser.oca.argo.colossi.network/#/) doesn't support layouts where Reference is used, so to preview OCA when using the Reference-data type, the layout must be provided by the user as a *.yaml file.

[swcurran]

I don't understand the relationship between the issue and parent/child spreadsheet. We don't have any parent/child requirements AFAIK, so there should not be a need for such a structure. The issue is that with the given input, we are getting the extra null name/null value pair in the output.

Is there something wrong in the input Excel that I provided?

[pknowl]

The Meta overlay in the original Excel you provided looks weird to me due to the attribute nesting, but let me get one of the technical guys to confirm. In any case, you now know how to reference stuff!

[swcurran]

There isn't supposed to be any nesting -- it's not intended, so not sure what you are seeing.

[blelump]

@swcurran please check with the newer template: https://github.com/THCLab/oca-parser-xls/blob/main/templates/template.xlsx .

[swcurran]

With the revised template, the generation (using the command line parser) doesn't work, giving errors below. I started from the template and pasted the values from my existing sheet, resulting in this file ocatemplate.xlsx. The old version of the file works both ways.

All of the data is (I think) in the same place as before.

{
  "errors": [
    "Not found column with Attribute Names definiton",
    "Not found column with Attribute Names definiton"
  ]
}

When I try it online, I get this output:

Failure! Fix those errors and try again:
Parsing attribute in row 15 failed. Attribute name is empty.
Parsing attribute in row 16 failed. Attribute name is empty.

[olichwiruk]

With oca-rust v0.2.23 and online works now.

That "" : "" entry in Meta overlays is caused by formulas in Meta [Attribute Name] and Meta [Attribute Values] columns that should be deleted, so the proper file looks like this: ocatemplate.xlsx.

BTW: in Main sheet value defined as Format for issuing_jurisdiction attribute (cell F14) is actually Entry Codes, so it should be placed in cell G14.

[swcurran]

Confirmed -- thanks! Updated the sheet to use Entry Codes a well -- thanks.