08-08-2023, 03:11 AM
>You mentioned "Keys=D." - have you tried "Keys=D" ? <-- Good thought, but the period was just in this post, not in the actual metadata. I also tried with naming the field in the PDF 'keys' - lowercase. That doesn't work either.
>I think you will need to have a 2 line csv file for each song being input (first line denoting fields, 2nd line the entries for the song) <-- Ok. However, for me this would be lot more work than using the one-line-per song, single CSV file, forScore library export as the input to exiftool to batch populate into each PDF doc. Depending on Mike's answer to my question #2 that is, I suppose. And there is also some value to having the metadata travel with the PDF doc itself. Partly because I create some of the scores myself and they will be used across both MobileSheets and forScore. And partly because it fits my workflow. Tho a consolidated database in a worksheet readily available on my desktop PC would be handy....
>I think you will need to have a 2 line csv file for each song being input (first line denoting fields, 2nd line the entries for the song) <-- Ok. However, for me this would be lot more work than using the one-line-per song, single CSV file, forScore library export as the input to exiftool to batch populate into each PDF doc. Depending on Mike's answer to my question #2 that is, I suppose. And there is also some value to having the metadata travel with the PDF doc itself. Partly because I create some of the scores myself and they will be used across both MobileSheets and forScore. And partly because it fits my workflow. Tho a consolidated database in a worksheet readily available on my desktop PC would be handy....