Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added missing fields that are utilised in span #12

Open
zazi opened this issue Dec 14, 2017 · 2 comments
Open

added missing fields that are utilised in span #12

zazi opened this issue Dec 14, 2017 · 2 comments

Comments

@zazi
Copy link
Contributor

zazi commented Dec 14, 2017

currently, these are:

  • x.indicator
  • x.packages
  • x.labels
  • x.oa
  • x.license

see here

@miku
Copy link
Member

miku commented Dec 20, 2017

I re-add the comment from #11:

The x was something of an ad-hoc namespace, that I added at the start of the project, meaning something like: not yet fully specified, specify in some later version. The intermediate schema is still 0.9 and we had several discussions about removing it altogether - as to simplify things (get rid of blob server, get rid of extra conversion steps, and so on).

The intermediate schema was not complete from the beginning, so a few field (open access, packages, ...) were added over time. Now, I believe, it is debatable, whether we need another schema altogether when we have a relatively stable format, that is the target schema.xml.

If we manage to drop the intermediate schema, we might be able to drop the blobserver (freeing infrastructure), get rid of the extra conversion steps to intermediate format and to SOLR (saving IO) - and in general have some easier way forward with regard to collaboration. We should discuss this together, and I believe there is some opportunity for this soon.

@zazi
Copy link
Contributor Author

zazi commented Dec 20, 2017

Thanks a lot for your comprehensive and interesting insights. Nevertheless, a search index schema (as it is the case of the finc Solr schema) differs in design and amount of fields a bit from a simple schema to hold relevant information for describing bibliographic resources. Hence, I would still argue for an independent (as simple as possible) schema for describing bibliographic resources, e.g., as a JSON schema (instead of a very technology dependent search index schema). Even the existing finc Solr schema can be simplified, if we go for client-specific search index schemata (with less properties overall ;) ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants