search

BenoitTalbot / bungeni-portal

Automatically exported from code.google.com/p/bungeni-portal
0 stars 0 forks source link

XML output of Bungeni Content Items #718

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
The motivation behind serializing Bungeni content items in XML format is to 
allow downstream provision of Bungeni content in other XML formats. 

Currently Bungeni content is created view a workflow process. The end point of 
the workflow results in content (questions, motions etc ) being "published".

Presently this publication results in the content being available for 
presentation on the web i.e. as a html page.

An extension to content publciation is required - whereby Bungeni content is 
explicitly published in XML format.

This XML format must provide all the information about the content being 
published :

 -- output XML must be canonical XML (see http://en.wikipedia.org/wiki/Canonical_XML)
 -- all the attributes of the content must be published
 -- all the attribute names must be retained , for e.g. if there is an attribute called full_title, the same name must be used to identify the content attribute in the XML.
 -- the permissions on the content item must also be published in the XML output.
 -- all the extended information about the content item must be published too :
     * list of workflow events, and all status information
     * list of attachments, and the attachments themselves
     * list of events, and the event information
     * list of any assignments of the item - e.g. if the content item was assigned to a committee

Original issue reported on code.google.com by ashok.ha...@gmail.com on 18 Jul 2011 at 1:34

GoogleCodeExporter commented 8 years ago 
The motivation behind serializing Bungeni content items in XML format is to 
allow downstream provision of Bungeni content in other XML formats. 

Currently Bungeni content is created view a workflow process. The end point of 
the workflow results in content (questions, motions etc ) being "published".

Presently this publication results in the content being available for 
presentation on the web i.e. as a html page.

An extension to content publciation is required - whereby Bungeni content is 
explicitly published in XML format.

This XML format must provide all the information about the content being 
published :

 -- output XML must be canonical XML (see http://en.wikipedia.org/wiki/Canonical_XML)
 -- all the attributes of the content must be published
 -- all the attribute names must be retained , for e.g. if there is an attribute called full_title, the same name must be used to identify the content attribute in the XML.
 -- the permissions on the content item must also be published in the XML output.
 -- all the extended information about the content item must be published too :
     * list of workflow events, and all status information
     * list of attachments, and the attachments themselves
     * list of events, and the event information
     * list of any assignments of the item - e.g. if the content item was assigned to a committee

Apart from Parliamentary content -- Parliamentary metadata also needs to be 
exportable to XML. Parliamentary metadata typically describes other information 
about the parliament :

 -- metadata about parliament
 -- metadata about users and membership
 -- metadata about groups and committees
 -- metadata about publications

Original comment by ashok.ha...@gmail.com on 19 Jul 2011 at 11:13

GoogleCodeExporter commented 8 years ago

Original comment by ashok.ha...@gmail.com on 24 Jul 2011 at 9:31

GoogleCodeExporter commented 8 years ago

Original comment by ashok.ha...@gmail.com on 27 Jul 2011 at 7:26

GoogleCodeExporter commented 8 years ago

Original comment by ashok.ha...@gmail.com on 27 Jul 2011 at 7:34

GoogleCodeExporter commented 8 years ago 
The motivation behind serializing Bungeni content items in XML format is to 
allow downstream provision of Bungeni content in other XML formats. 

Currently Bungeni content is created view a workflow process. The end point of 
the workflow results in content (questions, motions etc ) being "published".

Presently this publication results in the content being available for 
presentation on the web i.e. as a html page.

An extension to content publciation is required - whereby Bungeni content is 
explicitly published in XML format.

This XML format must provide all the information about the content being 
published :

 -- output XML must be canonical XML (see http://en.wikipedia.org/wiki/Canonical_XML)
 -- all the attributes of the content must be published
 -- all the attribute names must be retained , for e.g. if there is an attribute called full_title, the same name must be used to identify the content attribute in the XML.
 -- the permissions on the content item must also be published in the XML output.
 -- all the extended information about the content item must be published too :
     * list of workflow events, and all status information
     * list of attachments, and the attachments themselves
     * list of events, and the event information
     * list of any assignments of the item - e.g. if the content item was assigned to a committee
     * list of versions, and its metadata
     * list of auditlog events and its metadata

Apart from Parliamentary content -- Parliamentary metadata also needs to be 
exportable to XML. Parliamentary metadata typically describes other information 
about the parliament :

 -- metadata about parliament
 -- metadata about users and membership
 -- metadata about groups and committees
 -- metadata about publications

Original comment by ashok.ha...@gmail.com on 5 Sep 2011 at 1:40

GoogleCodeExporter commented 8 years ago 
Technical Summary :

Technical summary:
1) Create serialization utility that will take sqlobject as input and
will return XML representation including all available metadata and
all related objects (with relation depth = 1 e.g. only store fields of
related objects).
2) Create new workflow action 'publish to xml' that will use xml
serialization uitility to save XML representation of parliamentary
content. If object contains attachments it will be saved as zipped xml
packade that will include attached files. Every parlament will have
separate folder to store parliamentary content related to it. Each
type of parliamentary content should be saved have separate folder.
3) Create separate workflow action for parliament to store required metadata.

Original comment by ashok.ha...@gmail.com on 7 Sep 2011 at 11:47

GoogleCodeExporter commented 8 years ago

Original comment by ashok.ha...@gmail.com on 6 Oct 2011 at 7:33

GoogleCodeExporter commented 8 years ago

Original comment by ashok.ha...@gmail.com on 28 Nov 2011 at 6:01