On Thu, 30 Jun 2005, Gevik Babakhani wrote:
> Dear All,
>
>
>
> I would like to start a discussion regarding the content information and
> structure we would like to have in PGDN.
>
> Here is the proposal:
>
>
>
> The content in PGDN has the following:
>
> 1. Content id (of course) (sequence generated number)
we need two id's once we allow updating document. One is a pub_id -
publicly accessed persistent id and msg_id - internal id.
>
> 2. Author (user or author id)
>
>
>
> 3. major version (numeric like 3)
>
> 4. minor version (numeric like 2
>
> 5. revision. (numeric like 5)
>
> This makes a document version of 3.2.5
>
>
>
> 6. content applies to a PostgreSQL version. (varchar) (like "all pg
> versions", "8.x","7.x"
>
> 7. title (varchar)
>
> 8. A short description (varchar) (this would be the content introduction)
>
> 9. status (varchar) (E for editing for published, R for rejected)
>
> 10. the actual content or the story
>
> 11. date created
>
> 12. date updated
>
> 13. content type (like how-to, article, tutorial, etc ..)
>
>
>
> Do we need more information about a PGDN content? Please let me know what
> you think.
>
>
>
> Ps. the category and the keywords of the content are saved elsewhere.
>
>
>
> Regards,
>
> Gevik.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
