#1223 closed defect (fixed)
SchemaManager schema detection using elements: value test should strip space
| Reported by: | simonp | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | v2.8.1 |
| Component: | General | Version: | v2.8.0RC2 |
| Keywords: | Cc: |
Description
Some metadata files (usually outside GeoNetwork) can have whitespace in elements that causes problems when detecting schema eg.
<gco:CharacterString>Australian Marine Community Profile of ISOM
19115:2005/19139</gco:CharacterString>
Schema detection will not recognize this as an MCP record because of embedded whitespace.
Fix is to strip all space from both schema autodetect element and element from record being tested.
Change History (3)
comment:1 by , 11 years ago
| Priority: | major → minor |
|---|
comment:2 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:3 by , 11 years ago
| Milestone: | v2.8.0 → v2.8.1 |
|---|
Note:
See TracTickets
for help on using tickets.
Fixed in commits f06151f49cabfa3d4465f6433c5d8f49ce15efdc and ebf8526ee5f9b5db7d25ebd01efa62d802bcc22a