-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Feature Request - agent addresses criteria/documentation #5413
Comments
Can we disallow urls containing "https://www.google.com/url?"? I think these are probably just mistakes in copying urls. |
Above four are corrected. |
I don't think documentation will fix this because I am pretty sure it is just people in a hurry copying the search url instead of the one they really wanted. |
Thanks @AJLinn for getting the Fairbanks Pioneer Home! |
Yes, but there are a LOT of not-very-useful URLs. I can't stop them all, expectations need made clear. This should be recognized as the social problem it is. (And it's much bigger than addresses).
Are you seriously arguing that the current documentation is adequately defining the kind of data we want?!
Verbatim agent exists for that. Of course mistakes will be made, expectations should still be clear. |
Above are fixed and code table change has been requested. Suggest we close. |
Issue Documentation is http://handbook.arctosdb.org/how_to/How-to-Use-Issues-in-Arctos.html
Is your feature request related to a problem? Please describe.
I noticed an agent with a google search results address. That's not useful, not stable, and I posit should not be allowed.
Describe what you're trying to accomplish
Require something meaningful as address.
Describe the solution you'd like
Cleanup, but mostly better documentation.
Describe alternatives you've considered
??
Additional context
This probably isn't limited to google search results, that's just what I noticed, the real need is to develop good documentation. (And I'm not sure what that should say - maybe something about 'specific'??)
Priority
High-ish? The 4 cruddy addresses aren't hurting much, but the docs should be made better ASAP.
Data
The text was updated successfully, but these errors were encountered: