proprietary metadata configuration

[Ashok Hariharan]

I have added preliminary support for proprietary metadata setup via configuration.

These 2 pages on the wiki describe the changes :

http://code.google.com/p/bungeni-editor/wiki/DocTypeDefinition
http://code.google.com/p/bungeni-editor/wiki/SectionTypeDefinition

You will need to change the doc_types configuration and the section_types configuration appropriately for these updates to work .

There have also been various changes to the structure of the configuration folders ...what will perhaps affect you is the change of structure within config/system where I have reogranized the shipped XSLTs which are used by the middleware generator.. if you compare this structure :

http://bungeni-editor.googlecode.com/svn/BungeniEditor_configs/development_configs/system/

with your config folder you will get an idea of the changes. Importantly, the external imports within system/transformer/xsl have been remapped (and the XSLTs in there have been updated with various bug fixes ) .

There are still a couple of bugs in the proprietary metadata generation (no way to specify a  @source , nor does it support nested metadata setting .. but i will fix both today ) .

Ashok

[Ashok Hariharan]

I have added a further fix now to support nested proprietary metadata e.g

<proprietary source="#parliament" xmlns:bg="http://proprietary.org">
<bg:mymeta group="alpha">
   <bg:person name="Beta Charlie" />
      <bg:Age>33</bg:Age>
   </bg:person>
</bg:myeta>

[Samar Ayesh]

It's clear now how can I connect section-types with generated metadata tags , and how to use proprietary as a namespace
but what I need is to generate proprietary metadata such as frbrwork, expression, man with no relation to section-types...
how can I implement this?

[Ashok Hariharan]

On 11 December 2012 15:50, Samar Ayesh <smr....@gmail.com> wrote:

It's clear now how can I connect section-types with generated metadata tags , and how to use proprietary as a namespace
but what I need is to generate proprietary metadata such as frbrwork, expression, man with no relation to section-types...

What do you mean by that ... ? frbrwork is not proprietary metadata ,... but is core metadata
 
Ashok

how can I implement this?

On Thursday, December 6, 2012 10:02:44 AM UTC+2, Ashok Hariharan wrote:

I have added preliminary support for proprietary metadata setup via configuration.

These 2 pages on the wiki describe the changes :

http://code.google.com/p/bungeni-editor/wiki/DocTypeDefinition
http://code.google.com/p/bungeni-editor/wiki/SectionTypeDefinition

You will need to change the doc_types configuration and the section_types configuration appropriately for these updates to work .

There have also been various changes to the structure of the configuration folders ...what will perhaps affect you is the change of structure within config/system where I have reogranized the shipped XSLTs which are used by the middleware generator.. if you compare this structure :

http://bungeni-editor.googlecode.com/svn/BungeniEditor_configs/development_configs/system/

with your config folder you will get an idea of the changes. Importantly, the external imports within system/transformer/xsl have been remapped (and the XSLTs in there have been updated with various bug fixes ) .

There are still a couple of bugs in the proprietary metadata generation (no way to specify a  @source , nor does it support nested metadata setting .. but i will fix both today ) .

Ashok

--
You received this message because you are subscribed to the Google Groups "bungeni-editor" group.
To view this discussion on the web visit https://groups.google.com/d/msg/bungeni-editor/-/LaCxyCbLafUJ.
To post to this group, send email to bungeni...@googlegroups.com.
To unsubscribe from this group, send email to bungeni-edito...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bungeni-editor?hl=en.

[Samar Ayesh]

What I meant is that I need to add proprietary metadata that is not related to any section type .. I think I can add it to root sectionType

[Ashok Hariharan]

On 13 December 2012 10:19, Samar Ayesh <smr....@gmail.com> wrote:
> What I meant is that I need to add proprietary metadata that is not related
> to any section type .. I think I can add it to root sectionType
>

Yeah the logical place would be root section

> https://groups.google.com/d/msg/bungeni-editor/-/stpGD33NvvoJ.

[Samar Ayesh]

till now I didn't get metadata namespaces to work ...
I have tried speech and import question in debate-record

<sectionType name="Speech"
    prefix="speech"
    numstyle="serial"
    background="url:backgrounds/shade-1.png"
    indent-left=".6"
    indent-right="0"
    visibility="user" >
     <metadatas>
         <metadata name="BungeniSpeechBy" />
         <metadata name="BungeniSpeechByURI" />
         <metadata name="BungeniSpeechAs" />
         <metadata name="BungeniSpeechAsDesc" />
         <metadata name="BungeniSpeechAsURI" />
         <metadata name="BungeniPersonId" />
         <metadata name="BungeniPersonRole" />
     </metadatas>
     <output>
         <meta>
             <references>
               <an:TLCPerson id="$BungeniPersonID" href="$BungeniSpeechByURI" showAs="$BungeniSpeechBy" />
               <an:TLCRole id="$BungeniSpeechAs" href="$BungeniSpeechAsURI" showAs="$BungeniSpeechAsDesc" />
             </references>
             <proprietary ns="bg" xmlns:bg="http://prop.org" >
                 <bg:meta person="$BungeniSpeechBy" />
             </proprietary>
....

but there's no output either in metadata or content !!

[Ashok Hariharan]

Is your config folder all in svn ? 

Ashok

To view this discussion on the web visit https://groups.google.com/d/msg/bungeni-editor/-/xSjYgidDE-UJ.

[Ashok Hariharan]

Also tell me what you see in this file : 

birzeit_configs/system/errors/config_generator_errors.xml ? 

[Ashok Hariharan]

I noticed in your doc_types.xml : 

    <outputs>
        <namespace prefix="an" type="main" desc="Akoma Ntoso" uri="http://www.akomantoso.org/2.0" />
        <namespace prefix="muqid" type="proprietary" desc="Proprietary" uri="http://www.proprietary.org" />        
    </outputs>

You need to declare the "bg" namespace there if you want to use it otherwise use 'muqid' since its declared 

On 20 December 2012 12:00, Samar Ayesh <smr....@gmail.com> wrote:

To view this discussion on the web visit https://groups.google.com/d/msg/bungeni-editor/-/xSjYgidDE-UJ.

[Samar Ayesh]

how can I be sure that my config folder (birzeit_configs) is on svn?

when I do a commit for the whole folder a message appears
 (svn: E175005: Path '/svn/BungeniEditor_configs/birzeit_configs/system/errors' already exists
==[IDE]== Dec 22, 2012 9:22:53 AM Committing... finished.)

how can I commit it all?

I changed the prefix to muqid .. but I'm trying metadata in debaterecord in development_configs, but it didn't work with me !!

TLCPerson and TLCRole didn't appear in xml file !
also sectionTypes are not there !
even though I did update for the alldev folder ..

this message (<?xml version="1.0" encoding="UTF-8"?>
                      <errors date="Sat Dec 22 09:24:59 IST 2012" />
                        )
is written in config_generator_errors under development_configs/system/

errors/

[Flavio Zeni]

Dear Samar,

                just to say that Ashok will be on leave till first week of January 2013.

Let me take this opportunity to wish you all an Happy New Year.

Flavio

To view this discussion on the web visit https://groups.google.com/d/msg/bungeni-editor/-/G3q4YoaZp-sJ.

[Samar Ayesh]

aha ..
Happy new year Flavio :)

--

 ___________________________
 Samar Ayesh

[Ashok Hariharan]

Hi Samar --

Can you zip your birzeit_configs folder and email it to me ? You seem to have some folders in svn which shuold not be there and some modifications which need to be factored into an import xsl ... I can fix that for you ...

Ashok

To view this discussion on the web visit https://groups.google.com/d/msg/bungeni-editor/-/G3q4YoaZp-sJ.

[Ashok Hariharan]

Havent got it again ! same message ... can you send the attachment from your gmail account ? that should not be filtered ...

Ashok

On 8 January 2013 12:18, <say...@birzeit.edu> wrote:

try now .. the problem may be with .rar file .

On Tue, Jan 8, 2013 at 10:28 AM, <as...@parliaments.info> wrote:

Hi Samar -- didnt get it again ! your email system seems to remove attachments ... can you upload it to google docs and share the file , i can download it that way

On 8 January 2013 11:13, <say...@birzeit.edu> wrote:

here it is ..

On Mon, Jan 7, 2013 at 11:49 PM, <as...@parliaments.info> wrote:

Hi Samar --

I didnt get the attachment - i got this message below (can you send it as a zip file ) :

                                           
                                             
This is a message from the MailScanner E-Mail Virus Protection Service
----------------------------------------------------------------------
The original e-mail attachment "birzeit_configs.rar"
is on the list of unacceptable attachments for this site and has been
replaced by this warning message.

If you wish to receive a copy of the original attachment, please
e-mail helpdesk and include the whole of this message
in your request. Alternatively, you can call them, with
the contents of this message to hand when you call.

At Mon Jan  7 23:35:35 2013 the virus scanner said:
   MailScanner: Attempt to hide real filename extension (externals.txt.tmp)

Note to Help Desk: Look on the BZU (mailgw) MailScanner in /var/spool/MailScanner/quarantine/20130107 (message 9D2FB31AEED.A83C3).
-- 
Postmaster
Birzeit University
www.birzeit.edu

On 8 January 2013 00:35, <say...@birzeit.edu> wrote:

Happy New Year Ashok ..

attached birzeit_configs.rar
but I tried sectionTypes from development_configs folder that have to set metadata related to AN namespace but they didn't work !

[Ashok Hariharan]

Hi Samar -- 

I commitedin a corrected birzeit configuration (http://code.google.com/p/bungeni-editor/source/detail?r=2856 ) -- the main problem was in the configuration of the inline type ... ( i had to edit out some of your Act metadata configurators since I dont have your datasources here ) , so lets look at it step by step -- the configuration fix was minimal --  but i have gone ahead and done a dummy implementation for you that works -- see attached odt and xml .. 

From : http://bungeni-editor.googlecode.com/svn/BungeniEditor_configs/bz_configs/inline_types/act.xml

<?xml version="1.0" encoding="UTF-8"?>
<inlineTypes for="act" xmlns:an="http://www.akomantos.org/2.0">

    <!-- ASHOK old wrong configuration -->
    <!--<inlineType name="ref">
       <output>
          <metadatas>
             <metadata name="BungeniRefURI" />
          </metadatas>
          <meta>
              <TLCPerson id="$BungeniRefURI" />
          </meta>
          <content>
            <an:ref href="$BungeniRefURI" />
          </content>
       </output>
    </inlineType>
    -->
    <!-- ASHOK correct configuration -->
    <inlineType name="refPerson">
          <metadatas>
             <metadata name="BungeniPersonURI" />
             <metadata name="BungeniPersonID" />
             <metadata name="BungeniPersonFullName" />
          </metadatas>
          <output>   
              <meta>
                  <references>
                    <an:TLCPerson id="$BungeniPersonID" href="$BungeniPersonURI" as="$BungeniPersonFullName" />
                  </references>
              </meta>
              <content>
                 <an:ref href="#$BungeniPersonID" />
               </content>
          </output>
    </inlineType>

If you notice the commented configuration above -- you will see : 

       <output>
          <metadatas>
             <metadata name="BungeniRefURI" />
          </metadatas>
          <meta>
              <TLCPerson id="$BungeniRefURI" />
          </meta>
          <content>
            <an:ref href="$BungeniRefURI" />
          </content>
       </output>

Instead it should have been as specified in the second part (the <metadatas> element out of the <output> element, and TLCPerson needs to be wrapped in <references> element  ).. I need to document this better on the wiki - and also add some checks via a schema validator on the configuration .  

I have also implemented an example connector dialog that is loaded which sets the metadata on the inline  : 


http://bungeni-editor.googlecode.com/svn/BungeniEditor/trunk/BungeniEditorClient/src/org/bungeni/editor/selectors/act/PersonRefInline.java


the key part here is :


 class Person {
        String name; 
        String uri;
        String id;
        public Person(String name, String uri, String id){
            this.name = name;
            this.uri = uri;
            this.id = id;
        }
        @Override
        public String toString(){
            return name;
        }
    }
    
    List<Person> persons = new ArrayList<Person>(){
        {
           add(new Person("Samar Ayesh", "/ontology/Person/pl/Birzeit/2013", "unique-id-2013"));
           add(new Person("John Smith", "/ontology/Person/pl/SmithLand/2014", "unique-id-2014"));
           add(new Person("James Mango", "/ontology/Person/pl/MangoLand/2015", "unique-id-2015"));
        }
    };
    
    @Override
    public void commonInitFields(){
            DefaultComboBoxModel model = new DefaultComboBoxModel(persons.toArray());
            this.cboPersons.setModel(model);
    }

Which loads the combobox with some metadata that the user can select , and the processSelectInsert() API implementation that applies the selected metadata into the document : 


    @Override
    public boolean processSelectInsert() {
        // this gets you the container section name 
          OOComponentHelper ooDoc = getContainerPanel().getOoDocument();
          Person aPerson = (Person) cboPersons.getSelectedItem();
          CommonRouterActions.TypeCreationState tcs = getContainerPanel().initInlineType();
          if (tcs.propsMap != null ) {
             tcs.propsMap.put("BungeniPersonURI", aPerson.uri );
             tcs.propsMap.put("BungeniPersonID", aPerson.id );
             tcs.propsMap.put("BungeniPersonFullName", aPerson.name );
             ooDoc.setSelectedTextAttributes(tcs.propsMap);
          }
        return true;
    }
. 



This dialog is invoked via the toolbar action : 



http://bungeni-editor.googlecode.com/svn/BungeniEditor_configs/bz_configs/actions/toolbar_actions/act.xml


I have implemented a dummy action in the preface : 

   <blockAction title="PREFACE">
                <subaction tooltip="CREATE_PREFACE_FROM_SELECTION" target="make_act_preface"
                           condition="textSelected:true"
                           title="CREATE_PREFACE_FROM_SELECTION" >
                </subaction>
            
                <subaction tooltip="LONGTITLE" target="make_preface_longTitle"
                           condition="cursorInSection:preface :and: textSelected:true :and: sectionNotExists:longTitle"
                           title="LONGTITLE">
                </subaction> 

                <!--ASHOK to to test adding dialog metadata setter to reference -->
                <subaction tooltipe="MARK_REF_PERSON" target="mark_refperson"
                    condition="cursorInSection:preface :and: textSelected:true"
                    title="MARK_REF_PERSON" />

The target action router  -- 


    <action name="mark_refperson" source="inlineType" metadata="refPerson">
        <router class="org.bungeni.editor.actions.routers.routerInputReference" 
                dialog="refperson"
            />
    </action>

Which in turn invokes our implemented DIalog (selector_dialogs.xml)  : 

 <dialog id="refperson" class="org.bungeni.editor.selectors.act.Main" >
        <dialog
            class="org.bungeni.editor.selectors.act.PersonRefInline"
             />
    </dialog>

[Ashok Hariharan]

Hi Samar -

Let me update my example implementation to have proprietary metadata.

Secondly - I will add a step-by-step tutorial to the wiki - since the current XML configuration doesnt talk about implementation...

Ashok

On 10 January 2013 15:30, <say...@birzeit.edu> wrote:

Thanks alot Ashok , ref inlineType and it's metadata is working correctly now ...

but I need to add all my metadata fields as proprietary into meta section ..
I tried to edit on section_types/act.xml for meta section ...

<sectionType name="meta"
                 prefix="meta"
                 numstyle="single">
        <metadatas>
            <metadata name="ActSourceNo" />
        </metadatas>
        <output> 
            <meta>            

                 <proprietary source="#muq"  xmlns:muqid="http://muqtafi.birzeit.edu/proprietary">

                       <muqid:AdditionalInfo>

                           <muqid:SourceNo>$ActSourceNo</muqid:SourceNo>

                      </muqid:AdditionalInfo>

                 </proprietary>
            </meta>
            <content>
                <an:meta/>
            </content>
        </output>
    </sectionType>
I have those lines in doc_types.xml

     <outputs>
        <namespace prefix="an" type="main" desc="Akoma Ntoso" uri="http://www.akomantoso.org/2.0" />
        <namespace prefix="muqid" type="proprietary" desc="Proprietary" uri="http://www.proprietary.org" />       
    </outputs>

when I did that exporting to xml failed !!
how can fix this problem and have what I want ?

[Ashok Hariharan]

On 10 January 2013 15:30, <say...@birzeit.edu> wrote:

Thanks alot Ashok , ref inlineType and it's metadata is working correctly now ...

but I need to add all my metadata fields as proprietary into meta section ..
I tried to edit on section_types/act.xml for meta section ...

Hang on ... sectionType = meta is just a virtual placeholder used by the system - there should be no code in there ...
 
Instead of the below you need to something like  (i have used the same example from the bz_configs config folder :

    <inlineType name="refPerson">
          <metadatas>
             <metadata name="BungeniPersonURI" />
             <metadata name="BungeniPersonID" />
             <metadata name="BungeniPersonFullName" />
          </metadatas>
          <output>  
              <meta>
                  <references>
                    <an:TLCPerson id="$BungeniPersonID" href="$BungeniPersonURI" as="$BungeniPersonFullName" />
                  </references>

                  <proprietary ns="muqid" xmlns:muqid="#muqid" >
                    <muqid:additionalInfo>
                        <muqid:meta person="$BungeniFullName" />
                    </muqid:additionalInfo>
                  </proprietary>

              </meta>
              <content>
                 <an:ref href="#$BungeniPersonID" />
               </content>
          </output>
    </inlineType>

Is that clearer ?

<sectionType name="meta"
                 prefix="meta"
                 numstyle="single">
        <metadatas>
            <metadata name="ActSourceNo" />
        </metadatas>
        <output> 
            <meta>            

                 <proprietary source="#muq"  xmlns:muqid="http://muqtafi.birzeit.edu/proprietary">

                       <muqid:AdditionalInfo>

                           <muqid:SourceNo>$ActSourceNo</muqid:SourceNo>

                      </muqid:AdditionalInfo>

                 </proprietary>
            </meta>
            <content>
                <an:meta/>
            </content>
        </output>
    </sectionType>

I have those lines in doc_types.xml

     <outputs>
        <namespace prefix="an" type="main" desc="Akoma Ntoso" uri="http://www.akomantoso.org/2.0" />
        <namespace prefix="muqid" type="proprietary" desc="Proprietary" uri="http://www.proprietary.org" />       
    </outputs>

when I did that exporting to xml failed !!
how can fix this problem and have what I want ?

On Wed, Jan 9, 2013 at 4:46 PM, Ashok Hariharan <as...@parliaments.info> wrote:

[Samar Ayesh]

aha I know that it is possible with ref ..or any other inlineType, but what about if i needed it to appear every time ...
This the case:
I have my metadata fields filled at the beginning when bungeni starts, when metadata panels appear ..
I need those metadata fields to be present into meta section every time as proprietary tags as shown above for "SourceNo".. with no relation to any sectionType or inlineType.

--
You received this message because you are subscribed to the Google Groups "bungeni-editor" group.

To post to this group, send email to bungeni...@googlegroups.com.
To unsubscribe from this group, send email to bungeni-edito...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bungeni-editor?hl=en.

--

 ___________________________
 Samar Ayesh

[Ashok Hariharan]

On 11 January 2013 19:12, Samar Ayesh <smr....@gmail.com> wrote:

aha I know that it is possible with ref ..or any other inlineType, but what about if i needed it to appear every time ...
This the case:
I have my metadata fields filled at the beginning when bungeni starts, when metadata panels appear ..
I need those metadata fields to be present into meta section every time as proprietary tags as shown above for "SourceNo".. with no relation to any sectionType or inlineType.

OK -- I see what you mean -- let me see how it can be done. One way I know it can be done even now is to do it the way I described - via a inlineType or SectionType action - since in the router class you have access to all the metadata (even from the document level not just inline or section level ) - so you could via an extended router class, map the doc level metadata to the section metadata - and that will get output as proprietary header metadata.  However - i think there is a easier way to implement this in the middleware - let me get back to you ...
 

[Ashok Hariharan]

On 12 January 2013 00:22, Ashok Hariharan <as...@parliaments.info> wrote:

On 11 January 2013 19:12, Samar Ayesh <smr....@gmail.com> wrote:

aha I know that it is possible with ref ..or any other inlineType, but what about if i needed it to appear every time ...
This the case:
I have my metadata fields filled at the beginning when bungeni starts, when metadata panels appear ..
I need those metadata fields to be present into meta section every time as proprietary tags as shown above for "SourceNo".. with no relation to any sectionType or inlineType.

OK -- I see what you mean -- let me see how it can be done. One way I know it can be done even now is to do it the way I described - via a inlineType or SectionType action - since in the router class you have access to all the metadata (even from the document level not just inline or section level ) - so you could via an extended router class, map the doc level metadata to the section metadata - and that will get output as proprietary header metadata. 

This method is currently possible as a workaround ... but you have to write an extended router class... 

 

However - i think there is a easier way to implement this in the middleware - let me get back to you ...

I took a look at option (2)   now .. I can add support for this for pulling in global metadata (set at the document level ) via configuration... by perhaps next week, since I am working on a few other things at the moment. In this method you would not need to write any code, but it would pull in the required metadata via configuration.

Ashok

[Ashok Hariharan]

On 14 January 2013 12:10, Samar Ayesh <say...@birzeit.edu> wrote:

Aha .. You mean that by this configuration, metadata will be pulled out from metadata panels into xml generated AN file automatically ?

Exactly ... the info you see in the metadata panels is actually stored in the document... and i will add support to pull into meta directly.

If you open a marked up openoffice document and go to file-> properties in the openoffice menu - you will see your metadata shown as "custom properties". These are different from the metadata that you apply during markup which is usually on selected text these get embedded into the document but are captured per selection (and these you can find in the metadata/metadata.rdf file within the ODF file if you rename it to .zip file and view it. 

The other way i mentioned to do it right now -- was to extend the main router class and map the document metadata into the section metadata ... something like :

ooDocMetadata oodocMeta = new ooDocMetadata(ooDoc);

String actType = oodocMeta.GetProperty("BungeniActType");

        if (tcs.propsMap != null ) {

             tcs.propsMap.put("BungeniActType", actType);

             tcs.propsMap.put("BungeniPersonURI", aPerson.uri );

             tcs.propsMap.put("BungeniPersonID", aPerson.id );

             tcs.propsMap.put("BungeniPersonFullName", aPerson.name );

             ooDoc.setSelectedTextAttributes(tcs.propsMap);

          }

...

This way you can specify BungeniActType in the section type configuration and use it there to map it to meta .. 

ooDocument.setSectionMetadataAttributes(

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The University is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[Samar Ayesh]

Aha .. You mean that by this configuration, metadata will be pulled out from metadata panels into xml generated AN file automatically ?

[Samar Ayesh]

I see,  but I think that I will leave it for the next week till supported automatically ..

Thanks Ashok

[Samar Ayesh]

Hello Ashok,

 Are there any updates for this issue?

[Ashok Hariharan]

You mean for referencing globally set metadata in configuration ? I am testing a fix for that 

Ashok

[Samar Ayesh]

yes I mean the fields in metadata-panels to be reflected into global metadata section in xml