Details
-
New Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
Description
Currently we always turn a domain name "foobar.dk" into a seed "http://www.foobar.dk" on domain ingest. We should replace this with logic that always produces a seed that returns a 200. In some cases this may involve resolving redirects etc. Possibly/probably we should not do this at ingest time, but rather have a tool that runs the entire database over once in a while and fixes every default seed. We need to think about "default default" behaviour - ie what to do if we can't find a default seed for a domain.
Attachments
Issue Links
- duplicates
-
NASC-72 Verify new domains in NAS
- Open