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

cloud migration #189

Open
21 of 24 tasks
hmuniz opened this issue Sep 27, 2019 · 4 comments
Open
21 of 24 tasks

cloud migration #189

hmuniz opened this issue Sep 27, 2019 · 4 comments

Comments

@hmuniz
Copy link
Contributor

hmuniz commented Sep 27, 2019

  • synset page
    • content
    • add comment
    • delete comment
    • add vote
    • delete vote
    • add suggestion
    • delete suggestion
    • accept suggestion
    • reject suggestion
  • home page
    • content
    • login
  • search
    • redirect to synset page when search by a synset id
    • facets
    • synsets
  • data
    • document data migration (solr -> es)
    • consistency check
  • activity
    • search
    • filter
    • sort
hmuniz added a commit that referenced this issue Sep 27, 2019
  - votes handles
  - comment handles
  - suggestion handles
* define more generic methods
related to #189
hmuniz added a commit that referenced this issue Oct 2, 2019
update execute-search generic funtion args
add tags read
hmuniz added a commit that referenced this issue Oct 3, 2019
update heroku-setup.lisp to read credential from env var, related to #189
remove unused code
@hmuniz
Copy link
Contributor Author

hmuniz commented Oct 9, 2019

All information about the data migration and injection can be found in the BOX BRL-KRR/wnpt-server/solr->es/.

@arademaker
Copy link
Member

Por que merge.py e inject.py serem um gists e não ficar no repo? Por que ele precisa da own-api se os dados json já teriam sido exportados?

@arademaker
Copy link
Member

remove

Experiments -- We have a couple of experimental prototypes under development to test out some ideas.

but please document here the experiments that we are leaving behind and where is the code.

@vcvpaiva
Copy link
Member

vcvpaiva commented Oct 22, 2019 via email

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

3 participants