Update docs for dts-flavored bulk_specification endpoint #214
Conversation
|
| import specifications. These should be referenced by deployment and testing configuration | ||
| as necessary. |
There was a problem hiding this comment.
Hmm.. now I think about it, I wanted to delete the import_specifications folder as it was no longer needed since the narrative generates them on the fly. They were a stop gap up until that point.
See #178
Does it make sense for the schemas to live here or somewhere with a better name?
There was a problem hiding this comment.
If the rest of the folder is going away, I don't see a reason not to move schemas to something like "import_specification_schemas" or something like that.
There was a problem hiding this comment.
It might still make sense to have a template or some user-facing (or dev-facing) documentation for using the XSV/Excel importer specifications, though.
There was a problem hiding this comment.
If the rest of the folder is going away, I don't see a reason not to move schemas to something like "import_specification_schemas" or something like that.
I'd probably call it "import_schemas" to disambiguate from the import specification system
It might still make sense to have a template or some user-facing (or dev-facing) documentation for using the XSV/Excel importer specifications, though.
There's this: https://docs.kbase.us/data/upload-download-guide/bulk
As the title says. This just updates the relevant READMEs.