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

Support appearances #20

Open
17 of 27 tasks
carlgieringer opened this issue Jul 10, 2021 · 3 comments
Open
17 of 27 tasks

Support appearances #20

carlgieringer opened this issue Jul 10, 2021 · 3 comments
Assignees
Labels
big issues Issues containing a lot of thought about an issue, often with unresolved next steps core domain Entities and core domain/business logic enhancement New feature or request
Milestone

Comments

@carlgieringer
Copy link
Contributor

carlgieringer commented Jul 10, 2021

An appearance is an assertion that an entity appears somewhere else. The entities would be:

Characteristics of appearances:

  • An appearance is justifiable (the entity does or does not appear in the locations represented conceptually by the locator(s) and citation(s).
  • Each appearance has a multiple location strategies that are justifiable. (the entity does or does not appear in this particular location.)

Main Feature

  • Create Appearance from MediaExcerpt
  • CreateAppearancePage/Editor
  • AppearancePage
  • Add AppearanceConfirmations
    • AppearanceConfirmationsService/AppearanceConfirmationsDao
    • Create an appearance when someone creates or duplicates an appearance
    • Add a UI to confirm an appearance
  • See a user's analysis of a source
    • Support searching for all Appearances by (URL, domain, or source) and Appearance creatorId.
    • Add links on AppearancePage to search for creatorId, and (URL or sourceId).
    • How to handle if another user already created the Appearance, but the current user wants it in their analysis? Include it if they have added justifications to the appearing proposition? Answer: add initial Appearance vote persistence where we add a (single unique) vote for an Appearance if the user readsOrCreates an Appearance. Then query based on positive-only votes (which will be the only polarity supported initially.)
  • ContextTrail: add Appearance connecting entity. For now the trails will start from a Media Excerpt only. Later they will start from Justifications, which could start from elsewhere.
  • MediaExcerptPage: list Appearances
  • Find a Proposition's Appearances
    • Search Appearances by appearingPropositionId
    • Add link to proposition appearances on PropositionPage
    • Add Appearances to PropositionUsagesPage

Later

  • AppearancePage:
    • list other Appearances for current Appearance's Proposition (apparition)
    • list other Propositions (apparitions) for current Appearance's MediaExcerpt
  • Navigate to an appearing Proposition from a MediaExcerpt basis #694
  • Support a visible scoring for Appearances in a list. Show whether the user/group agrees/disagrees/neither with each appearing proposition.
  • When navigating to Proposition Justifications from the list of Appearances, maintain the userIds filter so that the app prioritizes justifications relating to the fact check. Justifications from other users can be deprioritized (lower in ranking) or hidden behind a link "Other users have added justifications. Click here to show them." The query to select justifications must account for voting similar to how we account for appearance confirmations in the initial fact check.
  • Support Appearances as a justification target (omnijustifiable?) (Support omnijustifiables/omnivotables #35)
    • Show Appearance Justifications on AppearancePage
  • Browser in-context display of appearances on a page (one user or all.)
  • Support groups of people who are cooperating on a fact-check so that users can invite other users to the group and we can filter the appearances by group membership?
@carlgieringer carlgieringer added the enhancement New feature or request label Jul 10, 2021
@carlgieringer carlgieringer added this to the P1 milestone Jul 10, 2021
@carlgieringer carlgieringer added the core domain Entities and core domain/business logic label Jul 10, 2021
@carlgieringer
Copy link
Contributor Author

carlgieringer commented Jul 14, 2021

There appears to be a relationship between statements and appearances, since every appearance has a source and every source has some sort of author. Appearance can be for capturing something for critique, whereas a statement-based justification can be for constructing argument. What we don't need to duplicate are justifications for a statement and justifications for an appearance. The appearance would just be the justifications of the statement, but limited to a particular source or source-appearance/URL. (See hearsay comment below.)

Quote-based justifications could be thought of as 'lazy' statement-based justifications, where the capturer is not necessarily taking the time to pull out all of the propositions present in the quote, but instead is relying upon the aggregation of the quoted material's (implicit) propositions and the authority of the speaker and/or source.

@carlgieringer
Copy link
Contributor Author

What we don't need to duplicate are justifications for a statement and justifications for an appearance.

This is technically incorrect; it can be possible to justify a statement independently of an appearance of the statement when recording hearsay.

@carlgieringer carlgieringer self-assigned this Sep 24, 2022
@carlgieringer
Copy link
Contributor Author

carlgieringer commented Oct 4, 2022

(TODOs moved above.)

@carlgieringer carlgieringer linked a pull request Oct 4, 2022 that will close this issue
@carlgieringer carlgieringer moved this from Todo to In Progress in Add appearances Aug 12, 2023
@carlgieringer carlgieringer moved this from In Progress to Done in Add appearances Oct 27, 2023
@carlgieringer carlgieringer moved this from Done to In Progress in Add appearances Oct 27, 2023
@carlgieringer carlgieringer added the big issues Issues containing a lot of thought about an issue, often with unresolved next steps label Jul 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
big issues Issues containing a lot of thought about an issue, often with unresolved next steps core domain Entities and core domain/business logic enhancement New feature or request
Projects
Status: In Progress
Development

No branches or pull requests

1 participant