Hosta

Shortcut: COM:OVERWRITE· COM:CROP

Esta guía es sobre cómo y cuándo se debe o no debe sobreescribir archivos existentes. ^[1] La guía en esto es necesaria debido a que tanto los proyectos de Wikimedia que usan los archivos de Commons como Reutilización del contenido fuera de Wikimedia confian en archivos que serán rezonablemente estables. Como resultado, la regla básica es que los archivos existentes no deben ser sobreescritos con contenido substancialmente diferente, mientras que mejoras menores deben sobreescribir la versión anterior (pero vea más abajo para excepciones). En caso de dida, o para resolver conflictos inter-usuario, suba la versión como un nuevo archivo.

Nota: La licencia no puede ser cambiada. Al subir un archivo bajo una licencia diferente sólo puede ser realizado creando un nuevo archivo.

Cuando no se sobreescribe el archivo existente, los cambios se deben subir usando un nuevo nombre (idealmente similar al antiguo archivo), y la página de descripción del archivo debe enlazar al archivo original para dar crédito al autor original

Sobreescribir

Mejoras menores

Como regla general, usa el enlace Subir una nueva versión de este archivo sólo para mejoras relativamente menores. Ejemplos incluyen

• reemplazado con el mismo archivo con una resolución mayor
• cambios de color menores y no controversiales , reducción de ruido, correción de perspectiva, etc
• Remoción de marca de agua
• necesidad de rotación en 90/180/270º o correcciones de rotación menores en imágenes que no están correctamente alineadas en vertical
• Recortes menores
• Correcciones de diagramas, mapas, o gráficos, si una versión más exacta está disponible

y cosas similares donde la composición esencial no ha sido alterada. Esto puede incluir un recorte menor, por ejemplo remover un borde añadido recientemente (no sobreescriba archivos que remueven partes de imágenes históricas), pero recortes agresivos usualmente son cargados con un nuevo nombre, como "Nombre de imagen antigua (recortada).jpg".

Correcciones de errores menores que usualmente se consideran una mejora menor. Por lo tanto, las correcciones más extensas, es más probable que sea mejor subir la versi+on corregida como un nuevo archivo (para evitar desacuerdos potenciales sobre qué corrección es apropiada, y potencialmente una guerra de cargas), y si es necesario nominar la versión antigua para borrado.

Nota: un archivo con anotaciones en imagen perderá dichas anotaciones si las dimensiones en pixeles cambian -"véase Help:Gadget-ImageAnnotator#Limitations". Esto no es razón para separar un archivo cuando se hacen modificaciones menores, así como también las anotaciones pueden ser reingresadas.

Excepciones

Si un trabajo de"restauración digital" es realizada a un documento u obra histórica (no importa cuan menor es) debe ser cargada bajo un nuevo nombre, proveyendo un enlace hacia la fuente donde se basó el nuevo archivo en el campo "Otras versiones". Los cambios que han sido realizados también deben ser documentados en un detalle suficiente para reproducirlos, en lo posible. Esta es la mejor práctica para restauraciones, debido a que permite a los usuarios y restauraciones subsecuentes a seguir la cadena de mejoras y para realizar comparaciones detalladas con los originales. (Entonces, si un archivo que se ha experimentado una restauración, por ejemplo, perdido una mota de polvo, no es necesario tener un archivo nuevo para esta clase de cambios menores durante la restauración.) In algunos casos como los archivos originales marcados con {{Please-do-not-overwrite-original-files}}.

The symbol for Featured Pictures

? Tenga cuidado con archivos que han sido adjudicados como estado especial como Imágenes destacadas que serán identificadas en Imágenes valiosas que serán identificadas en su descripción usando {{Assessments}}.

archivos "usados en los proyectos de Wikimedia donde su uso requiere que el archivo se mantenga intacto" -lo que significa no sobreeescribirlo del todo: No para actualizaciones, mejoras menores, o corrección de errores. Los comentarios (incluyendo apuntar los errores, y apuntar a otras versiones) pueden ir libremente en la descripción del archivo de Commons, pero el archivo en si no debe ser sobreescrito. De ser necesario, suba una nueva versión como un archivo separado. Dichos archivos deben ser marcados como {{Please-do-not-overwrite-permanent-version}}.

Cambios polemicos o controversiales. Si otro editor piensa que el cambio no es una mejora (incluso si el editor marco este cambio como menor), el cambio puede ser revertido, y el nuevo archivo debe ser subido bajo un nuevo nombre. Véase más abajo.

Respecto a los creadores de contenido

The original image creator is often the best person to make edits. Since JPG is a lossy format, every edit to a JPG can deteriorate the image slightly; seemingly minor and "beneficial" edits such as changing white balance or adding noise reduction can actually do significant damage. Often the image creator has access to the RAW files from which to make a new version with whatever fix is required. This is always superior to editing the JPG. If it is a photograph, the image creator was there when the picture was taken so will be in a better position to judge whether colours and lighting are correct. Therefore it is strongly recommended that users wishing to make improvements to photographs first contact the creator, whether on Commons or elsewhere.

Versiones sin editar

Sometimes users uploading new files that have been edited (eg a photograph improved for colour, contrast, etc, compared to the raw photo) may wish to provide the original unedited version as well. Uploading these independently would needlessly clutter categories. The solution is to first upload the unedited version, and then shortly afterwards to upload the edited version over it, so that the unedited version is available in the file history. The unedited versions are not intended to be used independently, and should not be split out as separate files unless this is needed for a specific known use. Files using this approach should be labelled with {{Unedited version}}.

Note: overwriting unedited versions applies only shortly after upload of the unedited version, and only to the original uploader when uploading an improved version of the same file. In all other cases, the usual criteria about overwriting apply (is it minor improvement? etc). In addition, the usual rule about resolving disagreements applies: if another user feels it useful to split the file, it should be split.

Imágenes secundarias

Sometimes users may wish to provide an image related to their upload, which might fall outside the Project scope as an independent file. Examples include images of labels related to the subject of the main image, or the reverse of a postcard as evidence of copyright status. The solution is to first upload the secondary image, and then shortly afterwards to upload the main image over it, so that the secondary image is available in the file history. The secondary images are not intended to be used independently, and should not be split out as separate files unless this is needed for a specific known use. Files using this approach should be labelled with {{secondary image}}. Note that secondary images are not exempt from the usual requirements of Commons:Licensing.

Note: overwriting secondary images applies only shortly after upload of the secondary image, and only to the original uploader. In all other cases, the usual criteria about overwriting apply (is it minor improvement? etc). In addition, the usual rule about resolving disagreements applies: if another user feels it useful to split the file, it should be split.

Archivos con los datos actuales

Ten cuidado al sobreescribir archivos con nuevas versiones que reflejen nueva información, como en varios casos que puede no ser lo que quieren los reutilizadores.

However, files may be identified to reusers as ones where information may be updated - these files can and should be overwritten to reflect new information as necessary. Identification may be by the filename, file description, or (most clearly) with the {{current}} template. A file named "File:Germany location map.svg" is expected to indicate the current boundaries, and is expected to be updated if, for example, the boundaries changed or errors were observed. On the other hand a file named "File:Germany, Federal Republic of location map October 1949 - November 1950.svg" is expected to be correct for that period and not reflect current boundaries.

NO sobrescribir

Excepciones a la regla de cambios menores

• Excepciones a la regla de "cambios menores que deben ser subidos bajo el mismo archivo" ("véase más abajo")
  • Restauración digital
  • Files that have been awarded a special status like Commons Featured Picture, Commons Quality Image, or similar status on another Wikimedia project. Such files are marked with {{Assessments}}.
  • Files used in Wikimedia projects where the use requires the file to remain unchanged
  • Controversial or contested changes - see below.
  • Removing parts of historical images.

For instance, historical engravings often have a border, and text describing the image under the image. If it was part of the original composition, and you want to remove it for some use on Wikimedia sites, upload it as a new file. If there are annotations or markings in the image that weren't part of the original composition, these can be removed and placed in the metadata: for example, in the case of the Bundesarchive images, this is usually a call number and date of the photograph, etc.), this can be edited out and placed into the {{information}} template, without a need to upload as a new image.

Substantial changes

• Major changes (eg a radical crop)
• Changes that reflect different data (eg updating a map)
  • unless the file is marked as updateable - i.e. identified to reusers as one where information may be updated, by the filename, description, or with the {{current}} template

Unrelated files

• Completely unrelated files
  • Different files on the same topic (such as a photo of a cow uploaded over another photo of a cow)
  • Different files relating to the exact same object (eg a different photo of Michelangelo's David)
  • Note: do not overwrite a file in order to delete it; follow the Commons:Deletion policy instead.

Controversial or contested changes

Changes to a file that are likely to be contested should be uploaded to a separate filename. Upload wars (a form of edit war in which contributors repeatedly upload different versions of a file in an effort to have their version be the visible one) are always undesirable. As with other forms of edit warring, users who engage in upload wars may be blocked from editing.

If another editor thinks that a change is not an improvement (even if the editor making the change thinks it minor), the change can be reverted. Once a change has been reverted, the new image should be uploaded under a new filename (unless the reverting editor explicitly or implicitly agrees to the contested change). This is true even if the change is necessary, in one editor's view, to avoid a copyright infringement: in this case, if agreement cannot be reached through discussion, the old file should be nominated for deletion.

The more known uses of a file there are (through transclusions on Wikimedia projects), the more cautious contributors should be in deciding whether a change qualifies as "minor". Widespread usage of a file makes it more likely that even small changes will be controversial. If in doubt, uploading as a separate file avoids potential surprises for reusers. In some cases, prior discussion with previous uploader(s) or in locations where the file is in use may help decide whether a planned change can be considered "minor".

Ejemplos

Pequeñas mejoras

Véase, por ejemplo, la versión de las historias de

• File:Avestaforsen.jpg, which is essentially the same image, with several subtle corrections applied
• File:15th anniversary of Image Comics - seven founders.jpg, which has minor cleanup
• File:Chess Board.svg, which has always identical appearance but underwent several improvements of its coding
• File:Wappen Kottmarsdorf klein.gif - a GIF version of a coat of arms, recreated from the SVG version, replacing a much lower resolution GIF. Even though the improvement is dramatic, because there is no change in the design or composition, this is considered a minor improvement.

Minor improvements for textual elements include correcting spelling on a map's labels. By contrast, translating a map's labels from English to German is a major change, and should be uploaded as a separate file.

Substantial crop or un-crop

Further information: Commons:Media for cleanup #Unnecessary borders

Whether a crop is "substantial" depends partly on the proportion of the image cropped, and partly on how much the excluded content affects the composition. File:Miyasaka Hakuryu II - Tigress with Two Cubs - Walters 71909.jpg is an image of a museum object on a grey background; cropping much closer to the object was considered a minor crop. On the other hand, the photograph below of Martin Scorsese was substantially cropped for a closeup on his face, and the result was put into a separate file; and the photograph below of a mountain was cropped to substantially recompose it.

• 

  Scorsese: Original image

• 

  Scorsese: Image cropped for closeup

• 

  Zizalga: Original image

• 

  Zizalga: Image cropped for recomposition

When cropping a JPEG image, remember to always use lossless cropping.

• Example: This 1899 portrait of a young man with a fish by Wilhelm von Gloeden was uploaded in 2005 but then overwritten in 2010 by a full length un-cropped version. Though the intent was to restore the image to a better quality version, the overwrite proved highly controversial as it changed the context from a modest pose to a nude with potential erotic connotations. In some existing transclusions this change was unwanted and caused controversy. Uploading the higher quality image as a separate file would have avoided this.

Unedited versions

• Example: File:Homenagem ao Padre Fernando Augusto da Silva, Santo António, Funchal, 1927.jpg is an image from 1927, with the original unedited scan uploaded first, and then the improved version uploaded a minute later.
• Example: File:Periquitos - Psilopsiagon aymara.jpg is a cropped version of File:Psilopsiagon aymara -Capilla del Monte -four-8.jpg, and has the uncropped original version in the file history.
• Counter-example: File:Wounded Knee aftermath3.jpg is a digitally enhanced version of the unedited original File:Wounded Knee aftermath.jpg. During the restoration it was discovered that what was described as "debris" in the original were dead bodies. Though the restoration itself was non-controversial, overwriting the original with such an important change of context would be considered controversial, and for that reason alone the images should be kept as separate image pages.

Secondary images

• Example: File:Neapolitan Fisherboy.jpg is an image of a sculpture, and contains an image of the sculpture's label in the file history.
• Example: File:William Shatner Star Trek.JPG is a publicity photo of William Shatner as James Kirk from the television program Star Trek, and the oldest image in the file history is used to verify the public domain status.

Files with current data

Examples:

• 

  2014 Pacific typhoon s...
  

• 

  2014 Atlantic hurrican...
  

• 

  IAEA members.svg
  

• 

  Shanghaimetro Current.svg
  

• 

  Germany location map.svg
  

• 

  United States installe...
  

Controversial or contested changes

• Example: File:Kit body rmcf1213a.png had two upload wars over the content of a Real Madrid kit.

Permanent versions

• 

  A news photo used on Wikinews

Linking files

Attribution

Be sure to attribute the original author appropriately, and to apply a license compatible with the original file. You can use {{Derived from}} and {{derivative versions}} to link the files. More specific derivative templates are also available, including {{Image extracted}}, {{Retouched picture}}, {{AttribSVG}}.

Using "other versions" field of Information template

The template {{Information}} has an |other versions parameter which you can use to link between different versions of a file. You can

• use the {{thumbnail}} or {{Other}} templates to show a small preview of the linked file
• use a <gallery> tag to show different versions (see meta:Help:Images and other uploaded files#Gallery)
• use an "other versions" template containing a gallery tag to link different versions (see Category:Other versions templates).

Link to a variable content

When you want to provide or use a stable link from the other projects for any image which is anticipated to be repeatedly updated, you have several ways to do it:

• Label the image page with the {{current}} template (see #Files with current data). The main disadvantage is that the old version cannot be directly linked if needed.
• Create a file redirect page under a fictive filename on Commons and use a link to this filename on the other projects. Change the redirect to each new version (inbound links from other projects need not to be updated). This means updating just one link instead of many. (Note the effect of overwriting or switching over can be delayed slightly through cache delay or can fail through software imperfection.) Example: link to File:Africa borders redirect on Wikipedia, and on Commons have File:Africa borders redirect point to File:Africa borders 2011, File:Africa borders 2012, etc as needed.
• Combine the two methods. Particular version can be uploaded (and linked) separately under their specific permanent filenames and a different filename can be marked with {{current}} version and overwritten ever by the current version. That means (just as the previous solution) that the current version is available under two filenames: one for the constant content and one for the updatable content. This solution should be more immune towards cache delay and software-update bugs than the previous one.

Warning: when doing one of these solutions, be sure that users of the filename are clear that the content of the file may change, and try to check uses of the file before updating the redirect or overwriting the file.

Notes

1. ↑ Un archivo puede ser sobre escrito por cualquiero usuario con una cuenta de al menos 4 días de eantgüedad desde la descripción de la página del archivo usando el enlace Subir una nueva versión de este archivo debajo del Historial del archivo; o a través de Special:Upload. Special:Upload provee dos mensajes de advertencia a la hora de sobreescribir un archivo - MediaWiki:UploadFormPreviewOverwriteError y MediaWiki:Fileexists (véase también Bugzilla:39344). UploadWizard no permite sobreescribir archivos.

See also

• Ask a user not to overwrite files: To request that another editor not overwrite an existing file, you may place {{Dont overwrite}} on the user's talk page. This request is automatically translated into many languages.
• Request a file split: You can request a split up of file history by adding {{Split}} on the file page. This places the file in Category:Media requiring a split up.
• Label a file not to be overwritten: {{Please-do-not-overwrite-original-files}} may be used on file pages to designate files that should not be overwritten.
• Image formatting templates may save having to create a new file version. For example, temporary or illustrative crops may be created using {{Preview Crop}} rather than creating a new derived image or overwriting an existing image. Images may be overlaid without having to create new derivatives by using the {{Superimpose}} template.

Help

Ways to get help

Mira en las Preguntas frecuentes If you place {{helpme}} on your talk page, a volunteer will visit you there as soon as possible! Join the #wikimedia-commons IRC channel for real-time chat. New to IRC? Click here to be connected instantly! Go to the Commons Help Desk.

Other policies and guidelines

Políticas y recomendaciones de Wikimedia Commons Políticas Proyecto Aviso legal Política de protección de datos Alcance del proyecto Tipos de archivo Evidencia Punto de vista neutral Principio de precaución Páginas, galerías y categorías Contenido Sobre las licencias De minimis Uso razonable Cuándo usar la etiqueta PD-Art Normas de borrado Borrado de ediciones Criterios para el borrado rápido Política de idiomas Category policy Comportamiento Política de bloqueo Protección de páginas Revocación de los privilegios de administrador Paid contribution disclosure Translation administrators Firmantes Username policy Recomendaciones Contenido What Commons is not Non-copyright restrictions Fan art Desnudez Fotografías de personas identificables Trabajos derivados Cuándo usar la etiqueta PD-scan Galerías Notas en las imágenes Renombrar un archivo Sobrescribir archivos existentes Grandfathered old files Comportamiento Assume good faith Propiedad de las páginas y archivos Recomendaciones de páginas de discusión Política de galerías, plantillas y categorías específicas de usuario Vandalismo Revertir Patrulla Licensing help Choosing a license Copyright rules Copyright rules by subject matter Copyright rules by territory Marcas de derechos de autor PD files Copyright special cases Trabajos derivados De minimis Libertad de panorama 2D copying Umbral de originalidad Using files Reutilización del contenido fuera de Wikimedia Tarjeta de crédito Reuse of PD-Art photographs Como detectar infracciones de derechos de autor Lavado de licencia Problematic sources Flickr Picasa Web Bad sources Revisor de licencias Portal de la comunidad Help contents