Thanks TonyM & Mark S. for prod to extract some EXIF data to the TW. My focus, I think, simply comes from work on photographs Adobe Lightroom. It uses embedded data directly to organise its entire non-destructive editing system.
So part of it is a kind of mindset *I* have about EXIF outside TW. Why bother importing it? On reflection, for the use case, you may be right in that it may be better to have the basic EXIF data in the TW. There could also be some benefits for the user--like being able to export all the meta data without the end user needing specialised software to do so. FWIW, I'm now thinking of extracting all the needed metadata into a single data-tiddler, with each line an array for each image and with the child painter's details, i.e.: *Image-File-Number: Name, Age, School, Gender, Year.* I'll give it a go and see. Thanks, Josiah Mark S. wrote: > > I too am puzzled why you would need/want the TW file to be nearly empty. > The information is not going to be searchable , if that is a goal, unless > it is loaded in the TW. > TonyM wrote: > In your case the import exif data may not be such a chore or excessive > space as you think. Say you had 1KB of exif data per image and 4000 images > this is only 4MB which is acceptable for a single function tiddlywiki > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/9db4e209-389c-4d12-9ec8-8f8b143cec99%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
