When images are downloaded by PhotoCenter, all the Meta data (Exif) to be downloaded with the image. So when same image was uploaded back to PhotoCenter with Meta data as a different image(image2). So Meta data can be re-used by image2 uploaded.
At the Globe, the main concern of our photo department was ensuring that inaccurate or incomplete caption information does not persist. Seems like it would be better to simply replace the original IPTC caption with the updated Photo Center caption information. Any relevant information from the original caption will be retained by the person editing the caption. Thanks.
Hello! We are currently working on this and looking for some feedback.
The original ask is to replace the original IPTC metadata with the updated version made in the Photo Center (PC) UI. However, we've uncovered the ability to keep the updated version made in PC UI as well as the original. Example:
IPTC Caption: As Trump does x, y and z he does this and that Edit made in Photo Center UI: Trump actually did this thing IPTC Caption (after): Trump actually did this thing; As Trump does x, y and z he does this and that
So the first IPTC Caption data (before the semicolon) that follows the image, will be edits made in the PC UI. The IPTC caption data (after the semicolon) is the original.
Please let us know your thoughts ASAP so we can implement one or the other. Looking for feedback by EOD today so we can move forward. Thanks!
@Thomas Berger: Thanks for your feedback! Just to clarify, do you mean that you want the IPTC data of the image (the binary) to be available to front end readers?
Or just typical metadata fields like caption and photographer (as an example) that is rendered through Page Builder via the ANS. Thanks!
Hi all - back to validate the finalized a/c with the group here. Please let us know if anything below does not meet your needs. Thanks! We are hoping to tackle this by end of Q2.
Background
When editors download an image from Photo Center, send to print, or have an outbound feed fetching images from Photo Center, they would like to see changes made to the metadata (i.e. the caption, etc.) in Photo Center, reflected in the IPTC data. This is crucial for print workflows in particular. There is no need for a pristine version (the version that was originally uploaded into Photo Center).
a/c
When a user downloads an image from Photo Center, they would like to see all of the metadata associated with that image, including the metadata they’ve inputted on Photo Center
When a user sends to print, they would also like to see all of the metadata associated with that image, including the metadata they’ve inputted on Photo Center
If users have a 3rd party system that fetches images from Photo Center (i.e. via an outbound feed) into a more complicated workflow, the IPTC data edited in Photo Center will also need to follow
We don't see a need to retain the state of the metadata when the file was first uploaded / ingested into Photo Center.
I added ingested as in our case, most of our photos do not get uploaded directly to Photo Center, but get first ingested to an internal digital asset management system, and there is a constantly running task that looks for images created or updated in a 1 minute interval and sends them via a JSON feed that is ingested by a custom Arc I/O process that was implemented by Arc as part of our onboarding.
What we do want is for the IPTC header portion of the photo file to be updated EVERY time the metadata is updated and saved. Updating the IPTC header only when a user downloads the file is not sufficient. We want the IPTC header on the photo to reflect the way the metadata is set on it's Photo Center at all times. Photo files do not always leave ARc via a download from Photo Center. They can also leave Arc as part of an outbound feed that includes photos.
Please let me know if you have any further questions on our requirements.
The Globe does not need the original, uploaded information; we only need the most recent information from Photo Center -- so, for us, your assumption is correct.
Hi - just a follow up question to the group - do you require a copy of the original uploaded version? Our assumption is that you do not, and that your main pain point is that the edits you make to the metadata in Photo Center is not there when you download or send to print.
Good news about this being committed to be "tackled" in early 2020. Please provide us with details about how Arc intends to implement this BEFORE implementation begins, so there will be alighment between expectations and what is delivered. Also there may be some workflow variations that would be easy to accomodate if they were considered as part of the initial implementation.
I agree with Greg’s comment below, it is better to replace the IPTC than to add to it.
At the Globe, the main concern of our photo department was ensuring that inaccurate or incomplete caption information does not persist. Seems like it would be better to simply replace the original IPTC caption with the updated Photo Center caption information. Any relevant information from the original caption will be retained by the person editing the caption. Thanks.
Hello! We are currently working on this and looking for some feedback.
The original ask is to replace the original IPTC metadata with the updated version made in the Photo Center (PC) UI. However, we've uncovered the ability to keep the updated version made in PC UI as well as the original. Example:
IPTC Caption: As Trump does x, y and z he does this and that
Edit made in Photo Center UI: Trump actually did this thing
IPTC Caption (after): Trump actually did this thing; As Trump does x, y and z he does this and that
So the first IPTC Caption data (before the semicolon) that follows the image, will be edits made in the PC UI. The IPTC caption data (after the semicolon) is the original.
Please let us know your thoughts ASAP so we can implement one or the other. Looking for feedback by EOD today so we can move forward. Thanks!
@Thomas Berger: Thanks for your feedback! Just to clarify, do you mean that you want the IPTC data of the image (the binary) to be available to front end readers?
Or just typical metadata fields like caption and photographer (as an example) that is rendered through Page Builder via the ANS. Thanks!
Great, that would solve a big issue for us. Is there an ETA for the feature?
Jakob -- Yes, it will.
Would this also apply to images sent to a print CMS through the API?
Hi Ryan~
May I know when will this be shipped or planned to be shipped?
Bonnie Mou
Hong Kong Apple Daily
Hi,
Thanks.
I'll add that the meta (eg. IPTC) should be kept when the image is displayed in front, using the resizer.
Thomas
Hi all - back to validate the finalized a/c with the group here. Please let us know if anything below does not meet your needs. Thanks! We are hoping to tackle this by end of Q2.
Background
When editors download an image from Photo Center, send to print, or have an outbound feed fetching images from Photo Center, they would like to see changes made to the metadata (i.e. the caption, etc.) in Photo Center, reflected in the IPTC data. This is crucial for print workflows in particular. There is no need for a pristine version (the version that was originally uploaded into Photo Center).
a/c
When a user downloads an image from Photo Center, they would like to see all of the metadata associated with that image, including the metadata they’ve inputted on Photo Center
When a user sends to print, they would also like to see all of the metadata associated with that image, including the metadata they’ve inputted on Photo Center
If users have a 3rd party system that fetches images from Photo Center (i.e. via an outbound feed) into a more complicated workflow, the IPTC data edited in Photo Center will also need to follow
Also, do you have an approximate ETA for this yet? A had-to-ask question from a recent meetring with newsroom/photo team.
Thanks,
Ian Krsntz
The Philadelphia Inquirer
Hi Larry,
We don't see a need to retain the state of the metadata when the file was first uploaded / ingested into Photo Center.
I added ingested as in our case, most of our photos do not get uploaded directly to Photo Center, but get first ingested to an internal digital asset management system, and there is a constantly running task that looks for images created or updated in a 1 minute interval and sends them via a JSON feed that is ingested by a custom Arc I/O process that was implemented by Arc as part of our onboarding.
What we do want is for the IPTC header portion of the photo file to be updated EVERY time the metadata is updated and saved. Updating the IPTC header only when a user downloads the file is not sufficient. We want the IPTC header on the photo to reflect the way the metadata is set on it's Photo Center at all times. Photo files do not always leave ARc via a download from Photo Center. They can also leave Arc as part of an outbound feed that includes photos.
Please let me know if you have any further questions on our requirements.
Thanks,
Ian Krantz
the Philadelphia Inquirer
Laay, Thanks for reaching out on this. I need to get some feedback from others on this, so I will get back to you early next week.
Ian Krantz
The Philadelphia Inquirer.
The Globe does not need the original, uploaded information; we only need the most recent information from Photo Center -- so, for us, your assumption is correct.
Greg Lang
The Boston Globe
Hi - just a follow up question to the group - do you require a copy of the original uploaded version? Our assumption is that you do not, and that your main pain point is that the edits you make to the metadata in Photo Center is not there when you download or send to print.
Thanks for confirming!
Hi Ian
Thanks for the note. Larry and I will be in touch as this work moves forward.
Ryan
hi Ryan,
Good news about this being committed to be "tackled" in early 2020. Please provide us with details about how Arc intends to implement this BEFORE implementation begins, so there will be alighment between expectations and what is delivered. Also there may be some workflow variations that would be easy to accomodate if they were considered as part of the initial implementation.
Thanks,
Ian
Ian Krantz
The Philadelphia Inquirer