Skip to content
This repository has been archived by the owner on Nov 7, 2019. It is now read-only.

Remove "uncrawlables" naming convention #17

Open
dcwalk opened this issue Aug 3, 2017 · 1 comment
Open

Remove "uncrawlables" naming convention #17

dcwalk opened this issue Aug 3, 2017 · 1 comment

Comments

@dcwalk
Copy link
Member

dcwalk commented Aug 3, 2017

From convo in #16 @b5:

Consensus is forming that our "uncrawlables" phrasing is a problem (@ebarry would also like to drop the uncrawlables phrase), and there are others that are worth considering. This a carry over from our Data Rescue work, and I'm totally down to change it. I'm hoping the next PR on this repo will be refactoring naming conventions, but I want to first write a glossary of terms (on a technical level) and then start a discussion from there about changing naming conventions moving forward.

@dcwalk dcwalk mentioned this issue Aug 3, 2017
@mhucka
Copy link

mhucka commented Aug 7, 2017

As far as a replacement for the term "uncrawlable" is unconcerned, here are some possible starting points. (Not saying these are good, just trying to start the creative process going!)

  • inaccessible
  • unharvestable
  • unparseable
  • uninterpretable
  • unspiderable

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

2 participants