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

feat: Add authors field to info.json for questions #9790

Draft
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

SethPoulsen
Copy link
Collaborator

@SethPoulsen SethPoulsen commented Apr 30, 2024

As part of shipping the question sharing featues (#9397), we would like to ensure that quesiton authors are able to get credit for their work, and so we are creating the ability to denote the authors of a question in the JSON, which will automatically be copied when people copy questions.

Some remaining items to discuss about this before pushing:

  • do we want an authors table as well?
  • what should be the piece of information we de-dupe authors across? email? (and if people use different names with the same email, what do we do then?)
  • what syntax do we want to use to allow people to put names and emails into these strings?

Comment on lines 178 to 180
tags?: string[];
authors?: string[];
clientFiles?: string[];
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do the tests have entirely separate type declarations for the JSON file schemas than the main codebase has in course-db.ts?

Copy link
Contributor

github-actions bot commented Apr 30, 2024

All images

Image Platform Old Size New Size Change
prairielearn/executor:125c6653cf52d758d6bb43bef4b6da846ace6de5 null 1627.45 MB 1627.62 MB 0.01%
prairielearn/prairielearn:125c6653cf52d758d6bb43bef4b6da846ace6de5 linux/amd64 1627.44 MB 1627.62 MB 0.01%

@SethPoulsen SethPoulsen changed the title feat: Add authors filed to info.json for questions feat: Add authors field to info.json for questions May 8, 2024
@jonatanschroeder
Copy link
Member

I was looking at old issues, and #1824 may be resolved here.

@SethPoulsen
Copy link
Collaborator Author

thanks for linking that Jonaton. It looks like some of the decision decisions around this have changed since then, we should discuss this more probably.

@mwest1066
Copy link
Member

thanks for linking that Jonaton. It looks like some of the decision decisions around this have changed since then, we should discuss this more probably.

I'd still really like to figure out how to support "claiming" of authorship in some way, or otherwise understand how we are going to handle the question of who can view authorship statistics.

@SethPoulsen
Copy link
Collaborator Author

figure out how to support "claiming" of authorship in some way

the simplest way, I think, is to just have a form where you input an email. Then we email a report to that email address. If you truly do own that email, you get the report!

If authors were actually linked to UIDs, that would be another way to make it happen. I think we should discuss again why we do/don't want to do that.

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

Successfully merging this pull request may close these issues.

None yet

3 participants