2 Replies Latest reply on Jan 4, 2011 2:47 AM by areohbee

    Feature Request: getRawMetadata vs. getFormattedMetadata

    areohbee Level 5

      If its not too yucky on the inside, I think it would be favorable on the outside to have:

       

      photo:getMetadata( name, fmt ) return the raw or formatted form as specified, if there are two values, otherwise just one. Maybe return both if fmt not specified.

        • 1. Re: Feature Request: getRawMetadata vs. getFormattedMetadata
          Raj&K

          It'll be really nice if metadata working process will be a bit redesigned a bit. May be we'll have some freedom on change metadata. For example GPS related. Save and load metadata to external file is not an option since all the user modification will be lost. I hope i'm not very far from the topic...

          • 2. Re: Feature Request: getRawMetadata vs. getFormattedMetadata
            areohbee Level 5

            Raj&K wrote:

             

            It'll be really nice if metadata working process will be a bit redesigned a bit. May be we'll have some freedom on change metadata. For example GPS related. Save and load metadata to external file is not an option since all the user modification will be lost. I hope i'm not very far from the topic...

             

             

            I'd like to see custom metadata be "first class citizens" in the metadata-world as well. Meaning, it gets saved and read...

             

            Another weakness is limited data type support - everything is treated like a string for library filters and smart collections, even if its underlying value type is number, boolean, or date - makes for some collection limitations to say the least, if not appearing completely broken to the user...

             

            PS - Being able to register for change observation would be awesome. - Thats worth a separate thread...