03-13-2012, 11:35 PM
Dear mybest,
Although I made very few posts I must say that I'm following this rule before I've heard of it. I like it and agree with it.
The idea to provide just reference(link) in the request section has one great advantage: order.
e.g. I don't use search, I just browse, when I look in tekla products I see tekla software, tekla add-ons, tekla api. I hate to jump from requests to releases and so one. Also if release is posted in requests it's very likely that it will be missed by others.
There could be one issue, if the thread is modified, I think the reference would point nowhere.
e.g. Tekla products had lot's of threads until someone decided to clean it up. If those thread links were used in software requests now they point nowhere if not edited there also.
I think that your example has three parts rule 17 , rule 1 and a large number of unrelated material.
Rule 1 and 17 are great for "heavy" stuff. Like books, software, article collections.
But as stated by you there's some hard work for every article to make it look according to rule 1. And one article is "light" stuff many won't read it's title.
So I think that for short, not important articles rule 1 should not be fully applied. Article title, ISBN, author should be enough.
Some few ideas:
- Why having different sections releases and request why not just one single endless section of requests and releases? Answer should be order. rule 17
- Who will move releases from requests to the right sections? Answer should be uploader. rule 17 It would be heavy task for moderator.
Regards
Although I made very few posts I must say that I'm following this rule before I've heard of it. I like it and agree with it.
Code:
***************************************
Content of this section is hidden, You must be registered and activate your account to see this content. See this link to read how you can remove this limitation:
http://forum.civilea.com/thread-27464.html
***************************************
e.g. I don't use search, I just browse, when I look in tekla products I see tekla software, tekla add-ons, tekla api. I hate to jump from requests to releases and so one. Also if release is posted in requests it's very likely that it will be missed by others.
There could be one issue, if the thread is modified, I think the reference would point nowhere.
e.g. Tekla products had lot's of threads until someone decided to clean it up. If those thread links were used in software requests now they point nowhere if not edited there also.
I think that your example has three parts rule 17 , rule 1 and a large number of unrelated material.
Rule 1 and 17 are great for "heavy" stuff. Like books, software, article collections.
But as stated by you there's some hard work for every article to make it look according to rule 1. And one article is "light" stuff many won't read it's title.
So I think that for short, not important articles rule 1 should not be fully applied. Article title, ISBN, author should be enough.
Some few ideas:
- Why having different sections releases and request why not just one single endless section of requests and releases? Answer should be order. rule 17
- Who will move releases from requests to the right sections? Answer should be uploader. rule 17 It would be heavy task for moderator.
Regards