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

Tco 69 data 2 #100

Closed
wants to merge 8 commits into from
Closed

Tco 69 data 2 #100

wants to merge 8 commits into from

Conversation

matt-bernhardt
Copy link
Member

Summary of changes (please refer to commit messages for full details)

Developer

Ticket(s)

https://mitlibraries.atlassian.net/browse/TCO-###

Accessibility

  • ANDI or Wave has been run in accordance to our guide and
    all issues introduced by these changes have been resolved or opened
    as new issues (link to those issues in the Pull Request details above)
  • There are no accessibility implications to this change

Documentation

  • Project documentation has been updated, and yard output previewed
  • No documentation changes are needed

ENV

  • All new ENV is documented in README.
  • All new ENV has been added to Heroku Pipeline, Staging and Prod.
  • ENV has not changed.

Stakeholders

  • Stakeholder approval has been confirmed
  • Stakeholder approval is not needed

Dependencies and migrations

YES | NO dependencies are updated

YES | NO migrations are included

Reviewer

Code

  • I have confirmed that the code works as intended.
  • Any CodeClimate issues have been fixed or confirmed as
    added technical debt.

Documentation

  • The commit message is clear and follows our guidelines
    (not just this pull request message).
  • The documentation has been updated or is unnecessary.
  • New dependencies are appropriate or there were no changes.

Testing

  • There are appropriate tests covering any new functionality.
  • No additional test coverage is required.

JPrevost and others added 8 commits August 29, 2024 14:09
Reword this...

tmp

best commit message evah

DO NOT MERGE: More verbose class diagram

The changes here are still workshopping how we want to handle the data
model - there isn't a single change that's being proposed yet.

Add validation to code approach diagram
This takes the different prototype class diagrams out of
docs/reference/classes.md and creates specific diagrams for
both prototypes (along with a "prototype zero" option that was
briefly considered and abandoned).

It also writes up a workflow document for using each
prototype, including sample code and output to try and
illustrate the ideas motivating each option.
This is the first step toward the Data prototype for a categorization / validation workflow.
I wanted this to be just a Detector class, but that was conflicting with
the Detector module name.
This also adds the Category field to the SuggestedResource model.
This should probably be squashed into the previous commit.

Side effect: some of the SuggestedResource tests are now failing.
There are evaluate_* methods on the Terms model
which will record link records in TermDetectinators
for which detectors activate on a given term.
@mitlib mitlib temporarily deployed to tacos-api-pipeline-pr-100 September 3, 2024 13:39 Inactive
@matt-bernhardt
Copy link
Member Author

matt-bernhardt commented Sep 9, 2024

This branch is no longer needed. It was a practice copy of one of the main prototypes which contributed to the choice of categorization strategy, but was not unique in itself.

@matt-bernhardt matt-bernhardt deleted the tco-69-data-2 branch September 9, 2024 14:20
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.

3 participants