Do things like these appropriate?
Product barcodes:
For food products I typically take one photo for each side of the packaging. I usually don’t take photos of the actual product itself. So for cereals I don’t take the bag out of the box to take photos of the cereals themselves. That’s partly because the packaging typically has a photo of the product itself already.
For non food products I think taking one photo for each side of the packaging would still make sense. I feel like taking an additional photo to document the content of the product (device, included cables, chargers, etc) would make sense. I’m not sure taking detailed photos of each included part would make sense but then I don’t know if this has been discussed before.
The idea of Open Food Facts is really to document the food products offering. So personally I tend to take any photo from the packaging because it contains all the “claims” from the producer. I don’t take photo of the product inside the packaging , but that might also be a good idea.
Our database may be used in unexpected way, for example a researcher might want to study the marketing of food products… or some detail we don’t take attention yet in the database but that they may retrieve thanks to those additional photos.
Of course we also have a limited amount of space on our servers, so it is important to keep taking photo with real “information”.
My logic is producers usually try to show the product in best possible conditions, so it can be helpful to see it in real world as is
This is what I’m trying to understand here, in this topic. The problem is it is not defined what real/useful information is and should be captured and what is not. If random user thinks it will be a great idea to take tons of almost same photos with only a little different in edge/perspective, for instance, should it be punished or forbidden? Because theoretically, this user can explain for themself and be sure it is useful, because all these photos will give better and most correct understanding of product packaging form or something similar. So if it is critically important for OFF to about not wasting too much server storage, the guidelines should be clearer