|
|
Add New Release CRC-Hash Status description.JPG (13,369 bytes) Edit File CRC-Hash Status description.JPG (27,686 bytes) |
|
|
Suggest making this a dropdown menu in both locations. Unrelated: inconsistent inclusion of colon on metadata headings on Edit File page. Edit File metadata headings.JPG (22,775 bytes) |
|
|
On the File metadata page: - "CRC/Hash Status" is not immediately apparent as it is appended to "Released By". - possible confusion with "CRC/Status" field which is "verified" by API client (e.g. Avdump2). File metadata page (2).JPG (56,195 bytes) File metadata page.JPG (57,186 bytes) |
|
|
The note in the massadd form is not a requirement as such and more a technical guideline. As we try to minimize manual insertion of data for files inserting the crc by hand for each entry would be a waste of time. At the same time we require the crc field for be filled when the hash status is set. Hence you can't set the status without having the crc filled. Which you can only do in the mass add form if you have them as a filename tag. I hope you see the issue. Most releases feature properly named files and hence this isn't a large issue and for instances where md5 files are provided a mod can easily mass set the files in quesiton to verified if he gets contacted. |
- Anonymous
