From: Rob H. <rob...@gm...> - 2011-08-06 23:39:27
|
Devs: I was looking over my addon, and I see that I have over extended the use and purpose of it. It's use and purpose of two fold: 1) View Exif Metadata 2) Ability to edit selected Exif metadata keys... I have gone overboard with it's functionality by: a) allowing the user to be able to convert a non- Exiv2 compatible image into one that is compatible. Should I remove this functionality from this addon? Yes, it does give our users an added benefit... To go along with this conversion, the plugin will update the media's extension in the database for the user... In being able to edit, the Exif metadata, the user can update/ change the title of the media. Also if the user has not entered a date in the media editor, saving the Exif metadata will also add the date object for it... Does any one have any ideas about this addon that might be of interest to our users or yourselves? -- Sincerely yours, Rob G. Healey "Always surround yourself with people that inspire you to greatness!" |
From: John R. <jr...@ce...> - 2011-08-07 00:40:51
|
On Aug 6, 2011, at 4:39 PM, Rob Healey wrote: > Devs: > > I was looking over my addon, and I see that I have over extended the use and purpose of it. It's use and purpose of two fold: > 1) View Exif Metadata > 2) Ability to edit selected Exif metadata keys... > > I have gone overboard with it's functionality by: > a) allowing the user to be able to convert a non- Exiv2 compatible image into one that is compatible. Should I remove this functionality from this addon? Yes, it does give our users an added benefit... > > To go along with this conversion, the plugin will update the media's extension in the database for the user... > > In being able to edit, the Exif metadata, the user can update/ change the title of the media. Also if the user has not entered a date in the media editor, saving the Exif metadata will also add the date object for it... > > Does any one have any ideas about this addon that might be of interest to our users or yourselves? Rob, It seems to me that, since Gramps is a genealogy database, your plugin would be most useful if it afforded the user the ability to add geenalogy-related tags using the XMP facility in Exiv2. Possibilities include citation information for images of documents, the names of people in the image for photographs, and a back-link to the gramps object that the media item is attached to, which could be used to repair a broken link if the image file is moved to a different path. Regards, John Ralls |
From: jerome <rom...@ya...> - 2011-08-07 08:25:11
|
About tagging, Nick.H made tags active on database. :) Media objects have this feature enabled... I use it for grouping media, like into some photo managers. Same idea with notes: my 'english' notes are tagged with addition of translated notes for them. So, these custom tags are stored on gramps database but might be also written on the media itself ? Jérome --- En date de : Dim 7.8.11, John Ralls <jr...@ce...> a écrit : > De: John Ralls <jr...@ce...> > Objet: Re: [Gramps-devel] Edit Image Exif Metadata addon > À: "Rob Healey" <rob...@gm...> > Cc: "Gramps Development List" <gra...@li...> > Date: Dimanche 7 août 2011, 2h40 > > On Aug 6, 2011, at 4:39 PM, Rob Healey wrote: > > > Devs: > > > > I was looking over my addon, and I see that I have > over extended the use and purpose of it. It's use and > purpose of two fold: > > 1) View Exif Metadata > > 2) Ability to edit selected Exif metadata keys... > > > > I have gone overboard with it's functionality by: > > a) allowing the user to be able to convert a non- > Exiv2 compatible image into one that is compatible. > Should I remove this functionality from this addon? > Yes, it does give our users an added benefit... > > > > To go along with this conversion, the plugin will > update the media's extension in the database for the > user... > > > > In being able to edit, the Exif metadata, the user can > update/ change the title of the media. Also if the > user has not entered a date in the media editor, saving the > Exif metadata will also add the date object for it... > > > > Does any one have any ideas about this addon that > might be of interest to our users or yourselves? > > Rob, > > It seems to me that, since Gramps is a genealogy database, > your plugin would be most useful if it afforded the user the > ability to add geenalogy-related tags using the XMP facility > in Exiv2. Possibilities include citation information for > images of documents, the names of people in the image for > photographs, and a back-link to the gramps object that the > media item is attached to, which could be used to repair a > broken link if the image file is moved to a different path. > > Regards, > John Ralls > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San > Francisco, CA > The must-attend event for mobile developers. Connect with > experts. > Get tools for creating Super Apps. See the latest > technologies. > Sessions, hands-on labs, demos & much more. Register > early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: John R. <jr...@ce...> - 2011-08-07 16:24:05
|
On Aug 7, 2011, at 1:25 AM, jerome wrote: > About tagging, Nick.H made tags active on database. :) > > Media objects have this feature enabled... > > I use it for grouping media, like into some photo managers. > Same idea with notes: my 'english' notes are tagged with addition of translated notes for them. > > So, these custom tags are stored on gramps database but might be also written on the media itself ? Not necessarily the same tags, but yes, that's what Rob's extension does: It writes tags into the media file's metadata. Regards, John Ralls |
From: John R. <jr...@ce...> - 2011-08-08 20:49:45
|
On Aug 8, 2011, at 1:07 PM, Rob Healey wrote: > Dear John and Jerome: > > There was some talk in the beginning of creating the "Edit Image Exif Metadata" addon, about having functionality for being able to save items into the Attributes of the media object itself? > > I think that this might be a great idea for what the both of you are talking about??? > > What do you think? Does a media object's Attributes have the same filtering abilities as an object's tags? > > Sincerely yours, > Rob G. Healey > > On Sun, Aug 7, 2011 at 9:23 AM, John Ralls <jr...@ce...> wrote: > > On Aug 7, 2011, at 1:25 AM, jerome wrote: > > > About tagging, Nick.H made tags active on database. :) > > > > Media objects have this feature enabled... > > > > I use it for grouping media, like into some photo managers. > > Same idea with notes: my 'english' notes are tagged with addition of translated notes for them. > > > > So, these custom tags are stored on gramps database but might be also written on the media itself ? > > Not necessarily the same tags, but yes, that's what Rob's extension does: It writes tags into the media file's metadata. Rob, I'm not sure that I understand your questions, or what you mean by "Media Object". Certainly a Gramps media list can be filtered by the Metadata (ID, Notes, Atributes, Reference Count) stored in the Gramps database, but I don't think that there's any way at present for Gramps to do anything more with an image file's metadata than to edit or display it for the currently selected media item. There's no reason that I can think of that Gramps couldn't build a table of image metadata and make that searchable or filterable, but what I had in mind was that Gramps could copy the source data from the media item's record in the Gramps database onto the image file, which could be used outside of Gramps or to reconnect the image file with its media item if the file symlink in the database were to become invalid. Regards, John Ralls |
From: Rob H. <rob...@gm...> - 2011-08-09 00:46:21
|
Dear John and Nick: Ok, to be able to separate what we are talking about to make sure that I am understanding you... There are eight different object's in the database (Person, Family, Events, Places, Source, Repository, Media, and Note), and the media object within the database can be edited by the media editor... Exif metadata can be viewed by MetadataViewer in the MediaView's bottombar, and it can be viewed/ edited by "Edit Image Exif Metadata" in MediaView's sidebar... Tags and Attributes can be edited/ created by Gramps... "Edit Image Exif Metadata" can also create/ edit anything that the media editor can by accessing the DbTxn... It would be easy to be able to save the media path within the Exif metadata, but we would need to isolate and find an Exif key that no one uses and save the file path to it... Nick Hall, do you know of an Exif tag that could be used for this purpose...? Sincerely yours, Rob G. Healey On Mon, Aug 8, 2011 at 1:49 PM, John Ralls <jr...@ce...> wrote: > > On Aug 8, 2011, at 1:07 PM, Rob Healey wrote: > > > Dear John and Jerome: > > > > There was some talk in the beginning of creating the "Edit Image Exif > Metadata" addon, about having functionality for being able to save items > into the Attributes of the media object itself? > > > > I think that this might be a great idea for what the both of you are > talking about??? > > > > What do you think? Does a media object's Attributes have the same > filtering abilities as an object's tags? > > > > Sincerely yours, > > Rob G. Healey > > > > On Sun, Aug 7, 2011 at 9:23 AM, John Ralls <jr...@ce...> wrote: > > > > On Aug 7, 2011, at 1:25 AM, jerome wrote: > > > > > About tagging, Nick.H made tags active on database. :) > > > > > > Media objects have this feature enabled... > > > > > > I use it for grouping media, like into some photo managers. > > > Same idea with notes: my 'english' notes are tagged with addition of > translated notes for them. > > > > > > So, these custom tags are stored on gramps database but might be also > written on the media itself ? > > > > Not necessarily the same tags, but yes, that's what Rob's extension does: > It writes tags into the media file's metadata. > > Rob, > > I'm not sure that I understand your questions, or what you mean by "Media > Object". Certainly a Gramps media list can be filtered by the Metadata (ID, > Notes, Atributes, Reference Count) stored in the Gramps database, but I > don't think that there's any way at present for Gramps to do anything more > with an image file's metadata than to edit or display it for the currently > selected media item. There's no reason that I can think of that Gramps > couldn't build a table of image metadata and make that searchable or > filterable, but what I had in mind was that Gramps could copy the source > data from the media item's record in the Gramps database onto the image > file, which could be used outside of Gramps or to reconnect the image file > with its media item if the file symlink in the database were to become > invalid. > > Regards, > John Ralls > > -- Sincerely yours, Rob G. Healey "Always surround yourself with people that inspire you to greatness!" |
From: John R. <jr...@ce...> - 2011-08-09 03:01:24
|
On Aug 8, 2011, at 5:46 PM, Rob Healey wrote: > Dear John and Nick: > > Ok, to be able to separate what we are talking about to make sure that I am understanding you... > > There are eight different object's in the database (Person, Family, Events, Places, Source, Repository, Media, and Note), and the media object within the database can be edited by the media editor... > > Exif metadata can be viewed by MetadataViewer in the MediaView's bottombar, and it can be viewed/ edited by "Edit Image Exif Metadata" in MediaView's sidebar... > > Tags and Attributes can be edited/ created by Gramps... "Edit Image Exif Metadata" can also create/ edit anything that the media editor can by accessing the DbTxn... > > It would be easy to be able to save the media path within the Exif metadata, but we would need to isolate and find an Exif key that no one uses and save the file path to it... > > Nick Hall, do you know of an Exif tag that could be used for this purpose...? Rob, Not EXIF, XMP (http://en.wikipedia.org/wiki/Extensible_Metadata_Platform). You make up your own tags. It's supported by libexif2. Rather than saving the path, there's got to be a key field in the DB that identifies the media item. Write that to the Image file metadata, and if the symlink gets borked Gramps will be able to identify the picture. It could also save the user from adding the same image more than once. You can use the XMP data to also stick a citation and the attributes from the media object onto the image file, where they'd be viewable from other applications. Regards, John Ralls |
From: John R. <jr...@ce...> - 2011-08-09 05:24:55
|
On Aug 8, 2011, at 9:17 PM, Rob Healey wrote: > Dear John: > > On Mon, Aug 8, 2011 at 8:01 PM, John Ralls <jr...@ce...> wrote: > > On Aug 8, 2011, at 5:46 PM, Rob Healey wrote: > > > Dear John and Nick: > > > > Ok, to be able to separate what we are talking about to make sure that I am understanding you... > > > > There are eight different object's in the database (Person, Family, Events, Places, Source, Repository, Media, and Note), and the media object within the database can be edited by the media editor... > > > > Exif metadata can be viewed by MetadataViewer in the MediaView's bottombar, and it can be viewed/ edited by "Edit Image Exif Metadata" in MediaView's sidebar... > > > > Tags and Attributes can be edited/ created by Gramps... "Edit Image Exif Metadata" can also create/ edit anything that the media editor can by accessing the DbTxn... > > > > It would be easy to be able to save the media path within the Exif metadata, but we would need to isolate and find an Exif key that no one uses and save the file path to it... > > > > Nick Hall, do you know of an Exif tag that could be used for this purpose...? > > Rob, > > Not EXIF, XMP (http://en.wikipedia.org/wiki/Extensible_Metadata_Platform). You make up your own tags. It's supported by libexif2. > > As far as Xmp and Iptc tags go, Nick Hall and I decided to not include these tags because they were difficult to get a standard value to work in displaying... > > tag = plugin_image["Xmp.xmp.Label"] > value = tag.human_value > > tag = plugin_image["Iptc.Application2.ModifyDate"] > value = tag.human_value > > tag = plugin_image["Exif.Image.Artist"] > value = tag.human_value > > The last example works, but the first two do NOT! > > Yes, we could use the Xmp tags by making a call to the user's installed Exiv2 library! We do not have to see them to be able to use them... > > What Xmp tags do you think that we should use? Rob, Make up your own, or look around and see if anyone else has invented a grammar for what you want to do. The "X" is for "extensible", just like XML. For example, there are a bunch of research paper managers that encode the BibTeX citation for the paper back into the PDF using the XMP metadata. JabRef (which just happened to be the first one that came up when I Googled just now) has a nice discussion of what they're doing at http://jabref.sourceforge.net/help/XMPHelp.php. (Unfortunately libexif2 doesn't support PDFs, but that's a separate issue entirely. Ancestry, Footnote, and the camera I use in libraries all make jpegs, so it's not that big a deal, but it is sometimes convenient to convert multipage documents into a single PDF.) Regards, John Ralls |
From: Duncan L. <dun...@gm...> - 2011-08-10 19:14:04
|
Hej Rob , I've been looking forward to working with the Exif tool for ages. I look forward to the image itself holding information about people, place and date. As for over extending the function of it... the ability to make a non-compliant file Exif capable sounds very relevant to the purpose of the plugin. In what way do you feel it is going overboard? Duncan -- 'The unconsidered life is not worth living' - Socrates |
From: Rob H. <rob...@gm...> - 2011-08-10 19:34:10
|
Dear Duncan: I am very grateful that you re looking forward to being able to save certain information within the image Exif metadata... On Wed, Aug 10, 2011 at 12:13 PM, Duncan Lithgow <dun...@gm...>wrote: > Hej Rob , I've been looking forward to working with the Exif tool for > ages. I look forward to the image itself holding information about > people, place and date. > I am also phishing for ideas of what information from the media object's should also be contained within the image as possible backup information... This way it could be accessed later if necessary to be build the database... John Ralls mentioned somethings like image source citation, image path, and who is in the image... Sincerely yours, Rob G. Healey > As for over extending the function of it... the ability to make a > non-compliant file Exif capable sounds very relevant to the purpose of > the plugin. In what way do you feel it is going overboard? > > Duncan > > -- > 'The unconsidered life is not worth living' - Socrates > -- Sincerely yours, Rob G. Healey "Always surround yourself with people that inspire you to greatness!" |
From: Duncan L. <dun...@gm...> - 2011-08-24 20:51:16
|
On 10 August 2011 21:34, Rob Healey <rob...@gm...> wrote: > Dear Duncan: > I am very grateful that you re looking forward to being able to save certain > information within the image Exif metadata... > On Wed, Aug 10, 2011 at 12:13 PM, Duncan Lithgow <dun...@gm...> > wrote: >> >> Hej Rob , I've been looking forward to working with the Exif tool for >> ages. I look forward to the image itself holding information about >> people, place and date. > > I am also phishing for ideas of what information from the media object's > should also be contained within the image as possible backup information... > This way it could be accessed later if necessary to be build the database... > John Ralls mentioned somethings like image source citation, image path, and > who is in the image... > Sincerely yours, > Rob G. Healey Some handle back to the database would be good. Maybe a handle back to each database object referencing the image. Duncan -- 'The unconsidered life is not worth living' - Socrates |
From: Rob H. <rob...@gm...> - 2011-08-24 21:38:50
|
Greetings: So something like this might handle it: for (classname, newhandle) in db.find_backlink_handles(handle, include_classes = ["Person", "Family", "Event", "Place", "Source"]): Would this do it? I believe out of the eight objects, these are the ones that can have a media object? Sincerely yours, Rob G. Healey On Wed, Aug 24, 2011 at 1:50 PM, Duncan Lithgow <dun...@gm...>wrote: > On 10 August 2011 21:34, Rob Healey <rob...@gm...> wrote: > > Dear Duncan: > > I am very grateful that you re looking forward to being able to save > certain > > information within the image Exif metadata... > > On Wed, Aug 10, 2011 at 12:13 PM, Duncan Lithgow < > dun...@gm...> > > wrote: > >> > >> Hej Rob , I've been looking forward to working with the Exif tool for > >> ages. I look forward to the image itself holding information about > >> people, place and date. > > > > I am also phishing for ideas of what information from the media object's > > should also be contained within the image as possible backup > information... > > This way it could be accessed later if necessary to be build the > database... > > John Ralls mentioned somethings like image source citation, image path, > and > > who is in the image... > > Sincerely yours, > > Rob G. Healey > > Some handle back to the database would be good. Maybe a handle back to > each database object referencing the image. > > Duncan > > -- > 'The unconsidered life is not worth living' - Socrates > -- Sincerely yours, Rob G. Healey "Always surround yourself with people that inspire you to greatness!" |
From: Duncan L. <dun...@gm...> - 2011-08-26 20:29:23
|
On 24 August 2011 23:38, Rob Healey <rob...@gm...> wrote: ... > for (classname, newhandle) in db.find_backlink_handles(handle, > include_classes = ["Person", "Family", "Event", "Place", "Source"]): I'm no programmer, but yes, that's what I was thinking. Duncan -- 'The unconsidered life is not worth living' - Socrates |