I have the job of making a webapp on our umbraco site to let users upload documents (PDFs, PPTs, etc), and I want to let them upload revisions as well. Since Umbraco doesn't support media item versioning directly I have a few ideas for workarounds, and am wondering if anyone has thought up anything better. There's a promising looking package at http://umedial.com/ but it's not ready.
1. Create a 'VersionedMedia' custom media type with some additional fields (SourceNodeID, RevisionNumber, RevisionNotes), and use this when saving/reading the file in codebehind. I've never worked with custom media or datatypes and don't know how hard that is; apparently it's easier in v > 4.6
2. Use standard media items but use a custom db table to track versions. I know this will work but was hoping for a more clever solution written by programmers better than me
3. Use Amazon S3 or a similar cloud offering with versioning enabled. Don't know that I can store version metadata that way, and it seems like we'd need to do a 2-stage upload (browser -> umbraco -> S3).
Any suggestions?
Of course there's:
4. Convince the client that versioning is unnecessary...
Strategy for managing media item versions via API
I have the job of making a webapp on our umbraco site to let users upload documents (PDFs, PPTs, etc), and I want to let them upload revisions as well. Since Umbraco doesn't support media item versioning directly I have a few ideas for workarounds, and am wondering if anyone has thought up anything better. There's a promising looking package at http://umedial.com/ but it's not ready.
1. Create a 'VersionedMedia' custom media type with some additional fields (SourceNodeID, RevisionNumber, RevisionNotes), and use this when saving/reading the file in codebehind. I've never worked with custom media or datatypes and don't know how hard that is; apparently it's easier in v > 4.6
2. Use standard media items but use a custom db table to track versions. I know this will work but was hoping for a more clever solution written by programmers better than me
3. Use Amazon S3 or a similar cloud offering with versioning enabled. Don't know that I can store version metadata that way, and it seems like we'd need to do a 2-stage upload (browser -> umbraco -> S3).
Any suggestions?
Of course there's:
4. Convince the client that versioning is unnecessary...
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.