I bought WSN Links 3.20 a few weeks ago. After installing i played around with the software. All right so far.
Now have to implement a Directory like DMOZ for a customer. As I saw there is no way to support the 'Narrow', 'Narrow1' etc tags in WSN. Which means for me that grouped subcategories are NOT possible with WSN. Right?
So i have a few questions: 1) Is it possible to build a high traffic website with e.g. 150.000 links?
2) How to realize DMOZ Style Directory with grouped subcategories based on the 'Narrow' tags?
3) what is a good strategy to build a DMOZ direcory? - Create categories manually or automated (i have a tool for parsing the RDFs, but i'm not sure if it's possible to map the tables...)? - I didn't see IDs for dmoz in the WSN tables. how to map DMOZ-IDs to WSN-IDs?
4) What can be done with 'category types'? - Is it possible to map 'Narrow'-tags from RDF-data to a custom category type in WSN? - How much category types are possible? - Why are category types limited to the Top Category?
Thanks in advance and greeting from Austria, crazyharry
1) 150,000 links isn't an amount if traffic. 150,000 links is easily supported. High traffic, however, requires progressively more powerful web hosting.
2) Subcategories can be grouped with category types. I do not, however, have any real idea of what a 'narrow' tag in DMOZ means so perhaps it's different.
3) What do you mean by "DMOZ-IDs"? As far as parsing the RDFs, I did start to convert a mysql version of the RDFs to WSN once, but mysql takes days to change a field name with that size of database.
4) I don't see any problem with changing the category type of a deep sublevel category.
ad 2) 'narrowed'-tags are references to other similar categories like recommendations. so thes are very interesting for the users.
maybe this can be realized using the 'related categories' feature. Right?
ad 3) sorry, i mean the 'category IDs' (catiID) of DEMOZ. I dont have an idea who to map the catIDs to IDs in WSN. From my understanding the orginal catIDs can't be used in WSN because the ID are automatically incemented my MySQL. Any Idea?
I dont want to alter the (Source-)table, because of the time consuming taks you mentioned. Instead of changing the table i want to write a script to 1) export the source records, 2) convert the record to the WSN format and 3) import to the WSN-table. Similar concept you used for the 'importer.php' script for importing LMA-data. :-)
Q: which are the required fields of the 'wsnlinks_links' table for bulk import(minimum required fields)? Q: which fileds are checked during the 'regenerate counters' process? Q: Is there any further documentation about the WSN datamodell?
crazyharry wrote: ad 2) 'narrowed'-tags are references to other similar categories like recommendations. so thes are very interesting for the users.
maybe this can be realized using the 'related categories' feature. Right?
Related categories will show a list of categories which have been marked as related.
ad 3) sorry, i mean the 'category IDs' (catiID) of DEMOZ. I dont have an idea who to map the catIDs to IDs in WSN. From my understanding the orginal catIDs can't be used in WSN because the ID are automatically incemented my MySQL. Any Idea?
I didn't think auto incriment prevented you from specifying your own id, but if it does you can turn off the auto incriment for a while until you're done importing.
Q: which are the required fields of the 'wsnlinks_links' table for bulk import(minimum required fields)?
The requirements are that the validated field needs to be set to 1 and the type field to 'regular' for links to show, and you have to have a category id. Outside of that it's a matter of what the source can provide. Presumably you'll be able to supply title, description, url.
Also you'll need to run regeneration after importing to get other fields like parentids filled in based on category data.
Q: which fileds are checked during the 'regenerate counters' process?
Checked? Basically it regenerates the values for everything that can be recalculated -- which means fields which are storing data about the category the link is in, the field storing the link owner's name, and fields related to comments on the link.
Q: Is there any further documentation about the WSN datamodell?
Not as far as would be useful for import scripts.
You should add items using the class, like this (it has the advantage of doing a few things automatically like setting a link type when you don't supply one): require 'classes/onelink.php'; $mylink = new onelink('new', 'new'); $mylink->title = 'title'; $mylink->url = 'http://something'; $mylink->catid = x; $mylink->validated = 1; $mylink->add(); // it's now added to the database
Comments on How to realize DMOZ Style Directory?
Beginner
Usergroup: Customer
Joined: Aug 27, 2005
Location: Austria
Total Topics: 2
Total Comments: 5
Hi there,
I bought WSN Links 3.20 a few weeks ago. After installing i played around with the software. All right so far.
Now have to implement a Directory like DMOZ for a customer. As I saw there is no way to support the 'Narrow', 'Narrow1' etc tags in WSN. Which means for me that grouped subcategories are NOT possible with WSN. Right?
So i have a few questions:
1) Is it possible to build a high traffic website with e.g. 150.000 links?
2) How to realize DMOZ Style Directory with grouped subcategories based on the 'Narrow' tags?
3) what is a good strategy to build a DMOZ direcory?
- Create categories manually or automated (i have a tool for parsing
the RDFs, but i'm not sure if it's possible to map the tables...)?
- I didn't see IDs for dmoz in the WSN tables. how to map DMOZ-IDs to
WSN-IDs?
4) What can be done with 'category types'?
- Is it possible to map 'Narrow'-tags from RDF-data to a custom category
type in WSN?
- How much category types are possible?
- Why are category types limited to the Top Category?
Thanks in advance and greeting from Austria,
crazyharry
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
1) 150,000 links isn't an amount if traffic. 150,000 links is easily supported. High traffic, however, requires progressively more powerful web hosting.
2) Subcategories can be grouped with category types. I do not, however, have any real idea of what a 'narrow' tag in DMOZ means so perhaps it's different.
3) What do you mean by "DMOZ-IDs"?
As far as parsing the RDFs, I did start to convert a mysql version of the RDFs to WSN once, but mysql takes days to change a field name with that size of database.
4) I don't see any problem with changing the category type of a deep sublevel category.
Beginner
Usergroup: Customer
Joined: Aug 27, 2005
Location: Austria
Total Topics: 2
Total Comments: 5
hi paul,
thanks for answering my questions.
ad 2) 'narrowed'-tags are references to other similar categories like recommendations. so thes are very interesting for the users.
maybe this can be realized using the 'related categories' feature. Right?
ad 3) sorry, i mean the 'category IDs' (catiID) of DEMOZ.
I dont have an idea who to map the catIDs to IDs in WSN. From my understanding the orginal catIDs can't be used in WSN because the ID are automatically incemented my MySQL. Any Idea?
I dont want to alter the (Source-)table, because of the time consuming taks you mentioned. Instead of changing the table i want to write a script to 1) export the source records, 2) convert the record to the WSN format and 3) import to the WSN-table. Similar concept you used for the 'importer.php' script for importing LMA-data. :-)
Q: which are the required fields of the 'wsnlinks_links' table for bulk import(minimum required fields)?
Q: which fileds are checked during the 'regenerate counters' process?
Q: Is there any further documentation about the WSN datamodell?
tanks and best regards,
crazyharry
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
ad 2) 'narrowed'-tags are references to other similar categories like recommendations. so thes are very interesting for the users.
maybe this can be realized using the 'related categories' feature. Right?
Related categories will show a list of categories which have been marked as related.
ad 3) sorry, i mean the 'category IDs' (catiID) of DEMOZ.
I dont have an idea who to map the catIDs to IDs in WSN. From my understanding the orginal catIDs can't be used in WSN because the ID are automatically incemented my MySQL. Any Idea?
I didn't think auto incriment prevented you from specifying your own id, but if it does you can turn off the auto incriment for a while until you're done importing.
Q: which are the required fields of the 'wsnlinks_links' table for bulk import(minimum required fields)?
The requirements are that the validated field needs to be set to 1 and the type field to 'regular' for links to show, and you have to have a category id. Outside of that it's a matter of what the source can provide. Presumably you'll be able to supply title, description, url.
Also you'll need to run regeneration after importing to get other fields like parentids filled in based on category data.
Q: which fileds are checked during the 'regenerate counters' process?
Checked? Basically it regenerates the values for everything that can be recalculated -- which means fields which are storing data about the category the link is in, the field storing the link owner's name, and fields related to comments on the link.
Q: Is there any further documentation about the WSN datamodell?
Not as far as would be useful for import scripts.
You should add items using the class, like this (it has the advantage of doing a few things automatically like setting a link type when you don't supply one):
require 'classes/onelink.php';
$mylink = new onelink('new', 'new');
$mylink->title = 'title';
$mylink->url = 'http://something';
$mylink->catid = x;
$mylink->validated = 1;
$mylink->add(); // it's now added to the database
Beginner
Usergroup: Customer
Joined: Aug 27, 2005
Location: Austria
Total Topics: 2
Total Comments: 5
hi paul,
thank you for your reply and your very helpful information.
best regard,
crazyharry