Questions about implemented mapping

[rebeccaringuette]

This issue presents questions about the implemented mapping from HAPI to SPASE. Split from the comments in issue hapi-server/data-specification#279.

The https://hapi-server.org/meta/infos/TestData3.1/dataset1-A%CE%B1%E2%98%83.json link has a snowman....? Should this be removed?
Also, the directory structure of TestData3.2 is different than the others. May need to be fixed.

[rweigel]

The snowman is for testing support for a dataset with a UTF-8 character that requires 3 bytes. If I recall correctly, it was chosen because it is a commonly implemented glyph.

The file name is based on the id, and if the id has slashes, directories are created. We don't have a standard for mapping info responses to a file name, so this is an arbitrary choice. Creating a standard is not trivial because one needs to account for special characters for operating systems.

[rebeccaringuette]

Rebecca to check the snowman example.
The 3.2 example: set aside as a later topic due to the complexity mapping to SPASE filenames. Do we need a check on the generated SPASE filename in the code? For now, just create with existing filenames.