Commons:파일 이름 변경
Shortcuts: COM:FR • COM:MOVE • COM:RENAME
|
이 문서의 요지는: The file rename function allows authorized users to rename files based on specific criteria, such as improving file names, correcting errors, harmonizing names, and avoiding policy violations. Users can request a rename by filling out a form or using a user script. File redirects are preferred, but in some cases, redirects can be suppressed. |
- "COM:MOVE은 여기로 연결됩니다. 다른 프로젝트에서 파일 이동에 대한 자세한 내용은 Commons:공용으로 파일 이동을 참고하세요.
파일 이름 변경 기능을 사용해서 마치 문서 이동을 하는 것처럼 파일의 이름을 다시 지을 수 있습니다. 모든 사용자는 파일 이름 변경을 신청할 수 있지만, 이름을 실제로 변경할 수 있는 것은 특정 권한을 가진 사용자들뿐입니다.
이름을 변경해야 하는 파일들에는 어떤 것들이 있나요?
Whether a filename is perceived to be suitable often depends on the familiarity of the individual with the subject, which is often the place depicted. It also occurs that items are known under different terms to different contributors or they believe entities are primarily well-known under the term they are used with to describe this entity, neglecting cultural differences, even within countries.
Not of less importance is the purpose the filename is believed to have; contributors frequently categorizing files have different demands from those who create, process, manage and upload them. Uploaders often have schemas naming their files; moving files might break them. If possible, language and schema should be preserved, as well as the camera or catalogue number.
문제가 발생하지 않는 파일 이름 변경의 이유는 7가지가 있습니다.
| # | 목적 | 예 (변경 전) | 예 (변경 후) |
|---|---|---|---|
| 1. | 본래 올린 이가 요청한 경우.[1] | ||
| 2. | 의미 없거나 모호한 이름을 가진 파일의 내용을 알맞게 고칠 때[2] | File:DSC 1342.jpg (전혀 정보가 없는 경우) | File:Pretoria Venningpark DSC 1342.jpg |
| File:20110428 OH K1023900 0014.JPG - Flickr - NZ Defence Force.jpg (only photographer or rights holder) | File:Helicopter A109LUH(NZ) by NZ Defence Force.jpg | ||
| File:20120519 3349.CR2.png (날짜만 있는 경우) | File:Sebkha-Chott 3349.png | ||
| File:Paris 319.jpg (넓은 범위의 위치만 있는 경우) | File:Paris 75018 Rue Norvins no 018 Le Consulat z.jpg | ||
| File:Smartphone.jpg (포괄적인 범주인 경우) | File:Samsung Galaxy Note series (Original, II, and 3).jpg | ||
| File:RAS.jpg (약자나 이니셜인 경우) | File:Rodrigo Arias Sánchez.jpg | ||
| File:Flickr - law keven - Anybody know a Good Dentist^......Happy Furry Friday Everybody...-O))).jpg (파일 내용과 관련이 없는 경우) | File:Lion-tailed Macaque, Colchester Zoo, England.jpg | ||
| File:Louvre 12.jpg (inappropriate for specific content) | File:Mona Lisa by Leonardo da Vinci.jpg | ||
| 3. | 잘못되었거나 오해의 소지가 있는 이름을 고칠 때[3] | File:Ayres Rock 3.png File:Van Gogh portrait 1787.jpg File:Unknown insect 02.jpg |
File:Ayers Rock 3.png File:Van Gogh portrait 1887.jpg File:Hogna radiata 02.jpg |
| 4. | 다른 유사한 파일의 이름과 조화시키려 할 때[4] | File:Bhf-BS-Icon.svg File:Icon HST bs 1.svg File:Dst symbol.svg |
File:BSicon BHF.svg File:BSicon HST.svg File:BSicon DST.svg |
| 5. | To change a filename that would be a violation of Commons’ policies and guidelines if it appeared elsewhere on the project as text. This includes gratuitous vulgarity, personal attacks/harassment, blatant advertising, and cases where revision deletion would be authorized.[5] | File:Stupid fat idiot.jpg File:Buy now NEW PAINT! 555-6200.png |
File:<Name of the person>.jpg File:2007 pink Honda Accord.png |
| 6. | 논란의 여지가 없는 유지보수 및 버그 수정, including fixing double extensions, invalid or incorrect extensions, character handling problems, and other similar technical issues.[6] | File:Map of Asia.svg.png File:Computer mouse.jpe File:Mooncake.jpg, File:Mooncake.JPG |
File:Map of Asia.png File:Computer mouse.jpg File:Mooncake.jpg, File:Square Mooncake.jpg |
- 추가 정보
- Please consider creating file redirects instead, where applicable and possible. They are cheap, usually do not break anything and are easily edited or deleted, if required.
- ↑ 특별한 이유가 없는 한 업로더 요청은 존중되어야 합니다. 하지만 이것은 업로더에 대한 예의이지 절대적인 권리는 아니며 파일 이동자가, 제안 된 새 파일 명이 부적절하다고 느낄 경우 다른 이름을 제안하거나 요청을 거부할 수 있습니다.
- ↑ Including:
- 전혀 정보가 없는 경우
Composed entirely of random letters, numbers, and words like “Flickr”, “original”, and “crop”, which do not describe the subject of the image, but may indicate its upload history. - Only information is the photographer or rights holder
The only piece of meaningful information is the name of the photographer or the holder of the copyright. - 날짜 정보만 있는 경우
Only piece of meaningful information is the date that the photograph was taken on. - Only information is the location (broad)
The only piece of meaningful information is a broad location, such as a city, province, or country. In this case, the location is so large that an average person would not be able to figure out where the image was taken or what the image depicted, without assistance from someone that knows the area. - Generic category rather than specific item
The only piece of meaningful information is a word, such as “smartphone” or “screenshot”, which broadly describes the subject of the file, but does not impart any information that would help someone identify the specific object depicted. This is not just restricted to inanimate objects, it also applies to broad titles or groupings, such as “queen” or “bird”. - Acronyms and initials
The only piece of meaningful information is an acronym or a person’s initials. This differs from “Absolutely no information at all” in that the acronym or initials are related to the subject of the file, even if it takes a second to figure out how. - Names that are not meaningless, but do not describe the file
Contains a coherent description or message that do not describe the subject of the file. Does not apply in cases where the name of the file is the title given to a work of art by the artist that created it, even if the name has nothing to do with what is depicted (for example, many works of Dadaism). - Images where the information in the filename, while normally acceptable, is inappropriate for the specific content.
Not including: Specific locations, such as a park, an individual building, or an event.
- 전혀 정보가 없는 경우
- ↑
If an object or organism was incorrectly identified in the filename (such as calling a Sylvilagus floridanus by the name “File:Sylvilagus audubonii.jpg”), this criterion covers renaming the image. If the filename includes words like “unidentified” or “unknown” when describing an object or organism, and that object or organism has been identified, this criterion also covers the change. This criterion does not, however, cover moving a file from its common usage name to its scientific or technical name.
- ↑
Just because images share a category does not mean that they are part of a set. There are two scenarios that this criterion is designed for. First, certain complex templates (such as those that use BSicons or that display football kits) assume that the images used in them will follow a specific naming convention. Wikisource also uses a specific naming convention for the source files they transcribe. Second, files that form parts of a whole (such as scans from the same book or large images that are divided into smaller portions due to Commons’ upload size restriction) should follow the same naming convention so that they appear together, in order, in categories and lists.
- ↑
Note that Commons’ neutral point of view differs significantly from that of English Wikipedia. A file like “File:Taiwanese Tiaoyutai islands map.png” would be acceptable on Commons, even though it is not neutrally titled (see here). This does not mean that all non-neutrally worded titles are acceptable, however. An image of a person with the name “File:1BIGGest_nOSE_everS33n.JPG” would not enjoy the same protection.
- ↑
This is not a catch-all for anything that doesn't fit one of the above. This is for specific technical problems, generally which have a Phabricator task and have been the subject of community discussion.
- View →the discussion that led to the selection of these criteria.
이름을 변경하면 안되는 파일들에는 어떤 것들이 있나요?
As a matter of principle it's best to leave all files with generally valid names at their locations, even if slightly better names may exist. So for example:
| # | Criteria to decline | Examples (old name) | Examples (new name) |
|---|---|---|---|
| 1. | Files should NOT be renamed only because the new name looks a bit better. | File:TowerBridge'09.jpg | File:Tower_Bridge_2009.jpg |
| File:Logo_correct.jpg | File:Logo.jpg | ||
| 2. | Files should NOT be renamed only to translate the filename to another language and/or because the filename is not correctly capitalized. Remember, Commons is a multilingual project, so there's no reason to favor English over other languages. | File:Rathaus_bremen.jpg | File:Bremen_town_hall.jpg |
| 3. | If a filename in a local project conflicts with a filename at Commons, the file in the local project should be renamed. Renaming it at Commons would mean changing it in a lot of projects instead of just one. | ||
| 4. | Files with copyright issues should NOT be renamed until copyright issues are resolved. There is no reason to rename a file if it is going to be deleted on copyright grounds. |
Additional naming conventions and exceptions from the above list might be discussed for specific projects. For example, moving PDF and DjVu files transcluded at the Wikisources is problematic for those wikis and should be avoided unless the file mover understands the consequences.
A user repeatedly renaming files under invalid reasons can be stripped of the filemover privilege. Warning: certain cases of wheel-warring—such as reversal of a preceding renaming which had a valid reason—may result in removal of the filemover privilege even for one infraction.
파일 이름을 바꾸는 방법
어떤 사용자든 파일 이름 변경을 신청할 수 있지만, 실제 변경이 가능한 것은 권한을 가진 사용자들뿐입니다.
To request a file rename while logged in, select "More → Move" near the top right of the file page, then fill in the provided form (this functionality is provided by the default gadget RenameLink). Users who do not have an account or are unwilling to run JavaScript can request a file rename by adding the template
- {{Rename|required newname.ext|required rationale number|reason=required text reason}}
to the file description. Either way, the file will be added to Category:Media requiring renaming and an authorised user will perform the move if it conforms to the guidelines described above. There could be a delay of a few hours to several days depending on the type and language of the request.
Responding editors should follow the instructions on the template. In most cases, a file redirect should be left on the original page, except if it is a misleading or promotional name.
이름 변경 권한을 가진 사용자에는 관리자, 파일 이동자, 위키미디어 사무장이 있습니다. 파일 이동자가 되고 싶다면 $request에서 요청합니다. 만약 이 그룹에 속해 있다면 movefile 권한을 갖고 있기 때문에, 보통 일반 문서를 옮기는 것처럼 "이동 & 치환하기" 탭을 이용하면 됩니다.
대량 이름 변경
A user script that can rename many files: User:Legoktm/massrename.js.
File name swaps
To perform file name swaps, you need the suppressredirect right. For example, somebody uploaded two files: "Obverse Of Token.jpg" and "Reverse Of Token.jpg", but the "obverse" image shows in fact the reverse side, and the reverse shows the obverse side. In this case, you'd have to:
- Move "Obverse Of Token.jpg" to "Temporary name Of Token.jpg" without leaving a redirect.
- Move "Reverse Of Token.jpg" to "Obverse Of Token.jpg" without leaving a redirect.
- Move "Temporary name Of Token.jpg" to "Reverse Of Token.jpg" without leaving a redirect.
넘겨주기 남기기
이동하기 탭을 사용하여 파일을 이동, 즉 이름을 변경하면 기본적으로 기존의 파일명은 자동으로 새로운 파일명으로의 넘겨주기 문서가 됩니다. 또한 기존 파일명의 섬네일로 가는 url도 넘겨주기가 됩니다. 그러나 파일의 풀 사이즈 버전으로 가는 다이렉트 링크는 넘겨주기가 되지 않습니다. 이동된 파일로의 념겨주기는 Move& Replace를 사용하는 경우 이중 넘겨주기를 막기 위해 자동으로 업데이트됩니다.[1] Move & Replace를 사용하지 않는 경우 파일로 가는 모든 넘겨주기를 직접 수동으로 수정해야 합니다.
모든 파일 이동자들은 suppressredirect 권한을 가집니다.[2] 이를 통해 파일 이동자들은 파일을 이동했을 때 넘겨주기를 남기지 않고, 원래의 파일명은 자동으로 삭제되도록 할 수 있습니다. 유념할 점은 정책상 넘겨주기를 삭제하는 것이 필수는 아니라는 점이며, 넘겨주기를 삭제할지 남길지는 전적으로 선택사항입니다.
넘겨주기를 남기지 않는 것은 다음의 경우에만 허용됩니다.
- To move recently uploaded files with an obvious error in the file name where that error would not be a reasonable redirect. For example: moving "Sheep in a tree.jpg" to "Squirrel in a tree.jpg" when the image does in fact depict a squirrel.
- To perform file name swaps.
- When the original file name contains vandalism. (Renaming criterion #5)
Please note, this ability should be used only in certain circumstances and only if you are absolutely sure that it is not going to break the display of the file on any project. Redirects should never be suppressed if the file is in use on any project. When in doubt, leave a redirect.
If you forget to suppress the redirect in case of file name vandalism or you are not fully certain if the original file name is actually vandalism, leave a redirect and tag the redirect for speedy deletion per G2.
The malicious or reckless breaking of file links via the suppressredirect user right is considered an abuse of the file mover right and is grounds for immediate revocation of that right.
넘겨주기를 만들지 않는 방법
If you are using the move and replace script there will be a checkbox that says "Leave a redirect behind". This is automatically checked and cannot be turned off if the file is in use. If the file is not in use, unchecking the box will suppress the redirect and one will not be created upon moving the file. The "Leave a redirect behind" checkbox is also available on the general special page, Special:MovePage, which can be found by searching for Special:MovePage/PAGENAME in the search bar.
To easily bypass the move and replace script on file pages and use the special page instead, a new tab must be opened through the move and replace button. Depending on your mouse settings you may be able to do this by "middle clicking" (clicking the mouse wheel) on the move and replace button. For others you can right click on the move and replace button and open in a new tab. Please note, the special page will not attempt to replace any usage of the file on any pages it is on.
이름을 변경하면 기록에 남나요?
모든 파일 이름 변경은 이동 기록에 기록됩니다. 이동 기록에는 모든 이름공간에서의 모든 이동 기록이 남아 있습니다. "파일만" 열람 가능한 이름공간 필터는 아직은 사용할 수 없습니다.
파일 이동자 현황
- 파일 이동자 목록 (현재 1,635명)
- 관리자 또한 파일 이동 기능을 사용할 수 있습니다. (현재 185명)
- 사무장은 모든 위키미디어 프로젝트의 파일 이름을 바꿀 수 있습니다. 개요는 메타 사무장 목록을 참조하십시오.
같이 보기
- Category:Media requiring renaming (by rationale) — category for files to be renamed.
- Rights of the filemover group
- Commons:Filemover statistics
- Commons:Rename a category
- Commons:Rename a template
- Help:File redirect
- Massrename tool
- MediaWiki:Filename-prefix-blacklist — filenames that the MediaWiki software itself prevents from being uploaded.
- Commons:File renaming/Global replace
- Recently declined rename requests
