And of course my original post on this thread was looking to just manually specify an author for each job. This would require making jobs for each photographer, which I'm still willing to do as it saves them time.

But ideally my last post would be what we want to happen so we can use, for example a generic sports job, and have the author get set automatically by the system.

Just to be clear, this is IPTC/XMP embedded into a photo, not an XML file. I'm looking for the 

Creator's CI: Email@1, Email@2 (ref2017.1) field from the IPTC standard to be used to match with a system user's email address for setting the Photographer/Author field on the image asset once imported via a job.

I believe the raw XMP data has this in the Iptc4xmpCore:CiEmailWork field:

<Iptc4xmpCore:CiEmailWork>kevin.cox@example.com</Iptc4xmpCore:CiEmailWork>

This field is displayed as "E-Mail(s):" in Photoshop's File Info dialog and as "Contact Emails:" in Photo Mechanic. 

Still no dice, the Photographer/Author field is still not filled in with that option enabled on our old job.

I got excited when I saw this in the release notes for TCMS Appliance 2.23.0-9 that we installed today:

• Auto generate byline/tagline from author information
  Byline and tagline will be automatically filled out if passed a specific user on my site (by supplying the matching email address) via a parser. When the user is a match, the byline and tagline should be automatically filled out. Currently this happens in the BLOX admin UI, but does not happen in parsers.
  For sites using a BLOX Job to export NITF files for third –party vendors, there will be additional tags in the output

Unfortunately it doesn't look like it accomplishes my request from this post. I tried with both the old Settings --> Jobs and the newly updated Editorial Settings --> Importers.

Any update here on a way to get this to work?

My publisher asked about this feature today, any time table yet for when it might be available?

There are actually a handful of things that suffer from the same bug. I've been trying to compile a list so I can submit a ticket about it.

In the meantime, if you edit the body copy (such as just inserting a space at the end of a paragraph) it'll force an update on the items that don't trigger one on their own.

What about using a "Domain" subscription? This way teachers can create their own accounts that will automatically get behind the paywall without y'all having to do a bunch of work to create them.

Brad, we already FTP into job folders directly from Photo Mechanic for adding photos into Total CMS.

I had discussions years ago about having an author automatically assigned through these jobs and was told it wasn't possible. If you've got that figured out I'd love to know.

I also have an open issue about how uploading photos through Jobs doesn't respect our global setting for sales (they always default to Automatic even when we're set to Disabled by default). Maybe I didn't get the memo that they corrected it as well?

I was a photographer before moving into my current role and still do most of our pro sports coverage, so I spend more time dealing with photos and collections as an "end user" than any other aspect of the system. Which means the inefficiencies here annoy me more than any others.

Oh ya! How did I not even notice that this issue will still exists, it ties right into my post above.

The main place we will use "greater than 25" item manipulation is photo galleries, and adding individual photos into a collection asset is a big one of those things that takes too many repetitive actions.

Some big progress has been made on this very old feature request. For anyone who missed this morning's webinar, go give it a watch to get caught up: https://community.townnews.com/communities/1/topics/1158-webinar-whats-new-in-blox-cms

This new batch edit functionality sounds great for very large jobs. However I'm worried there is no middle ground.

By far the largest use case, for us but I imagine others as well, is the ability to batch edit more than 25 assets, but not thousands, with normal real-time speed.

For example: A photographer files 53 photos from a high school football game for a gallery, on deadline. Right now that requires three separate batch edit operations to add themselves as the author, change the reprint status, edit the start time, etc. We need this to be done in one batch operation (which will reduce the number of clicks needed by two-thirds) and we need it to happen immediately.

It seems like we need functionality and permissions for a user to edit more than 25, but not thousands. Like 100 is fine for anyone, but don't let them do thousands of assets without the new permission assigned.