Persisting an uploaded image against a content type

one way would be creating a custom file store to save the poster image permanently after uploading it to the multiload / temporary folder and you can reference it to articles as a poster 

I'd rather do this with built-in core script, rather than adding anything custom like that, but thanks for the suggestion.

Matt said:

It's not ideal, and creates unnecessary versions of the Article, but I can't see a way around that, and most people won't care about (or see) the versions

Might this affect notifications of the Article being updated, edited or created to people subscribed to such notifications?

For anyone wanting to do the same, I think I've got a half-way decent idea.

Basically, once the file upload has completed, I can call some Velocity which edits the Article temporarily.. when I update the Article, I can append the image URL to the body HTML (at this point it it's the temporary location), and when it saves the article the Verint system will move the image to a permanent location.

I can grab the new location from the body of the updated Article, then update it again to remove the image.

It's not ideal, and creates unnecessary versions of the Article, but I can't see a way around that, and most people won't care about (or see) the versions.

Fortunately there's a parameter to stop notifications being sent out on Article updates; SuppressNotifications = 'True'

Just for reference re "with a few extra pieces of data going into a custom lookup table we implemented (think of that as our own version of Extended Attributes that works across any content type)."

There is a Telligent extension which does this github.com/.../ContentMetadata

Ah yes, we ended up rolling our own, but in hindsight maybe should have looked at that