On 29 Dec, [EMAIL PROTECTED] wrote:
> Type can be used as a filter with mgd_list_topic_articles. The function
> reference axplains it I think. I have no idea what the ids are, either.
> The extra fields have no midgard-specific purpose, you can use them
> as you like.
The IDs in articles are a legacy feature from pre-1.0 Midgard.
We used it to link articles into image files in a picture
archive site. These days, using the attachment mechanism is
probably a better idea.
> The scoring can be used in the _list_ functions to specify in what
> order you want your articles or topics returned when you fetch them.
Also, you can use scoring to give some valuation to documents.
For example, you can determine with scoring which articles
are 'top stories of the week' or something...
> The approved and locked fields can be set by mgd_article_toggle_lock
> and mgd_approve_article. These fields can be used for workflow management
> (i.e. only displaying articles that are approved, not allowing updates
> if an article is locked) but you'll have to use PHP code to do anything
> with them. Updating a locked article is not prohibited by Midgard,
> but you can build an admin site that enforces it.
Yes, this is pretty much how we think it should be. There
is now sense to build any artificial workflow features into
Midgard itself, but rather leave it all into the application
level and just provide some useful mechanisms for application
writers.
Of course, with the packaging feature of Midgard 2, expect to
see example workflow applications starting to emerge. After
that creating a real content management system on Midgard
won't be that difficult anymore.
> Emile
/Bergie
--
-- Henri Bergius -- +358 40 525 1334 -- [EMAIL PROTECTED] --
http://www.iki.fi/Henri.Bergius
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
