Rules of the RePEc Biblio

RePEc Biblio is based on user contributions and needs a few rules to function well. These rules may be amended as experience is gathered from the project.
  1. RePEc Biblio uses a tree data structure, with each main topic branching into subtopics, and those into further subtopics, and so on.
  2. An editor is in charge of any topic and may assign branches to him/herself or to new editors.
  3. A topic becomes lives if it has a least 10 valid bibliographic entries.
  4. A topic may have up to 20 bibliographic entries.
  5. To be valid, a bibliographic entry has to be currently listed on IDEAS. The editor must enter an entry using a RePEc handle, and the system will then pull the full reference, including other versions of the work, if available.
  6. The editor may add as many self-references as the level of the branch. For example, at level five, five self-references are allowed. This rule is to acknowledge that the narrower the topic, the more difficult it is to avoid self-referencing.
  7. Potential editors can petition an existing editor to open a new subtopic. If there is no appropriate editor, petition the RePEc Biblio administrator, currently Christian Zimmermann.
  8. Every editor needs to be registered with the RePEc Author Service.
  9. There is a link back from the IDEAS abstract page for each reference to the relevant topic.
  10. Complaints regarding poorly selected content should be addressed to the editor higher in the hierarchy of the branch and then to the RePEc Biblio administrator, if warranted. OPne can also use the rating system for each topic.
  11. Editors maintain a web form for each of their assigned topics that contains the following fields: a paragraph of text with up to 2000 characters, up to 3 JEL codes, up to 2 NEP reports, 1 link to another page (for example, Wikipedia, a specialized site), at least 10 but no more than 20 bibliographic entries, up to 26 new branches, and a scratch space that remains private. See a sample of this webform.