next message in archive
next message in thread
previous message in archive
previous message in thread
Index of Subjects
Index of Subjects
Jeff;
I have reviewed the test url put forward, the font is small in some ways
however that could be fixed. I would like you to continue to put forth your
proposal and please provide me with a url of the "online editing" part of the
database for me and the area editors to review.
The fact that this will include the template and not have errors in it is
good, some pages on ccn are still not over to the new template and some pages
have had the template hard coded into it defeating it's purpose. Will this
System in the future be able to include other pages on ccn and just not editors
area databases (i.e. the Editor's Home page, CCN-IP home page, & etc.)?
The current Csuite editing procedure is out of date and using new programing
languages can help us to attract more volunteers. Keep up the good work.
Michael Cormier
EIC, CCN
Jeff Warnica wrote:
> Consider http://phoenix.chebucto.ns.ca/index.php3 as a proof of concept for
> a on-the-fly database driven yahoo style directory. Consequently: I only put
> in real data in the CS&D branch, and some of the top branches from that.
>
> When completed it could be a replacement to the manually edited 'info' tree
> on Chebucto. In addition to the necessary feature of online browsing, it
> will allow for online editing of pages (ie, from a web browser, no HTML
> skills necessary), and potentially a finer grained security model.
>
> This is simultaneously a 'heads up' to the editors/ipe/webmaster/eic to
> think about changing to this once it reaches a higher level of maturity, and
> a call for PHP/SQL hackers (or potential PHP/SQL hackers) to help me work on
> it.
>
> The advantages of pages being built on the fly are that they all conform to
> a definite standard template, with no opportunity for it to be mangled by
> humans.
>
> The advantage of it being built on a database are that the database could be
> exposed via different formats (ie RDF, XML), but there is a common
> repository for the data.
>
> The current plans for the security model are that a particular account could
> have (insert/modify/delete) access to a branch of the tree band down. Since
> at the DB level there is no difference between pages and links, a account
> could potentially only have permissions to modify one link.
>
> I would like a more finely grained security model (with any arbitrary per
> user access to branches of the tree, filters where access can be masked off
> for a branch... All the fun things from NDS :) )
>
> When I first started this there was some differences in the template, and
> different thoughts on sorting the links.
next message in archive
next message in thread
previous message in archive
previous message in thread
Index of Subjects