 |
BOOK: ASP.NET 2.0 Website Programming Problem Design Solution ISBN: 978-0-7645-8464-0  | This is the forum to discuss the Wrox book ASP.NET 2.0 Website Programming: Problem - Design - Solution by Marco Bellinaso; ISBN: 9780764584640 |
|
Welcome to the p2p.wrox.com Forums.
You are currently viewing the BOOK: ASP.NET 2.0 Website Programming Problem Design Solution ISBN: 978-0-7645-8464-0 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
|
|
|
|
|

September 25th, 2007, 02:59 PM
|
|
Friend of Wrox
|
|
Join Date: Aug 2006
Posts: 142
Thanks: 0
Thanked 2 Times in 2 Posts
|
|
editor per page
Hi,
does anyone have a best practice on how to give 1 certain user editor rights for just 1 page ? (considering that you might have hundreds of different pages, meaning hundreds of different editors ?
tnx
koen
|
|

September 25th, 2007, 04:16 PM
|
|
Friend of Wrox
|
|
Join Date: Mar 2007
Posts: 488
Thanks: 2
Thanked 11 Times in 10 Posts
|
|
koen,
not sure if i understand the whole problem. do you mean 'one page' as in individually named pages such as ski1.aspx, ski2.aspx, goski1.aspx etc, etc.??
or, are you thinking along the lines of 'homepage' functionality per user??
if it's the latter, then i can certainly advise on that as i do just that for my originaltalent.com website (each user has a registered area where thay can add a biog, multimedia, articles, events, etc...).
i won't go into much more detail until i know what your exact requirement is on this one.
jimi
http://www.originaltalent.com
|
|

September 26th, 2007, 01:32 AM
|
|
Friend of Wrox
|
|
Join Date: Aug 2006
Posts: 142
Thanks: 0
Thanked 2 Times in 2 Posts
|
|
Hi jimi,
It's the first one : per page ski1.aspx, ski2.aspx, ....
the functionality you are mentioning looks nice too: this way I could have each users upload it's own pics etc.
all tips are welcome.
PS/ did you check my tagging solution ?
|
|

September 26th, 2007, 01:37 AM
|
|
Friend of Wrox
|
|
Join Date: Mar 2007
Posts: 488
Thanks: 2
Thanked 11 Times in 10 Posts
|
|
keon,
i'll 'think' of any tips and pass them on.
btw - what's the link to view the main tagging stuff, i'd love to take a look.
jimi
http://www.originaltalent.com
|
|

September 26th, 2007, 03:41 AM
|
|
Friend of Wrox
|
|
Join Date: Mar 2007
Posts: 488
Thanks: 2
Thanked 11 Times in 10 Posts
|
|
yes, (related articles), that's where generic tagging really becomes powerful. i suppose you could also 'score' the related articles by the number of matching tags, as well as the presence of any one or more matching tags. this, coupled with matching on 'key' content, would make for a very comprehensive search/tagging solution.
btw - did you add a 'tag' table as a seperate entity (keyed on articleID/ tagEntityType) or did you add a new freeform column onto the articles/posts table??
jimi
http://www.originaltalent.com
|
|

September 26th, 2007, 05:28 AM
|
|
Friend of Wrox
|
|
Join Date: Aug 2006
Posts: 142
Thanks: 0
Thanked 2 Times in 2 Posts
|
|
I actually just added an extra field in the articles list. not the best practice, but it is the easiest :)
|
|

September 26th, 2007, 05:58 AM
|
|
Friend of Wrox
|
|
Join Date: Mar 2007
Posts: 488
Thanks: 2
Thanked 11 Times in 10 Posts
|
|
keon - believe me, whatever get's the job done. 'nicities' (such as denormalising it) can be done later, if it proves to be beneficial (i.e. if you had a tags table, then you'd only need to search the tagField 'freetext' for any tags that matched articles, posts, user homepages etc, etc. of course, your tags table would have to be structured as such:
tagID, // just a table uniq id
tagField, // the list of comma separated tags
tagType, // an enum or the tablename that related to the tagfield
tagTypeID // the foriegn key linking the tags to the table/entity
as and when i get around to this area, this may or may not be the way that i'll approach it but for now, i think your approach is the most pragmatic.
jimi
http://www.originaltalent.com
|
|

September 26th, 2007, 07:12 AM
|
|
Friend of Wrox
|
|
Join Date: Mar 2007
Posts: 488
Thanks: 2
Thanked 11 Times in 10 Posts
|
|
keon,
getting back to the initial question here. if you're wanting to give your users access to edit multiple pages, then i think the best way fwd would be to have an admin table that contains:
pageName, // serverpath to page i.e. /faqs/whichskiboot.aspx
userID, // self explanatory
authorityLevel, // roles based i.e editor, moderator etc.. (tho not fully neccessary to make it all work)
valid_SttDate, // date at which user was given rights
valid_EndDate, // date when rights were removed (may default to 01/01/2041 for example)
noOfEdits, // cumulative count of edits performed on page for this user's management of it
lastEditDate // as it says on the tin
this would then allow you to give your users access to 'sets' of pages that they could edit. as the table is datetracked, it'd mean that you'd be able to keep a history of who was responsible for edits in a specific period. on loggin in, the user would see a list of pages that they had rights to edit (or moderate/approve etc). clicking on any of the links would validate their username against the entry and if all matched, then they'd be able to open the page in the appropriate mode for their authorityLevel on it.
i'm sure they're are better, more well thought out scenarios, but this one is consistant with how a lot of functions are managed in 'traditional' systems.
let me know what you think.
[edit] using the little site generator tool, i quickly put together a little site based on the above that could be integrated into your current site with a bit of tweaking:
http://www.originaltalent.com/downloads/TBH_AdHoc.zip
jimi
http://www.originaltalent.com
|
|

March 17th, 2009, 01:28 PM
|
|
Authorized User
|
|
Join Date: Feb 2009
Posts: 18
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Registered area for users
I am interested in learning how you implemented registered areas for your users. I tried to vist your website but could not get past the quick time movie.
Kind regards
Quote:
Originally Posted by jimibt
koen,
not sure if i understand the whole problem. do you mean 'one page' as in individually named pages such as ski1.aspx, ski2.aspx, goski1.aspx etc, etc.??
or, are you thinking along the lines of 'homepage' functionality per user??
if it's the latter, then i can certainly advise on that as i do just that for my originaltalent.com website (each user has a registered area where thay can add a biog, multimedia, articles, events, etc...).
i won't go into much more detail until i know what your exact requirement is on this one.
jimi
http://www.originaltalent.com
|
|
|
 |