You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://ifarchive.org/misc/org-procedures.html explains that when users upload HTML to ifarchive.org, the archive team clicks a button to zip it up. This changes the filetype of the file as it was uploaded to IFDB.
Later, when the archive team clicks the "Notify IFDB" button, which pings ifarchive-commit, the pending link will be updated to point to the ZIP file, but we won't update the file type of the link on IFDB. This requires manual work for the archive team to fix the file type and make the link work.
In order for IFDB to do the fixup automagically, we'd need to know the original filename of the file, so IFDB's Play Online button can link to it directly via unbox.
Perhaps pass it in an original_filename URL parameter?
The text was updated successfully, but these errors were encountered:
There's one thing to watch out for, though. If a file is uploaded more than once, we'll have multiple upload records. Since the primary key for this is the file MD5, we can't tell the records apart.
Therefore, it's possible that the request will come in with multipletuid or original_filename keys. Or none, conceivably.
Apropos iftechfoundation/ifdb-suggestion-tracker#448
In order for IFDB to do the fixup automagically, we'd need to know the original filename of the file, so IFDB's Play Online button can link to it directly via unbox.
Perhaps pass it in an
original_filename
URL parameter?The text was updated successfully, but these errors were encountered: