Dear all,
I'm new to the Voson wolrd - and I think it is simply awesome. I used other crawling sw but I ma liking Voson and NodeXL a lot and I am eager to learn.
I am using the sw mainly to map online networks starting from seed sites in the field of gender and media issues - a very fascinating global governance area, very underinvestigated. I have created a first database with 31 seed sites and specified some inbound and outbound parameter.. and ended up having my seed sites in the first ringset, the new sites (so many, but i am not surprised) in ringset 2... and 5 sites in a third ringset, which i am having trubles understanding. because inbound and outbound parameter were specified on my seed list - why am i finding a third ringset? these sites link to my seeds, but then why aren't they in the second ring?
also, i have pasted in the nodexl dialogue-box my list of seeds once and followed the procedure, but i find myself with 3 databases, not 1 as i expected, all of which contain the same number of nodes and were produced at the same time (i.e., same hours). why? i know with a free account i have 50 db i can produce so i'm kind of cautious using the tool for crawling...
I am sure i am missing something but, as i said, i'm new. forgive if i make silly questions.
best
elena
Hi Elena,
Thank you very much for your comments on VOSON!
About the ringset=3 question, I must admit I don't have an answer just as yet. You are quite right that if you have done just one crawl, then I would expect there wouldn't be any sites in ringset=3 (i.e. two 'jumps' from the seed set). We will need to investigate this.
But I have an answer to your question as to why there are additional databases automatically created in VOSON+NodeXL after a crawl is run. The answer is here (they are subsets of the network that people typically find useful and so we create them automatically for you):
http://www.uberlink.com/node/9#databases
I will get back to you about the ringset=3 sites, but it might take a bit of time.
Rob Ackland
Actually, the fact that these additional databases all have the same number of nodes indicates something is not correct. We will need to look at that. They should have different numbers of nodes.
Rob
This problem (auto-created additional networks all having the same number of nodes) should now be fixed.
Rob