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

Export and Import Judgements in the RRE Format #133

Closed
epugh opened this issue May 23, 2020 · 3 comments
Closed

Export and Import Judgements in the RRE Format #133

epugh opened this issue May 23, 2020 · 3 comments

Comments

@epugh
Copy link
Member

epugh commented May 23, 2020

I'm frustrated that I can't take my judgements in Quepid and export them to RRE for running at Scale. And vice versa, I'd like to import judgements from RRE into Quepid so I can actively play with the search parameters in the quepid interface.

Describe the solution you'd like
Export/Import loop in the RRE .json format. Export in the style that is closet to RRE, ie without the query group stuff, and then in import, take a RRE .json and get it to Quepid style.

Describe alternatives you've considered
I thought about exporting a Quepid Case into a complete RRE entity, but I think that involves too many different concepts.

Additional context
This is part of my Explorer project for 2020 to get the open source relevancy projects to all work together better! Buff off the rough edges in getting them to cooperate.

@epugh
Copy link
Member Author

epugh commented May 23, 2020

Hey @agazzarini I thought you might be interested in this ticket ;-)

@agazzarini
Copy link

Wow! Absolutely, if I can help in some way, just give me a shout!

epugh added a commit that referenced this issue May 28, 2020
@epugh
Copy link
Member Author

epugh commented May 29, 2020

i've got the API side done, now on to the front end gui.

@epugh epugh closed this as completed in b96a14d May 30, 2020
epugh added a commit that referenced this issue May 30, 2020
* Support RRE ratings format.  Fixes #133

* extract primary key for doc from field spec for export

* add the template to run, default to quepid.json since we dont know what template a user would use.  Maybe should be REPLACE_ME.json instead?

* add ltr export format

* remove debugging

* rubocop

* guess what?  We had upload icons for downloading, and downloading icons for uploading data!

* omg, maybe have this working in case listing and on a single main case page

* queriesCount is more reliable than the existence or not of the .queries array.  Fixes issue wiht exporting results from the individual Team page

* lets document this bug fix

* attempting GFM

* Remove the <export-case> component in favor of export-entire-case

Deal with when we show only a icon, or when we have a label text too!

* Delete old export-case component with much better export-entire-case, and rename it to export-case.

Removed a unused component!

* Lots of complexity around if a case had queries associated or not.

Turns out that export function with the modal view that supported multiple types of exports never actually checked this setting either.   And it made the UI kind of werid!

* rubocop

* rubocop will be the death of me

* Add LTR and RRE formatted exports!

* update changelog
@epugh epugh mentioned this issue May 31, 2020
5 tasks
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