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

Optional levels in the domain model #45

Closed
agazzarini opened this issue Aug 31, 2018 · 2 comments
Closed

Optional levels in the domain model #45

agazzarini opened this issue Aug 31, 2018 · 2 comments
Assignees
Labels
enhancement New feature or request task
Milestone

Comments

@agazzarini
Copy link
Member

The RRE domain/data model provides a hierarchy with several levels (corpus, topic, query group, query and metrics).

Although this could be helpful when you need to model a rich domain, sometimes that results in a lot of redundancy (e.g. query groups and queries have the same cardinality).

It would be great if the ratings file would allow to exclude one or more levels, with the edge case where we have only queries.

@agazzarini agazzarini added enhancement New feature or request task labels Aug 31, 2018
@agazzarini agazzarini added this to the 1.1 milestone Aug 31, 2018
@agazzarini agazzarini self-assigned this Aug 31, 2018
@agazzarini
Copy link
Member Author

topics and query_groups are now optional in the RRE domain model. That allows a high level of flexibility when defining the ratings set. Specifically (wiki will be updated asap) the domain model supports one of the following:

  • n topics -> n query groups -> n variant queries (i.e. logical variants of the same query)
  • n query groups -> n variant queries
  • n variant queries

In case one level is missing, RRE will create a unnamed node. So for example, if topics are missing, all defined query groups will belong to an "Unnamed" topic; if query groups are missing queries will belong to an "Unnamed" query group which in turn will belong to an "Unnamed" topic.

In this way the domain model is always consistent, and a report could easily hide those "Unnamed" layers

@agazzarini
Copy link
Member Author

RRE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request task
Projects
None yet
Development

No branches or pull requests

1 participant