[Building Sakai] Trying to fix SAK-17692/SAK-17694

Juan José Meroño Sánchez jjmerono at um.es
Thu Dec 9 02:55:41 PST 2010


  Hi this is Juanjo from Universidad de Murcia (Spain),

In order to fix the bug described in SAK-17692/SAK-17694 i suggest the 
following solution:

Create new sakai.properties like:

copyrightcode.count=6
copyrightcode.1=copy.fairuse
copyrightcode.2=copy.own
copyrightcode.3=copy.exception
copyrightcode.4=copy.permission
copyrightcode.5=copy.unknown
copyrightcode.6=copy.new
copyrightcode.default=copy.unknown
copyrightcode.own=copy.own
copyrightcode.new=copy.new

In the right.properties file appears the correct translation for the 
described codes.

If this properties are not present, sakai treats the copyrigtht  as it's 
doing right now, nothing changed. If you have more than one locale or if 
you made changes in any of the copyright status strings the bug is still 
present.

If properties are set, sakai uses the described codes to save the 
copyright status into the database, for new resources.

For resources already stored, it applies a dinamic strategy. When the 
resource is loaded in the edit metadata form (i didn't find any other 
use in the content tool), sakai translate the old string into the 
correct code dinamically (looking into the right.properties). If the 
resource changes,  the code will be stored (doing the database 
conversion on demand).

You can avoid this dinamic translation by creating a job or a database 
script in order to convert the oldest string into the correct code. 
Maybe not necesary as a first aproach, everything works with dinamic 
translation.

I will thank any feedback about that solution because i'm ready to 
upload the patch.

Bye !!

-- 
**************************************
Juan José Meroño Sánchez
Area de Tecnologías de la Información
y las Comunicaciones Aplicadas (ATICA)
http://www.um.es/atica
Universidad de Murcia
**************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20101209/2521a35d/attachment.html 


More information about the sakai-dev mailing list