kohsah/bungeni-exist

The eXist XML Db is used as a repository for AkomaNtoso documents by Bungeni. Bungeni is a suite of applications that provide a solution for drafting, managing, consolidating and publishing legislative and other parliamentary documents. It aims to increase the efficiency of parliamentary activities and make Parliaments more open and accessible to citizens -- virtually allowing them “inside the Parliament” or Bungeni, the Kiswahili word for “inside the Parliament”. Bungeni deals with the growing and challenging demands of increasing the efficiency of parliamentary activities and at the same time enabling Parliaments become more open to the citizens to foster accessibility, transparency and accountability of parliamentary activities.

bungeni-exist's Issues

Committing a single form does not provide a success or failure message

What steps will reproduce the problem?
1.save the roles form
2.click commit


What is the expected output? What do you see instead?
the roles get written to the file system, but no message is provided to the 
user.

Original issue reported on code.google.com by [email protected] on 8 Aug 2014 at 10:11

Add workflow button not working

What steps will reproduce the problem?
1.add a new type
2.add a form for the type
3.add a workflow for the type

What is the expected output? What do you see instead?

the add workflow screen must be shown, but nothing appears

Please use labels and text to provide additional information.

Original issue reported on code.google.com by [email protected] on 8 Aug 2014 at 10:20

PO file translation to XML broken on glue install

Seems to have broken since the glue changes for legislature->chamber structure

Original issue reported on code.google.com by [email protected] on 1 Oct 2014 at 6:07

Transformer pipeline does not support piping of style sheet level parameters

The Bungeni Transformer does not currently support piping of parameters, only 
output piping is supported.

TO DO : 

Support piping of parameters 

Original issue reported on code.google.com by [email protected] on 14 Nov 2011 at 2:46

Bungeni message strings and message Ids

We the case of translating literal strings on the XML portal -- i.e. the field 
labels. 

We have different kinds of message strings in the XML UI -- 

 1- the ones coming in html templates (these could be translated in place - by having different templates for different languages ) - and could also be scripted out by having placeholders for literal strings. This is easy to implement.

 2- there are literal strings that could be "shared" with bungeni . e.g. a question is entered in the bungeni workspace and also displayed in the bungnei workspace. There are message strings shown there rendered from Zope .po files. These could be used in eXist by converting the PO to xml and using the message ids as placeholders.  This is relatively more dificult to implement.

Original issue reported on code.google.com by [email protected] on 28 Oct 2011 at 1:44

Atom feed on listings

TO DO :

Implement a ATOM feed on  listings 

Original issue reported on code.google.com by [email protected] on 17 Nov 2011 at 9:41

appcontroller.xqm - route mapping action factor into configuration

currently appcontroller.xqm maps route paths to xquery actions. 

however there is a duplication here of code - the router path is repeated in 
ui-config.xml 

e.g. 
 <route href="/higher_house/question-version/text">
            <title>Business | Question Version Text</title>
            <navigation>/higher_house/business</navigation>
            <subnavigation>questions</subnavigation>
        </route>

and in appcontroller.xqm :

    else if ($CHAMBER-REL-PATH eq "/question-version/text" )
             then 
                   (: execute action :)
         ....


TO DO : map action into route configuration via a specific action 
configuration, and deprecate appcontroller.xqm: 

e.g. 
 <route href="/higher_house/question-version/text">
            <title>Business | Question Version Text</title>
            <navigation>/higher_house/business</navigation>
            <subnavigation>questions</subnavigation>
            <action>rou:get-question-version-text</action>
        </route>

Original issue reported on code.google.com by [email protected] on 6 Apr 2013 at 8:50

Rich Text content fields need to be safely unescaped

There are some fields (e.g. body_text) whose content is escaped html.

For these fields to be safely transported over into eXist they need to be 
unescaped + "tidy"-ed -- since unescaping does not guarantee that the html is 
clean since its user entered content.

To do:

Add a post-processing step to the transformer to unescape and cleanup specified 
fields.

Original issue reported on code.google.com by [email protected] on 28 Oct 2011 at 1:39

Title is set from the framework configuration

Currently the title for a page is always set from the framework configuration. 

This needs to be an override-able parameter settable from the controller.

Original issue reported on code.google.com by [email protected] on 11 Nov 2011 at 2:30

Search Implementation

The search implementation is described below.

1) Search configuration -- 

 * The search configuration must describe what fields are searchable on a content type. e.g. for a motion we should be able to specify  e.g.

<searchins>
    <searchin value="title" field="bu:shortName">Title</searchin>
    <searchin value="body" field="bu:body">Body</searchin>
    <searchin value="docno" field="bu:registryNumber">Doc No.</searchin>
</searchins>

which states that the title, body and docno are searchable.

value - is a short-identifier 
field - is the specific element / or attribute that we want to search for
the text in the element is the literal shown to the user.

the information in field is used to build the search query on the document 
dynamically. This is then eval-ed into a full-text search query.

2) Search behavior -- 

 - Search results must look like listings
 - Search results must be ordered based on the order-by parameter.

Logically the ordering should also be included in the search query eval, but 
this can be implemented separately. 

Original issue reported on code.google.com by [email protected] on 30 Nov 2011 at 2:54

Change information output needs cleanup

Change information outputin a document needs to be cleaned up.

Original issue reported on code.google.com by [email protected] on 11 Nov 2011 at 2:31

Paging implementation UI

The paging implementation currently displays ALL the individual pages as links.

However when the number of pages exceeds 15 pages, the UI becomes unmanageable 
i.e. too many links. 

TO DO :

 implement a scaled pager ,one that shows the first 6-7 pages and then shows links to access the next pages (or the previous 7 pages ) and also the first and last page.

Original issue reported on code.google.com by [email protected] on 14 Nov 2011 at 2:17