Perma-Link for parliamentary items

[GoogleCodeExporter]

Requirement 
------------

A perma-link for Bungeni parliamentary items is required. The Akoma Ntoso URI 
naming convention provides a reference naming convention for bungeni.

For bungeni parliamentary content -- the URI is captured in the URI field.

The value of this field for the parliamentary content will calculated at the 
point of content creation or as an action during the content workflow. Once 
set, the URI is not changed for an item in subsequent workflows - and it 
becomes a permanent identifier for the object.

The URI is composed of the following -- 

country/entity code -- the country for which the bungeni installation is 
running.
(Note: there is no parameter to identify the running country /entity ) 
document type - bill, motion, question -- this information is available for a 
parliamentary item 
date -- there are many dates -- but what date do we use in the URI for 
different content types -- publication date ?(to be decided on a per content 
type basis ) 
number -- this should be the registry id -- the officially identified number of 
the question.
part name -- for most bungeni content, this will always default to main.
language code -- this is the language of the content.

Note :
1 - Since attributes like "date" may not be known when the question is in draft 
-- they will determined during a worfklow state - so the URI correspondingly 
must be set during a worfklow stage. Once a URI is set , it does not change.

2 - Bungeni does not track AN xml versions i.e. Bungeni versions are not AN xml 
versions, so Bungeni versions of a question will not follow the AN xml schema 
of version names. Bungeni content names only the final AN xml version 

currently bungeni items are refered via URLs like :

<http://localhost/business/questions/obj-23>

here 23 is an "identifier" of the question item in the db.
with the above changes there will also be a URI identifier for
question 23 :

(where 14 is the regisrtry id of the question)

/ke/question/2001-03-01/14/eng@/main

We need a permalink resolver that allows referencing a bungeni item via its 
URI, i.e. something like  :

<http://localhost/bungeni/ke/question/2001-03-01/14/eng@/main> shows the 
bungeni question 14 (i.e. the obj-23 question from above)

Original issue reported on code.google.com by ashok.ha...@gmail.com on 18 Apr 2011 at 12:12

[GoogleCodeExporter]

Something like "routes" (http://routes.groovie.org/ )  or trails ( 
http://pypi.python.org/pypi/megrok.trails ) seems to be a better way of mapping 
objects to URLs. The foreign key traversal is useful in some cases ... but 
clumsy and slow when we want to do things like the below case... so this url 
resolving method will be a parallel alternative to container base urls ...  

Original comment by ashok.ha...@gmail.com on 25 May 2011 at 8:30

[GoogleCodeExporter]

Original comment by ashok.ha...@gmail.com on 8 Jul 2011 at 11:21

• Changed state: TestingFix

[GoogleCodeExporter]

Fixed see r8337 , r8458

Original comment by ashok.ha...@gmail.com on 12 Mar 2012 at 2:06

• Changed state: Closed