insanitywholesale / adopse-2021 Goto Github PK

It basically works already???

No subclass fields tho

Steps to repro:

• do a POST for openquestion
• do a GET for evaluationquestions

• take google sheet
• export to pdf
• add to wiki

• get started
  • install dependencies
  • run project
• how to work with the API
  • swagger UI
  • shape and meaning of JSON requests and responses
• how to use postgres
  • connection string in appsettings
  • environment variable USE_POSTGRES
• entityframework
  • code first
  • navigation properties
  • migrations

https://stackoverflow.com/questions/24022957/entity-framework-how-to-disable-lazy-loading-for-specific-query
https://stackoverflow.com/questions/51848257/ef-core-enable-lazy-loading-conditionally/51848495#51848495

reference for containerizing dotnet apps:
https://github.com/dotnet/dotnet-docker/blob/main/samples/dotnetapp/Dockerfile
https://docs.microsoft.com/en-us/dotnet/core/docker/build-container
https://docs.docker.com/samples/dotnetcore/

• Change type of Evaluator in EvaluationEvent to Person
• Change type of Evaluee in EvaluationParticipation to Person
• Delete unused types afterwards

One idea is included in schema.sql through the EvalueeAnswer table

add the ability to connect to postgres instead of in-memory db

• evaluator creates token
• evaluator gives token to evaluees
• evaluee inputs token
• evaluee sees related evaluationevents

instead of piling things on top of PUT, use PATCH instead.

reference: https://andrewhalil.com/2020/12/13/handling-http-patch-requests-in-a-net-core-web-api/

There should be access to subresources such as the questions in an evaluation. Add ability to, at minimum, add and delete questions from evaluation

add the ability to add tag(s) to questions and search by tag(s)

Prototype.zip

• 30-50 words
• more descriptive

Resource: https://docs.microsoft.com/en-us/aspnet/web-api/overview/data/using-web-api-with-entity-framework/part-5

Steps to reproduce:

• do a POST for openquestion with answer included
• do a GET for evaluationquestions and see that answer is null

Resource: https://www.learnentityframeworkcore.com/walkthroughs/existing-database

create a schema for the database

Might use https://gitlab.com/insanitywholesale/gogenjson for this if possible

A list of features to implement later if time allows:

• random set of questions
• random order of answers
• file upload evaluation unit
• timed evaluation
• instant and delayed grading
• dependency chain between evaluations
• anonymous/guest evaluations
• search engine
• example answer for evaluator use only in open questions
• multiple question sets per evaluation
• evaluation tags/categories
• question tags/categories
• create different (evaluations)/(mixes of questions)
• password reset
• show amount of questions in evaluation
• allow going back or not

ad-hoc docker run commands are not ideal so add a docker-compose file that runs the frontend, backend and database

WIP in README.md

add grade-related fields and functionality:

• grade (positive and negative or zero) per answer
• generate grade per question from the above
  • alternatively set grade per question and error out if exceeded by total combined grade of positive answers
• graded or non-graded questions
• graded or non-graded evaluations
• store evaluee grade in evalueeparticipation

https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/ado-net-technology-options-and-guidelines
https://www.programmersought.com/article/77488134107/

https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/retrieving-data-using-a-datareader
https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/dataadapters-and-datareaders
https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/dataset-datatable-dataview/creating-a-datareader
https://docs.microsoft.com/en-us/sql/connect/ado-net/retrieve-data-by-datareader

https://springframework.net/doc-latest/reference/html/data-quickstart.html

https://docs.microsoft.com/en-us/sql/odbc/reference/sample-odbc-program?view=sql-server-ver15

source: https://docs.microsoft.com/en-us/ef/ef6/modeling/code-first/conventions/built-in

Implementation of Login functionality

Stuff for login