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

Extract signals from diff result #6

Closed
danielballan opened this issue Mar 3, 2017 · 7 comments
Closed

Extract signals from diff result #6

danielballan opened this issue Mar 3, 2017 · 7 comments

Comments

@danielballan
Copy link
Contributor

Summary of ideas (copied from PROPOSALS.md from NYC event)

Per row:

  • type of change
  • contains date
  • contains non-visible tag
  • contains any tag
  • contains number
  • contains link tag
  • total characters changed
  • (maybe!) NLP metrics like "edit distance"

Per document:

  • total characters changed
  • history (timing) of changes
@danielballan danielballan changed the title Extract signals from PF diff result Extract signals from diff result Oct 9, 2017
@danielballan danielballan added this to the Backlog milestone Oct 9, 2017
@stale
Copy link

stale bot commented Jan 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.

@stale stale bot added the stale label Jan 10, 2019
@Mr0grog
Copy link
Member

Mr0grog commented Jan 10, 2019

This is pretty tightly tied in with #175 and edgi-govdata-archiving/web-monitoring-db#416. We should consolidate. (Or break apart into very concrete individual items.)

@stale stale bot removed the stale label Jan 10, 2019
@Mr0grog Mr0grog added this to New/Triage in Web Monitoring May 23, 2019
@Mr0grog Mr0grog moved this from New/Triage to Icebox in Web Monitoring May 23, 2019
@stale
Copy link

stale bot commented Jul 9, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.

@stale stale bot added the stale label Jul 9, 2019
@stale stale bot removed the stale label Jul 15, 2019
@Mr0grog Mr0grog self-assigned this Jul 15, 2019
@Mr0grog
Copy link
Member

Mr0grog commented Jul 15, 2019

Prioritizing this for myself to do the aforementioned consolidation/breakup.

@stale
Copy link

stale bot commented Jan 11, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.

@stale stale bot added the stale label Jan 11, 2020
@Mr0grog
Copy link
Member

Mr0grog commented Jan 16, 2020

This is happening over on the web-monitoring-task-sheets repo.

@stale stale bot removed the stale label Jan 16, 2020
@stale
Copy link

stale bot commented Jul 15, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.

@stale stale bot added the stale label Jul 15, 2020
@stale stale bot closed this as completed Jul 23, 2020
Web Monitoring automation moved this from Icebox to Done! Jul 23, 2020
@Mr0grog Mr0grog removed the stale label Oct 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Web Monitoring
  
Done!
Development

No branches or pull requests

2 participants