On Mon, 2016-09-26 at 14:56 +0700, Alexandre Rafalovitch wrote:
> So, a single format (JSON if it works,
> JSON+comments/quotes that Solr actually supports, or whatever). But
> then the inputs and outputs should be consistent so that the same
> tooling could be used for everything.
This is a very important part. Whatever is chosen should support inline
documentation. In a way, choosing the comment-lacking JSON format is a
good thing as that allow the introduction of an explicit documentation
key:
{ subheadline: {
"_documentation", "Only used for articles from source X, remove if
that source is deprecated",
"type", "ImportantText",
"stored", "true",
...
},
...
}
It would be great to have the content from such a documentation field
pop up in the schema browser in the GUI.
- Toke Eskildsen, State and University Library, Denmark
