Skip to content

Issues: iuni-cadre/cadre-wiki

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.

Sign up for GitHub

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

25 Open 0 Closed
25 Open 0 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

We need a tagging system for the packages.
#25 opened Sep 19, 2019 by contactaditya
Can packages have different access views like: Public, Private or Team Only.
#24 opened Sep 19, 2019 by contactaditya
We need to record the dataset that the package is using: MAG, WOS in the package table in the cadre metadatabase.
#23 opened Sep 19, 2019 by contactaditya
We need to have more helpful and specific error messages.
#22 opened Aug 29, 2019 by contactaditya
Need to have a place in the Cadre Query Interface where users can access their own EFS Folders. We can probably have a folder viewer or a tagging system.
#21 opened Aug 15, 2019 by contactaditya
Have a composite interface where we can query both graph and relational database and the user does not have to bother with selecting the database to query on.
#20 opened Jun 20, 2019 by contactaditya
We need to add more operators like NOT, XOR, Greater Than and Less Than.
#19 opened Jun 20, 2019 by contactaditya
Add the option to export/preview sql code generated by the GUI
#18 opened Apr 30, 2019 by XiaoranYan
We need to investigate what tools and frameworks we need for our notebooks. Adding support for local spark clusters to integrate with the cloud and making this feature available for all users.
#17 opened Apr 30, 2019 by XiaoranYan
Investigate ways to allows users to do large queries through the interface.
#16 opened Apr 30, 2019 by XiaoranYan
Investigating the way to keep track of file size and come up with way to handle large output.
#15 opened Apr 30, 2019 by XiaoranYan
We need a limit for the output size of the .CSV files. The Query Builder should you a different output format in that case.
#14 opened Apr 30, 2019 by XiaoranYan
1
Have a policy to clean up EFS periodically so that old unused query results don't end up taking up a lot of space.
#13 opened Apr 30, 2019 by XiaoranYan
Come up with a policy to decide how often do we want to update the Web of Science Data and the MAG Data in our databases.
#12 opened Apr 25, 2019 by contactaditya
Integrate MAG with the Query Interface and do we want to include the Patents data before Rome.
#11 opened Apr 25, 2019 by contactaditya
Have a feature request option for our application.
#10 opened Apr 25, 2019 by contactaditya
Have a plan ready for the CADRE Website and working out details like the tech stack, programming languages etc and whether or not we will need a feedback form/suggestions form and whether or not we will be using a database.
#9 opened Apr 25, 2019 by contactaditya
Make sure we have a guest account with all the members of the big ten academic alliance so that we can test out if the login feature is working correctly for the upcoming demos.
#8 opened Apr 25, 2019 by contactaditya
Have a log out button and a user profile containing details of the person.
#7 opened Apr 22, 2019 by contactaditya
Come with a policy for connection timeout and retires for both Preview Function and the actual final query.
#6 opened Apr 22, 2019 by contactaditya
Have a link to the Cadre Website on the Query Interface.
#5 opened Apr 22, 2019 by contactaditya
Have a policy related to session timeout and not to log out user if the user has an active session at least for an hour.
#4 opened Apr 22, 2019 by contactaditya
Have a policy related to data collection and be transparent about it.
#3 opened Apr 22, 2019 by contactaditya
Think about Alignment, font face, font size, colors for buttons, footers and other related design issues.
#2 opened Apr 22, 2019 by contactaditya
Allow users to select the output columns for the final query results.
#1 opened Apr 22, 2019 by contactaditya
ProTip! Exclude everything labeled bug with -label:bug.