You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Records we harvest from CSIRO who are also using 19115-3:2018 include two contactInfo elements for an organisation. One containing the postal address of the organisation and one containing the street address. Some details such as phone numbers and websites are duplicated in each contactInfo element (see xml fragment below) although this does not necessarily need to be the case.
We can't currently view these records in the default view as indexing can't currently handle multiple websites for a responsible party.
However, if I modify indexing to index just the first website, then there are display issues as well:
Would be good if we could at least index the records. We'd also be happy just to display the first contactInfo section for a party until the code (which looks to have been written for 19139 which is far less flexible) can be reworked to handle multiple contactInfos, web sites, etc. I'll put up a pull request for that if that's considered suitable.
element when indexing responsible party's to more align with the way 19139 records are indexed until
until gmMetadataContact is reworked to handle 19115-3:2018 responsible parties
Difficult to handle all possible combinations until that rework is done.
Records we harvest from CSIRO who are also using 19115-3:2018 include two contactInfo elements for an organisation. One containing the postal address of the organisation and one containing the street address. Some details such as phone numbers and websites are duplicated in each contactInfo element (see xml fragment below) although this does not necessarily need to be the case.
We can't currently view these records in the default view as indexing can't currently handle multiple websites for a responsible party.
However, if I modify indexing to index just the first website, then there are display issues as well:
Would be good if we could at least index the records. We'd also be happy just to display the first contactInfo section for a party until the code (which looks to have been written for 19139 which is far less flexible) can be reworked to handle multiple contactInfos, web sites, etc. I'll put up a pull request for that if that's considered suitable.
The text was updated successfully, but these errors were encountered: