Kathryn Irish

Results 23 issues of Kathryn Irish

Following discussion in https://github.com/openownership/lib-cove-bods/issues/123 Currently there's a normative requirement 'If an address in the addresses array is of type "alternative" then there is also another address in the array' There's...

codelist

Currently the description is "if interestedParty is a string, the interested party MAY be an entity or a person." The use of MAY here could be confusing. Clearer wording could...

schema descriptions

# Overview **What does this pull request do?** updates example data - componentRecords fields were listing statementIds, now they list recordIds **How can a reviewer test or examine your changes?**...

For personType unknownPerson and entityType unknownEntity do we require an unspecifiedRecord reason? for the anonymous person/entity the codelist description includes "The reason for non-disclosure should be given in the accompanying...

feature: missing information

The personType codes are knownPerson, anonymousPerson and unknownPerson the "Person" suffix seems unnecessary? (same possibly applies to entityType codes which have "entity" as a suffix?) is this to differentiate between...

codelist

In the schema we have `missingInfoReason` is required if `politicalExposureStatus` is `unknown` `missingInfoReason` is currently a field in the 'PEP Status' object and `details` is an array of these objects....

Validation

Issue added following removal of [this page](https://standard.openownership.org/en/0.3.0/schema/guidance/provenance.html) from the docs, see #636. That page included some information about using annotations for processing/cleaning/enrichment. But if annotations are to be used to...

codelist

GLEIF has a field 'transliterated other addresses' - we could think about options for address translation/transliteration beyond using an annotation https://www.gleif.org/en/about-lei/common-data-file-format/current-versions/level-1-data-lei-cdf-3-1-format

codelist

If there's a delay before the data review tool is able to process 0.4 data we may want to add warnings on the review tool and in the BODS docs?

Currently interest.startDate is an optional field. I think we should have some guidance that all interests SHOULD have a startDate (we currently say this can be rounded to nearest month...

feature: interests
dates
required fields