• reorder on a single page
• drop on the TOC to move to another page

Bonus

• spring loaded TOC elements allowing fine positioning across pages

Really, the ideal would probably be to make it a full screen modal for comment threads and comments within a thread (like UINavigationView), shrinking to a toolbar sort of thing for the text selection step of creating a new thread.

Event names:

• :visit_page, {case_slug:, page_id:, page_position:, duration:}
• :visit_edgenote, {case_slug:, edgenote_slug:, duration:}
• :visit_podcast, {case_slug:, podcast_id:, duration:}
• :read_card, {case_slug:, card_id:, duration:}

• Redesign editor toolbar so it’s not annoying (#110)
• Redesign Edgenote creation/editing workflow so it’s not annoying (#196)
• Give random users the ability to create cases, but to edit only their own (#261)
• Make unpublished cases invisible to non-editors

Like this? http://soundcite.knightlab.com

• subtitles
• tables
• blockquote
• inline images?? for when they’re really more than Edgenotes

In non-narrative contexts

• hyperlinks

“Captain‘s log” or blog posts?
Slack-style conversation between instructors who've used the case?
Hybrid.

Including:

• individual experiences of teaching and assessing the case, and of evaluating the students
• ideas for additions/extensions/spinoffs in classroom use
• MSC-pinned specific suggestions that emerge as exemplary

The delete button for comment threads a user just created is broken, but editors also need to be able to delete other people's comments or threads as a form of moderation.

Reader should hold the user’s profile and activity information, while devise should use LoginProviders, unique on the pair (email, provider) of which a user can have many. This will deal with the problem in which a user creates an account with a password and later tries to sign in with Google or Canvas using the same email.

Probably this is a .bind() creating a new function signature so the EventListener can’t be removed kind of problem. Look for that.

There are some problems with translating cases by using a json locale-keyed dictionary for each database field.

• Impossible to separate UI language from case language
• An editor with their UI in French will inadvertently translate English-only cases instead of editing their English contents.
• Can’t translate attachments
• Can’t have different numbers of cards/pages between translations
• Not searchable

Put these problems behind us by using different linked Case models for different translations.

• Add a locale field and a translation_base association to Case. Translations of a case have that case’s id as their translation_base. Each untranslated case’s translation_base is itself — not nil so that we can query for the full set of translations of a case, which must include the original.
• Get the “also available in these languages” list from the cases with the same translation_base
• Filter the catalog by locale—with fallbacks to English if the case isn’t translated
• Make a CaseCloner to deep-copy a case
• Serialize urls for the translated cases and make the other available languages links work without changing the locale
• New translation page that takes a new locale and new slug, then deep copies the case.
• Landing page for while the user waits for their case to be copied
• Migrate away from json type fields and extract mobility from case models
• Longer list of languages for cases to be translated into

Please :)

For editors: when an edgenote is removed from one card it should be easy to add it to another.

This also needs to change how an edgenote is created, as it’s gross to need to type in your slug in a little popup.

• Common chunks, at least
• Page level dynamic requires
  • Load only the overview when users aren’t signed in, at least

• The comment threads are “baked in” to the card if they are present when it is saved
• Comment threads are shifted if text is added or removed before their end index

• Discoverable cases
  • “Bottomless” featured pool (#113)
  • Map view (#133)
  • Keywords index (#192)
  • Library index (#193)
• Searchable cases
  • And filterable, and refinable (#194)
• Signed-out view that accomplishes platform marketing goals (#195)

Perhaps upvotes? Perhaps a engagement-based algorithm? How to mitigate pile-on effects? Should this apply equally to global communities and private ones?

• Rails
• React

• Add a file upload and icon field to Edgenote
  • Cap the file size lol
• Add an activity icon field to Page
• Change the function of the +Activity button to build a new page with “Instructions” card and sample Edgenote

Instructions

Use the attached file to...

• Attributes
• Format

Visible to all users of the case as metadata

• Keywords: “what kinds of classes is this useful for?”
• Learning objectives: clauses/bullet points
• Suggested audience: what background knowledge + resources for those missing that

Visible only to professors:

• Exercise instructions and answers
• Suggested classroom timeline: reference lengths for smallest indivisible chunks of activity, grouped into sets between which it's most smooth to take a break if needed.

Subtask of #111

• For each case and community pair
• Per case, integrating communities
• Per community, integrating cases
• Every message you can see?

Michigan Sustainability Cases should be added to the course navigation sidebar, which displays the case index. Additionally, a specific case should be offered as an “External Tool” for an Assignment, in which case the user should be granted an enrollment commensurate with their Canvas role.