autonoding

The foul practice of using a program to create nodes for you. Normaly it is done with reference books of some kind(like Webster 1913) but a few others exist (Everything Snapshot). Noders who do this, and the programs used, are both called Autonoders.

I prefer the more honest (if labour intensive) noding frenzies and HIMTN.

For the record, all MY Everything King James Bible writeups were laboriously submitted individually, by hand, because I do not know how to script ("autonode"). I feel that getting the complete work into the database is more important than making hardlinks as I go.
When I started doing Genesis, somebody (my regrets, I don't remember who) questioned whether my "gratuitous" links add value to the Bible. So now that's one vote for lots of links in assimilated doc's and one vote against.

If done with sensitivity, autonoding need not be a "foul practice".

A good autonoder would work like this:

• User marks up source material into nodes, giving each node a sensible name (e.g. "Luke 7:15" (qv)). Some hardlinks may be hand-inserted, but many may be ommitted.
• Script compares each word and each phrase of (say) three words or less, with its own list of nodenames, and if there is a match, converts the phrase into a hardlink.
• Script searches E2 for a node matching every word and every phrase (below a given length) in the document, and inserts hardlinks where appropriate. Stopwords would be required, and possibly some human intervention.
• A new login name is created for the autonoder, e.g. "Roger's Profanisaurus", so that:
  • Human does not take credit for autonoded content
  • Autonoded content is easily identifiable
  • Admin may delete autonoded content with a single SQL command if everything goes tits-up.
• Nodes are created.

Any old fool can export junk into E2: it takes effort to export quality nodes. (Effort which so far I have failed to stump up).