[livesupport-dev] Validator enabled in storageServer
  • Hi all,

    metadata validator is enabled in storageServer now (in CVS), all test
    data called from sampleData.php (by resetStorage method) and empty data
    templates have been updated to pass through it.

    If there would be problems related to validation, it can be disabled by
    'validate' filed in storageServer/var/conf.php (TRUE/FALSE flag).

    Tomas Hlava
    th@red2head.com

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • 16 Comments sorted by
  • It seems empty data template for audioclip is not used.

    During file-upload first I call putFile() with mdataFileLP parameter set to
    NULL.
    After that I have to call replaceMetadata() with some constructed xml,
    elsewhere mdata is empty (no records in ls_mdata) and cannot be
    changed/added by setMDataValue().

    Would be better if putFile() use empty data template, like storeWebstream()
    seems to do.




    > -----Ursprungliche Nachricht-----
    > Von: Tomas Hlava [mailto:th@red2head.com]
    > Gesendet: Montag, 7. Marz 2005 04:51
    > An: livesupport-dev@campware.org
    > Betreff: [livesupport-dev] Validator enabled in storageServer
    >
    >
    > Hi all,
    >
    > metadata validator is enabled in storageServer now (in CVS), all test
    > data called from sampleData.php (by resetStorage method) and empty data
    > templates have been updated to pass through it.
    >
    > If there would be problems related to validation, it can be disabled by
    > 'validate' filed in storageServer/var/conf.php (TRUE/FALSE flag).
    >
    > Tomas Hlava
    > th@red2head.com

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • On Mon, 7 Mar 2005 09:04:53 +0100 Sebastian Goebel wrote:
    > It seems empty data template for audioclip is not used.
    >
    > During file-upload first I call putFile() with mdataFileLP parameter set to
    > NULL.
    > After that I have to call replaceMetadata() with some constructed xml,
    > elsewhere mdata is empty (no records in ls_mdata) and cannot be
    > changed/added by setMDataValue().
    >
    > Would be better if putFile() use empty data template, like storeWebstream()
    > seems to do.

    Oh sorry - of course,
    it's fixed and commited now.

    Tomas Hlava
    th@red2head.com

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • Tomas Hlava wrote:
    > If there would be problems related to validation, it can be disabled by
    > 'validate' filed in storageServer/var/conf.php (TRUE/FALSE flag).

    I have a problem. I'm just writing the file upload feature in the C++
    GUI, with elements based on:

    http://livesupport.campware.org/public_html/doc/gui/metadataFields.html#table1

    here, for example, the genre metadata element is ls:genre. but, when I
    try to add an audio clip with such a metadta, I get an error from the
    validator:

    faultCode:805
    Validator: Unknown element #113 (genre, gunid=...)


    so, what is the relation between the above document, and the validator?
    what are the valid metadata?


    Akos

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • Akos Maroy wrote:
    > so, what is the relation between the above document, and the validator?
    > what are the valid metadata?

    speaking more of the issue, it's strange that on the main tab, genre is
    said to be ls:genre, whereas on the music tab, it's marked as dc:type.

    also, in Charles' design for the music tab, it's supposed to be a
    drop-down menu for the music tab. vs. a text entry field on the main
    tab. so, which one is it? if it's a drop-down, what is the value-set for it?


    Akos

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • On Mon, 07 Mar 2005 18:40:39 +0100 Akos Maroy wrote:
    > Tomas Hlava wrote:
    > > If there would be problems related to validation, it can be disabled by
    > > 'validate' filed in storageServer/var/conf.php (TRUE/FALSE flag).
    >
    > I have a problem. I'm just writing the file upload feature in the C++
    > GUI, with elements based on:
    >
    > http://livesupport.campware.org/public_html/doc/gui/metadataFields.html#table1
    >
    > here, for example, the genre metadata element is ls:genre. but, when I
    > try to add an audio clip with such a metadta, I get an error from the
    > validator:
    >
    > faultCode:805
    > Validator: Unknown element #113 (genre, gunid=...)
    >
    >
    > so, what is the relation between the above document, and the validator?
    > what are the valid metadata?

    I'sorry but namespace prefix is required now - try 'ls:genre'.
    Validator can handle only following predfined namespaces now:
    xmlns:ls="http://mdlf.org/livesupport/elements/1.0/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:dcterms="http://purl.org/dc/terms/"
    xmlns:xml="http://www.w3.org/XML/1998/namespace"

    Tomas Hlava
    th@red2head.com

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • Tomas Hlava wrote:
    > I'sorry but namespace prefix is required now - try 'ls:genre'.

    of course I tried ls:genre, but the error report quoted it without the
    namespace..

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • On Mon, 07 Mar 2005 18:49:20 +0100 Akos Maroy wrote:
    > Akos Maroy wrote:
    > speaking more of the issue, it's strange that on the main tab, genre is
    > said to be ls:genre, whereas on the music tab, it's marked as dc:type.

    Yes, it's wrong.
    It may be probably dc:type (and ls:genre is unnecessary).
    I will fix metadataFields.html in CVS

    Tomas Hlava
    th@red2head.com

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • Tomas Hlava wrote:
    > Yes, it's wrong.
    > It may be probably dc:type (and ls:genre is unnecessary).
    > I will fix metadataFields.html in CVS

    great.

    and is an open text field, or has a fixed value set? in the latter case,
    what is the value set?

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • On Mon, 07 Mar 2005 19:16:53 +0100 Akos Maroy wrote:
    > Tomas Hlava wrote:
    > > Yes, it's wrong.
    > > It may be probably dc:type (and ls:genre is unnecessary).
    > > I will fix metadataFields.html in CVS
    >
    > great.
    >
    > and is an open text field, or has a fixed value set? in the latter case,
    > what is the value set?

    It's type 'menu' by Doug's document, but I have only examples what would be in this set,
    not final complete set. I've attached what I have.

    Tomas Hlava
    th@red2head.com

    On Tue, 1 Feb 2005 08:25:51 +0100 Douglas.Arellanes@mdlf.org wrote:
    > Hi Tomas,
    >
    > Let me see if I can give you some samples of what that metadata should
    > look like. - doug
    >
    > > - possible values for Description.Mood
    >
    > High energy
    > Downtempo
    > Late night
    > Concentration
    >
    > - possible values for Type.Genre
    >
    > House
    > Country
    > Classical
    > Bossa Nova
    > Nu-Jazz
    > Tribal
    > Country Rock
    > Knedliky Rock
    > Turbofolk
    > etc.
    >

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • On Mon, 07 Mar 2005 19:13:35 +0100 Akos Maroy wrote:
    > Tomas Hlava wrote:
    > > I'sorry but namespace prefix is required now - try 'ls:genre'.
    >
    > of course I tried ls:genre, but the error report quoted it without the
    > namespace..

    Send me, please, XML generating this error.
    ls:genre is marked as optional element in audioclip/metadata container.

    --
    Tomas Hlava
    th@red2head.com

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • On Mon, 7 Mar 2005 19:31:36 +0100 Tomas Hlava wrote:
    > On Mon, 07 Mar 2005 19:16:53 +0100 Akos Maroy wrote:
    > > and is an open text field, or has a fixed value set? in the latter case,
    > > what is the value set?
    >
    > It's type 'menu' by Doug's document, but I have only examples what would be in this set,
    > not final complete set. I've attached what I have.

    I've found better value set for genres in list archive:

    On Wed, 02 Feb 2005 01:06:58 +0100 Robert Klajn wrote:
    > Doug : ....Robert can probably provide better descriptions for the mood field here.
    > Hi,
    > Here's my sample for metadata values.
    > a) possible values for Basic Type - Genre:
    > Avant-Garde
    > Alternative
    > Blues
    > Classical
    > Comedy
    > Country
    > Easy listening
    > Electronica
    > Folk
    > Gospel
    > Hip Hop
    > Jazz
    > Latin
    > New Age
    > Pop
    > Punk
    > R&B
    > Rap
    > Reggae
    > Rock
    > Soul
    > Soundtrack
    > Vocal
    > World Music


    Tomas Hlava
    th@red2head.com

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • Tomas Hlava wrote:
    > Send me, please, XML generating this error.
    > ls:genre is marked as optional element in audioclip/metadata container.

    you're right, the ls namespace was stripped on the C++ side, see:

    http://bugs.campware.org/view.php?id=623


    but: when was this introduced? I guess no one told Ferenc about it?
    what values do we use from the ls: namespace? I guess genre is out, as
    you've opted for dc:type instead...

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • Tomas Hlava wrote:
    > I've found better value set for genres in list archive:

    and is this list authoritive? should this be hard coded, or in a config
    file? (please, don't tell me the user can add/remove genre values Smile

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • This is a multipart message in MIME format.
    --=_alternative 003418D9C1256FBE_=
    Content-Type: text/plain; charset="us-ascii"

    Sebastian and I were discussing this on Friday as well. The end user
    probably shouldn't be able to add/edit menu items, but it would be good if
    they were in config files with documentation explaining how they could be
    edited. The other possibility would be to put that in the System Prefs in
    the HTML UI.

    doug






    Akos Maroy
    03/08/2005 10:03 AM
    Please respond to livesupport-dev


    To: livesupport-dev@campware.org
    cc:
    Subject: Re: [livesupport-dev] Validator enabled in storageServer


    Tomas Hlava wrote:
    > I've found better value set for genres in list archive:

    and is this list authoritive? should this be hard coded, or in a config
    file? (please, don't tell me the user can add/remove genre values Smile



    --=_alternative 003418D9C1256FBE_=
    Content-Type: text/html; charset="us-ascii"



    Sebastian and I were discussing this on Friday as well. The end user probably shouldn't be able to add/edit menu items, but it would be good if they were in config files with documentation explaining how they could be edited. The other possibility would be to put that in the System Prefs in the HTML UI.



    doug













    Akos Maroy <darkeye@tyrell.hu>

    03/08/2005 10:03 AM

    Please respond to livesupport-dev


           

            To:        livesupport-dev@campware.org

            cc:        

            Subject:        Re: [livesupport-dev] Validator enabled in storageServer






    Tomas Hlava wrote:

    > I've found better value set for genres in list archive:



    and is this list authoritive? should this be hard coded, or in a config

    file? (please, don't tell me the user can add/remove genre values Smile






    --=_alternative 003418D9C1256FBE_=--

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • Douglas.Arellanes@mdlf.org wrote:
    > Sebastian and I were discussing this on Friday as well. The end user
    > probably shouldn't be able to add/edit menu items, but it would be good if
    > they were in config files with documentation explaining how they could be
    > edited. The other possibility would be to put that in the System Prefs in
    > the HTML UI.

    ok. please see the related issue I added to mantis:

    http://bugs.campware.org/view.php?id=624

    could I get a complete list of all metadata values of type 'menu'?

    also, there are some strange metadata types of 'menu' type, like report
    location and creator in the talk tab. I'm not sure if we want to list
    all the possible location in the Universe, for example Smile

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • This is a multipart message in MIME format.
    --=_alternative 0035255AC1256FBE_=
    Content-Type: text/plain; charset="us-ascii"

    Heh. All possible locations in the Known Universe would be pretty cool to
    see in a pull-down. Those fields should be free text, with the
    understanding (as the DC people explain it) that users can use either
    textual names for location or GPS coordinates.

    But generally, wherever possible, we should try to limit users' ability to
    input junk data. For example, one person might put in 'Prague 6' and
    another 'Praha 6' and a third 'P6' and they'd all be talking about the
    same thing. The issue there is to try to strike a balance between ease of
    use for the user and ease of development. Which is why config files would
    be fine by me, with the assumption that by 1.1 we'd have some kind of
    interface for their administration.

    The other problem on things like 'Genre' come in when new styles of music
    develop. 'Acid Jazz' might be too passe, and 'Nu Jazz' is the preferred
    term, for example. Some way of editing those possibilities should be
    allowed, but not for every user.

    I'll work on the lists right now.

    doug






    Akos Maroy
    03/08/2005 10:34 AM
    Please respond to livesupport-dev


    To: livesupport-dev@campware.org
    cc:
    Subject: Re: [livesupport-dev] Validator enabled in storageServer


    Douglas.Arellanes@mdlf.org wrote:
    > Sebastian and I were discussing this on Friday as well. The end user
    > probably shouldn't be able to add/edit menu items, but it would be good
    if
    > they were in config files with documentation explaining how they could
    be
    > edited. The other possibility would be to put that in the System Prefs
    in
    > the HTML UI.

    ok. please see the related issue I added to mantis:

    http://bugs.campware.org/view.php?id=624

    could I get a complete list of all metadata values of type 'menu'?

    also, there are some strange metadata types of 'menu' type, like report
    location and creator in the talk tab. I'm not sure if we want to list
    all the possible location in the Universe, for example Smile



    --=_alternative 0035255AC1256FBE_=
    Content-Type: text/html; charset="us-ascii"



    Heh. All possible locations in the Known Universe would be pretty cool to see in a pull-down. Those fields should be free text, with the understanding (as the DC people explain it) that users can use either textual names for location or GPS coordinates.



    But generally, wherever possible, we should try to limit users' ability to input junk data. For example, one person might put in 'Prague 6' and another 'Praha 6' and a third 'P6' and they'd all be talking about the same thing. The issue there is to try to strike a balance between ease of use for the user and ease of development. Which is why config files would be fine by me, with the assumption that by 1.1 we'd have some kind of interface for their administration.



    The other problem on things like 'Genre' come in when new styles of music develop. 'Acid Jazz' might be too passe, and 'Nu Jazz' is the preferred term, for example. Some way of editing those possibilities should be allowed, but not for every user.



    I'll work on the lists right now.



    doug













    Akos Maroy <darkeye@tyrell.hu>

    03/08/2005 10:34 AM

    Please respond to livesupport-dev


           

            To:        livesupport-dev@campware.org

            cc:        

            Subject:        Re: [livesupport-dev] Validator enabled in storageServer






    Douglas.Arellanes@mdlf.org wrote:

    > Sebastian and I were discussing this on Friday as well. The end user

    > probably shouldn't be able to add/edit menu items, but it would be good if

    > they were in config files with documentation explaining how they could be

    > edited. The other possibility would be to put that in the System Prefs in

    > the HTML UI.



    ok. please see the related issue I added to mantis:



    http://bugs.campware.org/view.php?id=624



    could I get a complete list of all metadata values of type 'menu'?



    also, there are some strange metadata types of 'menu' type, like report

    location and creator in the talk tab. I'm not sure if we want to list

    all the possible location in the Universe, for example Smile






    --=_alternative 0035255AC1256FBE_=--

    ------------------------------------------
    Posted to Phorum via PhorumMail