[WIP] Add uri logging to postgres normalized document #309
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
I would make this a new celery task and just make it an additional part of the pipe, I think. |
…crapi into feature/postgres_api
…o feature/url_logging
Member
Author
|
Moving development to #389 for some more generalized post processing of both URLs and Contributors together, adding a new postgres model instead of just sticking it in the normalized document |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
SHARE collects a lot of URIs, and it would be nice to also collect information about where those uris actually go. This is the begnings o f a processor that will follow those links and save information about their status, and where they resolve.
TODO
There is a lot to be done in order for this plan to be viable, most notably creating a central "control" system that keeps track of how many times we've hit a particular website with requests according to their terms of service.