|
| INCLUDEFILE(jagt_mac.yo)
|
| notableofcontents()
|
|
| article(Distributed Cataloging on the Internet: the
| RePEc project
| +whenlatex(+latexcommand(\footnote{)The work
| discussed here has received financial support by the Joint
| Information Systems Committee of the UK Higher Education Funding
| Councils through its
| url(Electronic Library Programme)(http://www.ukoln.ac.uk/services/elib).
| We are grateful to
| url(Christopher F. Baum)(http://fmwww.bc.edu/EC-V/Baum.fac.html),
| url(Robert P. Parks)(http://wueconb.wustl.edu/~bob/),
| url(Thorsten Wichmann)(http://www.berlecon.de) and
| url(Christian Zimmermann)(http://www.er.uqam.ca/nobel/r14160/index.html)
| for comments on the questionnaires.
| url(William L. Goffe)(http://wuecon.wustl.edu/~goffe/)
| and Christian Zimmermann
| made many helpful suggestions.
| The topic of link(Subsection ref(sec:upta))(sec:upta)
| was suggested by url(Jane Greenberg)(http://ils.unc.edu/~janeg).
| Sophie C. Rigny kindly pointed
| out many stylistic and grammatical errors in an earlier version.
| +latexcommand(})))
| (Jos\'e Manuel Barrueco Cruz and Thomas Krichel)
| ()
|
| latexcommand(\thispagestyle{empty})
|
|
| latexcommand(\vfill\begin{center}) table(2)(ll)(row(cell(url(Jos\'e Manuel
| Barrueco Cruz)(http://www.uv.es/~barrueco )) cell(url(Thomas
| Krichel)(http://gretel.econ.surrey.ac.uk))) row(cell(url(Biblioteca de
| Ci\`encies Socials dq(Gregori Maians))(http://www.uv.es/econweb/))
| cell(url(Department of Economics)(http://www.econ.surrey.ac.uk)))
| row(cell(url(Universitat de Val\`encia)(http://www.uv.es))
| cell(url(University of Surrey)(http://www.surrey.ac.uk))) row(cell(Campus
| dels Tarongers s/n) cell(Stag Hill)) row(cell( 46071 Val\`encia ) cell(
| Guildford GU2 5XH )) row(cell( Spain ) cell( United Kingdom))
| row(cell(url(jose.barrueco@uv.es)(mailto:jose.barrueco@uv.es))
| cell(url(T.Krichel@surrey.ac.uk)(mailto:T.Krichel@surrey.ac.uk)))
| whenlatex(row(cell(tturl(http://www.uv.es/
| +latexcommand(~)barrueco))
| cell(tturl(http://gretel.econ.surrey.ac.uk))))
| row(cell( )
| cell( RePEc:per:1965+endash()06+endash()05:thomas_krichel)))
| +latexcommand(\end{center})
|
| abs(Cataloging educational resources requires a finer level of granularity
| than many other objects. Collecting that data is a costly process to
| achieve and manage. One possible approach towards cataloging these
| resources is to get a commonity of providers involved in cataloging the
| materials that they provide. This paper introduces RePEc of
| http://netec.wust.edu/RePEc, as an example for such an approach. RePEc is
| mainly a catalog of research papers in Economics. It is based on set of
| over 80 archives which all work independently but yet are interoperable.
| They together provide data about almost 60,000 preprints and over 10,000
| published articles. In principle each institution participating in RePEc
| provides its own papers by providing and maintaining an archive. The key
| issue of the paper is to evaluate the success of that decentralized
| approach in providing data of reasonable quality. )
|
| latexcommand(\vfill)
|
| Jos\'e Manuel Barrueco Cruz is a librarian at the Universitat de
| Val\`encia. Thomas Krichel is a lecturer in Economics at the University of
| Surrey. Both welcome comments on this paper, write to
| wopec@netec.mcc.ac.uk. whenlatex(This paper is available online at
| tturl(http://openlib.org/home/krichel/papers/jagt.html).) whenhtml(This
| paper is url(available in
| PDF)(http://openlib.org/home/krichel/papers/jagt.pdf).)
|
|
|
| latexcommand(\vfill)
|
|
| sect(Introduction)
|
|
| The Electronic dissemination of Economics working papers can be traced back
| to the start of the Working Papers in Economics
| (url(WoPEc)(http://netec.mcc.ac.uk/WoPEc.html)) project in April 1993. By
| May 1999 this single archive has grown into an interconnected network of
| over 80 archives holding over 14,000 downloadable working papers and over
| 50,000 descriptions of offline papers from close to 1,000 series. The
| network of archives is called url(RePEc)(http://netec.wust.edu/RePEc).
| This term is was initially conceived to stand for dq(Research Papers in
| Economics). Nowadays it is best understood as a literal, because the
| objectives of RePEc go way beyond a database of scientific papers. In
| link(Section ref(sec:repec))(sec:repec) we will introduce some of the
| broader aspects of RePEc.
|
| RePEc data is freely available, in the sense that the provider pays for the
| provision of the data, not the user. In order to make such a system viable
| without public subsidy, the cost of providing the data must be spread among
| many agents+footnote(understood here and in the rest of the paper as a
| person or institution). This requirement has been a feature of RePEc right
| from the start of the collection in May 1997. Each participating provider
| sets up an archive on a http or ftp server. The archive supports the
| storage of structural data about objects relevant to Economics, and
| possibly the storage of some of the objects themselves. All objects in
| RePEc are uniquely identified following by handles.
|
| RePEc data can be accessed through a plethora of user services. Some
| are heavily used, for example the dq(url(IDEAS)(http://ideas.uqam.ca))
| user service had one million hits in just over 2 moths in 1999.
| The main interest of this paper is to examine the collection aspect of the
| data. The idea that a coherent literature catalog can be put together by a
| large group of people who are physically dispersed and have very little
| personal commonication without the need of extensive training nor intensive
| coordination remains to be demonstrated. At the time of writing this paper
| RePEc is two years old. We feel that this is a good time to review the
| operations of RePEc and the data that it has collected. Clearly the RePEc
| data is in a constant state of flux. To keep matters simple we took a dump
| of the data on 1 May 1999. In this paper we are only referring to the state
| of the data on that date.
|
| There are some aspects of RePEc that this paper does not discuss. We
| eschew any mentioning of the data on software, books, etc to concentrate on
| the collection of traditional academic papers be they preprints or
| published articles. This data forms the bulk of the present collection. We
| also leave out the personal and institutional data which are is not included in
| the papers and article templates. We aim to use such data to build a fully
| relational database system that describes Economics as a discipline. We
| will report on such efforts in future papers.
|
| In link(Section ref(sec:indi))(sec:indi) we
| describe the setup of an individual archive through the use of an example. In
| link(Section ref(sec:soci))(sec:soci) we look at the actual network of
| archives and the social fabric that supports them. In link(Section
| ref(sec:data))(sec:data) we look at some aggregative aspects
| of the complete RePEc dataset.
| In link(Section ref(sec:user))(sec:user) we introduce the user services that
| implement RePEc data. link(Section ref(sec:conc))(sec:conc)
| concludes this paper with an overall evaluation of the methods used by
| RePEc.
|
|
| sect(RePEc)label(sec:repec)
|
| The nature of RePEc is not precisely defined. Most people
| think about it as a collection
| of archives and services that provide data about Economics.
| More precisely, RePEc is most commonly understood as referring to three
| things. First it is a collection of archives that provide data about
| Economics. Second it is the data that is found on these archives. Third, it
| is often also understood to represent the set of agents who build archives
| and channel the data from the archives to the users. In that latter sense
| RePEc has no formal management structure.
|
| RePEc has two aims. The dq(cataloging aim) is to provide a complete
| description of the Economics discipline that is available on the Internet.
| The dq(publishing aim) is to provide em(free)+latexcommand() access
| to Economics resources on the Internet.
|
| COMMENT(--- Este ejemplo creo que no es claro. Yo lo quitaria pues no aporta
| nada nuevo, solamente matiza lo anterior a un nivel que puede confundir
| al lector
|
| These aims are sometimes conflicting.
| For example, let us assume that a certain amount of money is available for
| cataloging purposes. Then the library objective might be best served by
| using these funds to gather information about a high-quality toll-gated
| journal resource, whereas the publishing objective would be better served
| by considering a collection that is on the Internet and may not be of the
| same quality since it has not yet been extensively peer-reviewed. RePEc
| has ambition to become involved in
| peer-review; however it can be used to support peer
| review. An initial move into that direction is the NEP project that we will
| mention again in link(Section ref(sec:user))(sec:user).
|
| --- )
|
| The basic principle of RePEc can be summarized as follows center( Many archives
| +latexcommand( $\Longrightarrow$ ) +htmlcommand( ---> )One
| dataset+latexcommand( $\Longrightarrow$ ) +htmlcommand( ---> ) Many services
| )
|
| Basic RePEc concepts are: archive, site and service.
|
| itemize(
| it()
| An dq(archive) is a space on a public access computer system which makes data
| available. It is a place where original data enters the system. The is no need
| to run any software other than an ftp or http daemon that makes the files in
| the archive available upon request. Each archive is identified by a
| three-letter code. Some elementary metadata about the archive like its name,
| its url and some basic contents information are polled by a special central
| archive with the handle
| RePEc:all, where dq(RePEc) is the naming authority and dq(all) is the archive
| code.
| it()A dq(site) is a collection of archives
| on the same computer system. It usually
| consists of a local archive augmented by frequently updated (dq(mirrored))
| copies of remote archives.
| it()A dq(service) is a rendering of RePEc data in a form that is available to
| the end user.
| )
|
|
| All archives hold papers and metadata about papers, as well as software
| that is useful to maintain archives. Everything contained in an archive may
| be mirrored. For example, if the full text of a paper is in the archive, it
| may be mirrored. If the archive does not wish the full text to be mirrored,
| it can store the papers outside the archive. The advantage of this
| dq(remote storage) is that the archive maintainer will get a complete set
| of access logs to the file. The disadvantage is that every request for the
| file will have to be served from the local archive rather than from the
| RePEc site that the user is accessing. Of course an archive may also
| contain data about documents that are exclusively available in print.
|
| There is no need for every site to mirror the complete contents of every
| archive in the system. To conserve disk space and bandwidth some sites only
| mirror bibliographic information rather than the documents that an archive
| may contain. Others mirror all the files of an archive. Others may mirror
| only parts of a few archives. The software that is used to mirror the
| archive is provided at RePEc:all. It first mirrors the central archive.
| This software then reads a configuration file and then writes batch calls
| to the popular dq(url(mirror)(http://sunsite.ic.ac.uk/mirror)) program for
| ftp and the dq(url(w3mir)(http://www.math.uio.no/~janl/w3mir/)) script for
| http archives.
|
| An obvious way to organize the mirroring process would be to mirror the
| data of all archives to a central location. This central location would in
| turn be mirrored to the other RePEc sites. The founders of RePEc did not
| adopt that solution, because it would be quite vulnerable to mistakes at
| the central site. Instead each site installs the mirroring software and
| mirrors dq(on its own), so to speak. Not all of them adopt the same
| frequency of updating. Many update every night, but a minority only updates
| every week. It is therefore not known how long it takes for a new item to
| be propagated through the system.
|
| Each service has its own name. A service that is based on mirrored scripts
| may run on many locations. Within reason, all services are free to use any
| part of the RePEc data as they see fit. For example a service may only
| show papers that are available electronically, others may restrict the
| choice further to act as quality filters. In this way services implement
| constraints on the data, whether they be availability constraints or quality constraints.
| The user service infrastructure is quite well developed, we list the most
| important ones in link(Section ref(sec:user))(sec:user). This distribution
| via the several user services is undisputedly successful feature of
| RePEc. It is therefore not given further attention here.
|
|
|
|
| COMMENT(---
| Por que no aņadir aqui un grafico? Quedaria mucho mas claro. Si quieres
| y tenemos tiempo yo puedo practicar un poco con el latex... Una vez que hemos
| diseņado uno podemos aplicarlo a toda la documentacion ... ---)
|
|
| sect(The structure of an archive)label(sec:indi)
|
| RePEc stands on two pillars. First, an em(attribute):em(value) template
| metadata format called ReDIF. This acronym stands for em(Re)search
| em(D)ocumentation em(I)nformation em(F)ormat but it is best understood as a
| literal. ReDIF defines a number of templates. Each templates describes an
| object in RePEc. It has a set of allowable fields, mandatory, and
| some repeatable. The second pillar is the Guildford protocol. It fixes
| rules how to store ReDIF in an archive. It basically indicates which files may
| contain which templates. It is possible to deploy ReDIF without using the
| Guildford protocol. But in the following we will ignore this conceptual
| distinction, because it is easiest to understand the structure and contents
| of an archive through an example. This is done in link(Subsection
| ref(sec:guil))(sec:guil). Therefore we will list files in the way required
| by the protocol as well as the contents of the file that is in fact written
| in ReDIF. This is done in link(Subsection ref(sec:guil))(sec:guil). We
| return to technical aspects of ReDIF in link(Subsection
| ref(sec:redi))(sec:redi).
|
| subsect(The Guildford Protocol)label(sec:guil)
|
| RePEc identifies each archive by a simple identifier or handle. Here we look at
| the archive RePEc:sur which lives at
| tturl(ftp://www.econ.surrey.ac.uk/pub/RePEc/sur). On the root directory of the
| archive, there are two mandatory files. The file em(surarch.rdf) contains a single
| ReDIF archive template.
| verb(Template-type: ReDIF-Archive 1.0
| Name: University of Surrey Economics Department
| Maintainer-Email: T.Krichel@surrey.ac.uk
| Description: This archive provides research papers from the
| Department of Economics of the University of Surrey,
| in the U.K.
| URL: ftp://www.econ.surrey.ac.uk/pub/RePEc/sur
| Homepage: http://www.econ.surrey.ac.uk
| Handle: RePEc:sur)
| In this file we find basic information about the archive. The other
| mandatory file is em(surseri.rdf). It must contain one
| or more series templates.
| verb(Template-Type: ReDIF-Series 1.0
| Name: Surrey Economics Online Papers
| Publisher-Name: University of Surrey, Department of Economics
| Publisher-Homepage: http://www.econ.surrey.ac.uk
| Maintainer-Name: Thomas Krichel
| Maintainer-Email: T.Krichel@surrey.ac.uk
| Handle: RePEc:sur:surrec)
| These two files are the only mandatory files in the Guildford
| protocol. If these are the only files present in the archive then all the archive
| is doing is to reserve the archive and the series codes. All documents have
| to be in a series. The papers for the series RePEc:sur:surrec are confined
| to a directory called em(surrec). It may contain files of any type. Any file
| ending in dq(.rdf) is considered to contain ReDIF templates. Let us
| consider one of them, em(surrec)/em(surrec9601.rdf)+footnote(We suppress
| the Abstract: field to conserve space.)+verb(Template-Type: ReDIF-Paper 1.0
| Title: Dynamic Aspect of Growth and Fiscal Policy
| Author-Name: Thomas Krichel
| Author-Email: T.Krichel@surrey.ac.uk
| Author-Name: Paul Levine
| Author-Email: P.Levine@surrey.ac.uk
| Author-WorkPlace-Name: University of Surrey
| Classification-JEL: C61; E21; E23; E62; O41
| File-URL: ftp://www.econ.surrey.ac.uk/pub/
| RePEc/sur/surrec/surrec9601.pdf
| File-Format: application/pdf
| Creation-Date: 199603
| Revision-Date: 199711
| Handle: RePEc:sur:surrec:9601)
| COMMENT(
| Note that in this example the full text of the paper is located within the
| archive directory structure itself. Therefore the full text is mirrored
| together with the bibliographic data. Services can then link to a mirrored
| copy of the full text. If the URL of the paper would point to a place outside
| the archive structure, the link to the full text would always point to that
| location.
| )
| Note that we have two authors here. The
| dq(Author-WorkPlace-Name) attribute only applies to the second author.
| We will come discuss this point now.
|
| subsect(The ReDIF metadata)label(sec:redi)
|
| COMMENT(jmbc(---Tipica pregunta que nos pueden hacer: por que ReDIF y no otro formato
| mas aceptado como.... el DC? ---))
|
| The ReDIF metadata is mainly an extension of the
| latexcommand(\citeN{petdeu94publishing}) whenhtml(url(Karlsson and Krichel
| (1999))(http://gretel.econ.surrey.ac.uk/papers/lindi.html)) commonly known
| as the IAFA templates. In particular it borrows the idea of clusters from
| the draft quote( There are certain classes of data elements, such as
| contact information, which occur every time an individual, group or
| organization needs to be described. Such data as names, telephone numbers,
| postal and email addresses etc. fall into this category. To avoid repeating
| these common elements explicitly in every template below, we define
| dq(clusters) which can then be referred to in a shorthand manner in the
| actual template definitions. ) ReDIF takes a slightly different approach
| to clusters. A cluster is a group of fields that jointly describe a
| repeatable attribute of the resource. This is best understood by an
| example. A paper may have several authors. For each author we may have
| several fields that we are interested in, the name, email address, homepage
| etc. If we have several authors then we have several such groups of
| attributes. In addition each author may be affiliated with several
| institutions. Here each institution may be described by several attributes
| for its name, homepage etc. Thus a nested data structure is required. It
| is evident that this requirement is best served in a syntax that
| explicitly allows for
| it such as XML. However in 1997+emdash()when ReDIF was
| designed+emdash()XML was not available. We are still convinced that the
| template syntax is more human readable and easier understood. However the
| computer can not find which attributes correspond to the same cluster
| unless some ordering is introduced. We proceed as follows.
| For each group of arguments that make
| up a cluster we specify one attribute as the dq(key) attribute. Whenever
| the key attribute appears a new cluster is supposed to begin. For example
| if the cluster describes a person then the name is the key. If an
| dq(author-email) appears without an dq(author-name) preceding it
| the parsing software aborts the processing of the template .
|
| Note that the designation of key attributes is not a feature of ReDIF. It
| is a feature of the template syntax of ReDIF. It is only the syntax that
| makes nesting more involved. We do not think that this is an important
| shortcoming. In fact we believe that the nested structure involving the
| persons and organizations should not be included in the
| document templates. What should be done instead is to
| separate the personal information out of the document templates into
| separate person templates
| verb(Template-Type: ReDIF-Person 1.0
| Name: Thomas Krichel
| Email: T.Krichel@surrey.ac.uk
| Author-Paper: RePEc:sur:surrec:9404
| Author-Paper: RePEc:sur:surrec:9601
| Homepage: http://gretel.econ.surrey.ac.uk
| Handle: RePEc:per:1965-06-05:thomas_krichel)
| We can then replace the author information for the first author in the
| paper template for +bendtt(RePEc:sur:surrec:9601) by verb(Author-Name:
| Thomas Krichel Author-Person: RePEc:per:1965-06-05:thomas_krichel) The
| benefits of such a relational structure are clear. There is a much reduced
| load on administration of the system. When one element of author
| data+emdash()+eg()her phone number+emdash()changes, this change has to be
| registered at only one point in the system. A pervasive use of these
| relational features will allow the resolution of current author information
| through the current person template of the author. The user of a RePEc
| service would therefore find the author of the paper even though the
| contact information on the paper's title page may no longer be current. We
| leave the implementation of such systems for future work.
|
|
| sect(The archives)label(sec:soci)
|
| The main issue of this paper is to evaluate if the decentralized collection
| of conventional bibliographic data works on the Internet. Given the
| requirements on the data that we have sketched in the previous section,
| will the staff at the providing institutions be able to supply it? This
| question is addressed in this section.
|
| In order to understand how the archive work in practice,
| we look at the social structure
| supporting the archives.
| We set out our understanding about how archives are maintained internally and
| supported externally. In theory all providers are equal. They all read the
| same documentation; then they all register once with the same central archive
| etc. In practice some are more equal than others. These people are not only
| are involved in the operation of a local archive but they also
| itemize(
| it()act as consultants for the erection of new archives
| it()work on implementation software
| it()develop and maintain RePEc services
| )
| For the purpose of this paper it is therefore useful
| to think about these persons as a small dq(RePEc team) whose members share
| roughly the same knowledge and enthusiasm. It consists of
| itemize(
| it()url(Jos\'e Manuel Barrueco Cruz)(http://www.uv.es/~barrueco),
| Assistant Librarian, url(Universitat de
| Val\`encia)(http://www.uv.es)
| it()Christopher Baum, Associate Professor
| of Economics, Boston College
| it()url(Sune Karlsson)(http://www.hhs.se/personal/sunek),
| Assistant Professor, url(Stockholm School of Economics)(http://www.hhs.se/)
| it()Thomas Krichel, lecturer in Economics, url(University of
| Surrey)(http://www.surrey.ac.uk)
| it()Sergei I. Parinov, Head of the Department for
| Information Technologies in the Economic System at
| url(Institute of Economics and Industrial Engineering of
| the Siberian Branch of the Russian Academy of Science)(http://www.ieie.nsc.ru)
| it()
| Robert P. Parks, Professor of Economics,
| Washington University St.+tilde()Louis
| it()Geoff Shuetrim, Researcher, Reserve Bank of
| Australia
| it()
| url(Christian Zimmermann)(http://www.er.uqam.ca/nobel/r14160/index.html),
| Assistant Professor of Economics, University of Qu\'ebec at Montr\'eal.
| )
|
| The level of involvement of these persons varies. But for the
| purpose of this study these people are assumed to be equal. This
| assumption allows us to bring forward the following definition.
| We say that an
| archive is dq(controlled) if it is managed by a member of the RePEc team
| or managed by a person working under the supervision of a team member.
| The other archives will be called dq(loose) archives. These archives
| are not under the direct control of a member of the RePEc team.
| We will address the controlled and loose archive
| in link(Subsection ref(sec:cont))(sec:cont)
| and link(Subsection ref(sec:loos))(sec:loos) respectively.
|
| subsect(The controlled archives)label(sec:cont)
|
| Within the controlled archives we distinguish five categories.
| enumerate(
|
| it()dq(archives of controlled collections)
| bring together material
| collected from different sources. The data collection effort
| is made by a member of the RePEc team or an agent working directly
| under her control.
|
| it()dq(archives of hosted collections)
| combine material collected from different sources.
| The data collection effort is made by a person outside the RePEc team but
| where the RePEc archive where the data is held in the form of ReDIF is on
| a disk to which a member of the RePEc team has write access.
|
| it()dq(archives of hosted sources)
| are archives for data from a single
| source that is provided by a person outside the RePEc team. The
| RePEc archive where the data is held in the form of ReDIF is on
| a disk to which a member of the RePEc team has write access.
|
| it()dq(archives that host private sources)
| are archives for data from a single
| source that is provided by a person who belongs to the
| RePEc team.
| it()dq(dead archives) are archives that are no longer being maintained
| on the host where they lived originally and that have been moved to
| a site that is controlled by a member of the RePEc team.
| )
| Table 1 lists the archives within these categories.
|
| +latexcommand(\setlength\tabcolsep{0em}\begin{table})
| table(2)(lr)(
| row(celll(em(type))cellr(em(codes of archives)))
| row(
| celll(controlled collections)
| cellr(RePEc:wpa RePEc:wop RePEc:wuk RePEc:hhs RePEc:hhb)
| )
| row(
| celll(hosted collections)
| cellr(RePEc:fth RePEc:fip)
| )
| row(
| celll(hosted source)
| cellr(RePEc:bbk RePEc:cpr RePEc:nbr RePEc:red RePEc:ecm RePEc:els)
| )
| row(
| celll(controlled sources)
| cellr(RePEc:val RePEc:sur RePEc:apr RePEc:boc RePEc:nos)
| )
| row(
| celll( )
| cellr(RePEc:ecm RePEc:cre)
| )
| row(
| celll(dead archives)
| cellr(RePEc:bru RePEc:tex RePEc:tcd)))
| +latexcommand(\caption{The controlled archives}
| \label{tab:a}\end{table}
| \setlength\tabcolsep{.2em})
|
| COMMENT(
| +latexcommand(\caption{The data in article and paper templates}
| \end{table})
| )
|
| subsubsect(Controlled collections)
|
| The RePEc:wop archive contains the data from the WoPEc project. This project
| was opened by Thomas Krichel in April 1993. At that time he placed
| the first electronic working paper in the discipline. During the following
| two years
| the emphasis of the archive shifted towards the description of remote
| documents, ie()those which
| are not available on the local server. In 1998, as a
| result of a major collection and awareness raising effort undertaken by the
| WoPEc project in the United Kingdom the part of the RePEc:wop data that related
| to series in this country was taken out to form the RePEc:wuk archive. The
| maintenance of the series from outside the United Kingdom was contracted out to
| a team at the Siberian Branch of the Russian Academy of Sciences working under
| the leadership of Sergei Parinov.
|
| RePEc:wpa is the data from the Economics working paper archive at WUStL
| (EconWPA) as operated by Bob Parks. url(EconWPA)(http://econwpa.wustl.edu)
| opened in September 1993. It is a collection of electronic papers. It operates
| through author submissions in a much similar way as the
| url(xxx)(http://xxx.lanl.gov) operates for Physics. Authors upload their papers
| with the archive and supply the bibliographic information themselves. In 1997 a
| converter was written by the Siberian team that converts these internal data to
| ReDIF.
|
| RePEc:hhs and RePEc:hhb archives maintained by the url(S-WoPEc)
| (http://swopec.hhs.se/) and url(S-WoBa)(http://swoba.hhs.se/)
| projects. These are Swedish national collections that gather data from many
| institutes. Section 4 of
| latexcommand(\citeN{sunkar99repec})whenhtml(url(Karlsson and Krichel
| (1999))(http://gretel.econ.surrey.ac.uk/papers/lindi.html)) contains a
| comprehensive description of the way that these projects operate.
|
| subsubsect(Hosted collections)
|
| RePEc:fth is by far the largest archive. It has over 28,000 papers but none
| of them are downloadable. It is a database produced by Fethy Mili, the
| Economics Departmental Librarian at Universit\'e de Montr\'eal. He collects
| data on printed working papers that he receives. His collection is one of
| the largest on this planet. He receives about 300 series. In order to
| update the holdings in the archive he uploads an ASCII dump of its recent
| additions to the database. He then activates three scripts. These convert
| his data to ReDIF, add the new data to existing stock, remove
| duplications+footnote(that involves some manual work) and clean the file
| space. These scripts have been written by Thomas Krichel. He has direct
| access to Fethy Mili's files. They also collaborate to ensure that there are not
| many duplications between the data in RePEc:fth and the data provided in
| other archives. This effort requires the collaboration of the other
| archives as well. Clearly, data supplied directly by the provider of the
| papers is preferable to data supplied by an intermediary.
| However the data of the providers does not stretch as far back as
| Fethy's data. Ideally there should be a transfer of the data from the
| RePEc:fth archive to the archive of the original provider. The provider
| should then consolidate their data with the data from RePEc. There are
| cases where such a consolidation has been successful. However there are
| some cases where this consolidation is still forthcoming. In those cases
| there are double holdings of data.
|
| RePEc:fip contains the contents of the Federal Reserve of the United States'
| dq(Fed in Print) database. This database is a centrally collected database for
| all the documents that the Fed publishes. Every regional branch contributes
| data to the collections. These contribution sends a text dump via email to
| Thomas Krichel who then runs a converter that will then write the
| data into the ReDIF format. A similar process has been working since 1994,
| when the US Fed became the first governmental organization to contribute
| to the collection.
|
| subsubsect(Controlled sources)
|
| These are archives that make material available from a single
| provider. RePEc:nbr and RePEc:els are based on the machine of the
| provider. For others the providers use a variety of means to bring the
| data to a machine of the RePEc team member. RePEc:cpr use the most
| primitive way by physically delivering disks to Thomas Krichel.
|
| subsubsect(Dead archives)
|
| RePEc:bru, RePEc:tex and RePEc:tcd are dead. These are archives that are no
| longer being maintained and are kept at a site under the control of a
| member of a RePEc team. It is not clear at what stage the archive is no
| longer being maintained. The best indication comes when an archive
| maintainer informs a member of the RePEc team that she is leaving the
| workplace where she built the archive. Another indication is that the
| archive can no longer be found at the url indicated in the archive
| template.+footnote(Note that it is possible to move an archive without
| notifying the keeper of the RePEc:all archive. To do that the old and new
| archives need to be held open simultaneously and the archive url must be
| set to the new archive on both locations until the RePEc:all archive has
| passed and taken a copy of the archive file with the new location.) Finally
| another indicator is when the archive has not been updated for a long
| time. There is currently no policy towards dead archives. It is likely that
| the number of dead archives will increase initially because the number of
| archives is increasing. Later the problem is likely to decline if the
| participation in RePEc becomes a common practice.
|
|
| COMMENT(jmbc(--- Otro indicador seria cuando ha dejado de actualizarse
| desde hace mucho tiempo. Por ejemplo Valencia...))
|
|
| subsect(Provider support)label(sec:suppo)
|
| COMMENT(
| Software written by url(Ivan Kurmanov)(http://gretel.econ.surrey.ac.uk/~ivan)
| allows to read the data files ReDIF templates into a hashed array in
| perl. This software also allows to check if the templates have a valid
| syntax. The reading software will discard any template that contains a
| mistake. It mill also ignore any individual data element that contains a
| faulty syntax. This may appear a rather Draconian approach.
| )
|
| The decentralized way of operating implies that any archive operator could
| write anything they like in the template. Racist, pornographic, arty-farty
| etc. expressions should be rare within the collection because each archive
| has to register with the keeper of the RePEc:all archive before the
| material from the archive can enter the RePEc distribution channels. Any
| check on the semantics of the contents has to be performed by the archive
| maintainer herself. They should be quite competent at performing this task
| since it they posses the local knowledge that is required. However to
| encode that information into the templates some dq(remote) or dq(global)
| knowledge is required. We aim at providing knowledge in the
| documentation. We also aim to give the archive maintainers feedback on
| their data. This is what we deal with in this section. In particular we aim
| to provide the contributors with reports on the validity of their data.
|
| When we undertook this study we sent an email to all providers
| of loose archives. This email contained details about the checks. The
| checks were not publicized before in this way. They were included in the
| guide for archive maintainers that Christian Zimmermann maintains at
| tturl(http://ideas.uqam.ca/ideas/maintain.html). But it can be confidently
| assumed that when the data were collected the error files had not been
| used.
|
| Let em(arc) be the three-letter code of an arbitrary archive. Then at
| bendtt(ftp://netec.mcc.ac.uk/pub/RePEc/help/)+em(arc)+whenlatex(
| )+bendtt(.rech) we store the result of a syntax check. It would be too long
| and too tedious to list the contents here. However we invite the reader to
| url(inspect those files)(ftp://netec.mcc.ac.uk/pub/RePEc/help/.). Note that
| these files are updated within a few hours of a change in the archive
| therefore the time stamp on the file will give a good indication for the
| time when the archive was last modified.
|
| The syntactic control is not the only one that we need to do. Since the
| templates are in fact within a relational framework we need to make sure
| that the relationships are valid. Even without the fully relational
| features that the dataset is aimed to eventually cover there are some
| relational features that need checking. For example, a paper handle
| bendtt(RePEc:arc:xyzxyx:1999-1) would make no sense if there is no series
| bendtt(RePEc:arc:xyzxyx) defined in the dataset. If this is not the case it
| is likely that a user service on the web for example would have at least
| one broken link that would point from the paper to its series or
| vice-versa. Note that the relational control is computationally much more
| involved than the syntactical check. The syntax check only needs to look at
| an individual template. The relational check needs to be aware of the
| complete dataset. This has some important implications for the idea of a
| decentralized and relational database. The full extent of these
| implications has yet to be revealed. For the moment moment we provide a
| relational check at
| bendtt(ftp://netec.mcc.ac.uk/pub/RePEc/help/)+em(arc)+bendtt(.rela).
|
| The last check is to control the url in the dataset. This is useful to find
| broken links to the full text of documents.
|
| A dataset as large as RePEc will never be completely error-free. There are
| many mistakes which are not machine-understandable and which therefore need
| human control. To deal with machine-understandable errors before they ever
| reach the user would be a desirable aim to reach. At the moment only the
| syntax check is performed at the time when the ReDIF data is read. Ideally
| one would like to see a check of the relational features as well as the
| control of the URLs be performed when the data is read. The only way that
| this could be done is to compute centrally a list of blacklisted templates.
| This is an area for future work.
|
| Finally there is an email discussion list for RePEc. It is called
| url(repec-admin)(http://www.mailbase.ac.uk/lists/repec-admin). This is
| essentially meant for the common concerns of archive providers. There is
| not a lot of traffic on the list, and questions concerning the maintenance
| of the archive. Most discussion concern general policy issues such as
| copyright and data on usage. We estimate that only about one in three
| archives have a representative on the list.
|
|
| subsect(The loose archives)label(sec:loos)
|
| In order to gather some data about the loose archives we sent an email to
| all 66 loose archives. It was sent to the addresses that are listed in the
| Maintainer-Email field of the archive template. The mail informed about the
| maintainer support that we detail in the link(Subsection
| ref(sec:suppo))(sec:suppo)+footnote(The text of the mail and the responses
| is available from the authors on request.) After sending a reminder, we
| achieved 22 responses. The small number of replies that we received is
| cause for concern. For anonymous questionnaires a response rate of one in
| three would be a great success. However we are dealing with a situation
| where the maintainer have some knowledge about what we are doing. There
| must be a common concern between us and the maintainer. Recall that almost
| all of them took the initiative to open the archive in the first place.
|
| The first question concerned the personal address of the
| respondent. In the second question we were interested in the professional
| status of the respondent quote( How would you describe your function?
| (dq(academic faculty), dq(researcher), dq(computing officer),
| dq(publications officer), dq(secretary), dq(student) etc). )
|
| Eleven respondents are academic staff, either in teaching or in
| full-time research positions, three professional researchers outside
| academia+emdash()we will group these as faculty respondents in the
| following+emdash()three students, two computer systems administrators, one
| librarian, one secretary, and one publications officer. The academic
| faculty were the first to respond, most of the answers we received from the
| others came after the reminder email.
|
| COMMENT(jmbc(---Quizas habria que notar la falta de bibliotecarios y enfatizar otra vez
| que la labor de catalogacion esta ahora en manos de los autores o
| distribuidores no de los bibliotecarios? ---))
|
| The next question concerned
| quote(
| Briefly describe how your RePEc archive was initiated.
| For example: who had the idea, why did you open the archive...
| )
| Here all the faculty respondents write that they opened the archives
| themselves. Eight of them mention that they have been approached by a
| member of the RePEc team. Six of them mention general awareness of RePEc.
| One student maintainer says that he was approached by the webmaster. All
| other non-faculty respondents report that they have been approached by
| faculty members.
|
| We already come up with one interpretation. It seems
| that the work on the archive works best when the academics are
| taking the initiative.
|
| quote(
| Briefly describe how the archive is maintained.
| For example: who is involved in maintaining it, do you update the
| files regularly, how do you collect the data...
| )
|
| The answers to this question are very difficult to summarize. Suffice is to
| say that we did not find two institutions that have the same
| procedures. Some involve as many as three persons in the process. Some use
| in-house scripts to update the server or to input the data. Even if
| academics are doing it on their own every single one of them seems to find
| a different way to do it. We conclude that trying to write a
| software that would help to automate the process would be very difficult
| because the software would have to cope with a large variety of individual
| organizational structures.
|
| quote(Are the researchers aware that their work is disseminated though
| +latexcommand(\url{)IDEAS/NEP/WoPEc+latexcommand(}) etc?)
|
| Here we have 16 answers that broadly say dq(yes) versus 6 that broadly say
| dq(no). A word of caution is on order here. An archive maintainer can
| easily state that the researchers are aware of it if she told them once
| that the research was disseminated. As one maintainer put it: dq(I keep
| reminding them but my guess is, less than 30% remember).
|
| quote( Do you find it difficult/cumbersome to make the updates?
| What could we do to help you?)
|
| All respondents write that it was easy or fairly easy to perform the
| updates. Many add that they did not need any further help. Suggestions are
| few and far between. None of them suggest procedural changes with the
| provision of the data. While this is a favorable result we must not forget
| that only one in three maintainers replied. It is possible that the other
| maintainers are rather confused and therefore did not bother to reply.
| We have some anecdotal evidence to support this idea.
|
| COMMENT(jmbc(--- Yo quitaria esta anecdota. Aunque es muy significativa, para entenderla
| se necesitan unos conocimientos de RePEc que el lector seguramente aun no
| tiene. Si el lector no encuantra ninguna misconception, puede que no
| siga leyendo el articulo :-\)
|
| Here is a recent
| email that we received. We blank out the name of the
| series
| quote(
| The [...] Papers are put on your site. We used to be
| able to give you the files as .rdf, but unfortunately we no longer have
| the facility to do this, so we are now saving the files as .txt MSdos
| for Windows. Could you please let me know if this is going to cause a
| problem, and if so, could you recommend another way that we can save the
| file.
| )
| We leave it the the reader to find the number of misconceptions that
| there are in this message.
|
| )
|
|
| sect(The total dataset)label(sec:data)
|
|
| +latexcommand(\begin{table}\begin{center}) table(5)(lrlrl)(
| row(cell()cells(2)(ReDIF-paper) cells(2)(ReDIF-article) )
| row(cell(em(field)) cell(em(all))cell(em(max)) cell(em(all)) cell(em(max)) )
| row(cell(template-type)cell(58254)celll(1) cell(10112) celll(1) )
| row(cell(handle) cell(58251) celll(2)cell(10110) celll(1) )
| row(cell(title) cell(58235) celll(2) cell(10110)celll(1) )
| row(cell(author-name) cell(98321) celll(14) cell(13855) celll(6) )
| row(cell(creation-date) cell(52730) celll(1) cell(8819)celll(1) )
| row(cell(revision-date) cell(536) celll(8) cell() celll() )
| row(cell(publication-date) cell()celll() cell(510) celll(1) )
| row(cell(abstract) cell(22984) celll(3) cell(1896) celll(1) )
| row(cell(classification-jel) cell(20194) celll(2) cell(436) celll(1) )
| row(cell(keywords) cell(39219)celll(3) cell(9084) celll(1) )
| row(cell(keywords-attent) cell(457) celll(1) cell() celll() )
| row(cell(publication-status) cell(6227) celll(3) cell(1568) celll(1) )
| row(cell(note)cell(9011) celll(1) cell(1479) celll(2) )
| row(cell(series) cell(4124) celll(2) cell()celll() )
| row(cell(number) cell(16021) celll(2) cell(1501) celll(1) )
| row(cell(price) cell(4175) celll(3) cell() celll() )
| row(cell(file-url) cell(17259) celll(22) cell(1853) celll(2) )
| row(cell(order-url) cell(2417) celll(1) cell() celll() )
| row(cell(contact-email) cell(1141) celll(1) cell() celll() )
| row(cell(availability) cell(7169) celll(2) cell() celll() )
| row(cell(length)cell(33342) celll(12) cell() celll() )
| row(cell(pages) cell() celll() cell(7920) celll(1) )
| row(cell(month) cell() celll() cell(489)celll(1) )
| row(cell(issue) cell() celll() cell(8705) celll(1) )
| row(cell(volume) cell() celll() cell(1293) celll(1))
| row(cell(year) cell() celll()cell(1293) celll(1) )
| row(cell(journal) cell() celll() cell(488) celll(1) )
| row(cell(paper-handle)cell() celll() cell(19) celll(1) )
| )
| +latexcommand(\caption{The data in article and paper templates}
| \label{tab:b}\end{center}\end{table})
|
| subsect(Aggregate Contents)
|
|
|
| In Table 2, we examine the document data in RePEc. For each field we give
| the total occurrences of the field in the dq(all) column and the maximum of
| occurrences that the field has within a single template in the dq(max)
| column. The document data appear in the ReDIF-paper and the ReDIF-article
| templates. There are two characteristics that potentially set articles
| apart from papers. First the paper can be understood as a preprint. From
| that point of view the article is a paper that has gone through some sort
| of peer review. In that case the distinction between paper and article has
| to do with the contents only. Secondly the distinction between paper and
| articles could be through their physical manifestation. From that point of
| view the article would be a document that is bound with others in a journal
| issue and it would therefore carry page numbers, issue numbers etc. This is
| the official criterion according to the ReDIF documentation. But it is not
| neat since the pagination may become redundant if the journal becomes
| electronic. In the following we will use the term dq(document) when we wish
| to refer to papers and articles simultaneously.
|
| Total numbers for documents are given by the dq(template-type) and
| dq(handle) fields. Since each template should have exactly one type and
| exactly one handle the tiny difference between the two numbers is made up
| of mistakes in the dataset. The title field is also required. It is
| encouraging to see that most documents have a creation date attached to
| them,
| because as the dataset grows it will become increasingly important to
| distinguish between recent and dated documents; only the former are likely
| to be of much interest. By contrast dq(revision-date) information is rare.
| Articles may also have a dq(publication-date). The difference of this field
| with the dq(creation-date) field is not clear. We consider this to be a
| design error in the template structure.
|
| COMMENT(--- Yo lo quitaria. publication-date no esta en la documentacion
| de ReDIF. Puede ser un error en redif.spec??)
|
| Let us consider the elements that refine the contents description. We
| encourage contributors to provide abstracts. The presence of abstracts for
| about one in three papers is very positive. The abstract field can be
| repeated. This is desirable when there are abstracts in different
| languages. A large number of the papers have a url(Journal of Economic
| Literature)(http://www.jel.org) (JEL) classification code attached to
| them. However almost all papers in the offline papers only archive
| RePEc:fth have the codes and that explains a very large
| proportion of the
| classified material. Note that this data has been compiled by a librarian.
| For the electronic papers there are only two in five papers that have a
| classification field. We agree that this is a serious limitation to the
| quality of the data. It would have been possible to require a
| classification number for each paper right from the start. This would have
| hampered the collection effort. In particular it would have made it
| impossible for the WoPEc team to dq(snarf) bibliographic data from sites
| where this JEL data was not available. There is also some concern among
| economists that their areas of work do not match with these codes. The use
| of more complete and sophisticated classification schemes would not be
| possible. The main argument against requiring JEL classification codes was,
| however, that there is considerable opposition against the scheme in the
| heterodox Econonomics commonity. They feel that the JEL classification
| scheme reflects the view of the orthodoxy. Requiring JEL classification
| codes would have meant excluding these contributors. Then and now only a tiny part of
| the collection could be grouped as heterodox. However our aim is that RePEc
| be a broad church. This was the decisive argument against requiring the use
| of JEL codes.
|
| There is a large number of templates that have keywords. About 50% of these
| templates come from RePEc:fip where each paper has a keyword. ReDIF allows
| for both free and qualified controlled vocabulary. This facility is
| used by for the internal keyword scheme of the url(Attent: Research
| Memoranda)(http://cwis.kub.nl/~dbi/english/info/attent.htm) database. They
| are only used by the RePEc:dgr archive.
|
| COMMENT(--- Yo lo quitaria. publication-date no esta en la documentacion
| de ReDIF. Puede ser un error en redif.spec??)
|
|
| The dq(publication-status) field can be used to indicate where the paper
| has been submitted to and where the paper has been formally published.
| This field appears in the data from large research bodies that have been
| issuing a series of papers for many years and that have data about the
| formal publication of the paper. The fields dq(series) and dq(number) are
| somewhat redundant since this information should also be available from the
| handle. The dq(price) field normally refers to the delivery of a printed
| copy. The mode of delivery is often just expressed in the dq(price) field.
| The dq(file-url) field refers to the dq(full text) locus of a part of the
| full text. Usually it is the complete full text.
|
| The document may have several
| components in addition to the full text. These can be listed as several
| dq(file) clusters. Each may carry an uncontrolled field about its function
| within the paper. For example the author may wish to supply a computer
| program that was used to produce the paper. In that case a whole series of
| files may be made available. However that is not the way the option of
| having many files is actually exercised. Most of the time it is used to
| include elements like graphics or tables that the author did not manage to
| include into the main document file.
|
| The dq(order-url) field is used to point to an intermediate page that sits
| between our description and the files of the document. In that case we are
| not aware if the resource does actually exist online. dq(order-url) may be
| used in conjunction with the dq(file-url) attribute. Note that there is no
| dq(order-email) field in the document templates. Such a field figures in
| the series template, because the ordering of a paper should be the same for
| all papers in the series. The dq(contact-email) may otherwise be used to
| contact the somebody who has any connection with the paper. This field is
| only used by the contributors to the RePEc:wpa archive. The
| dq(availability) is used most of the time to signal that the paper is no
| longer in print.
|
| Finally a
| dq(length) attribute can be used to indicate how many pages the reader has
| to go through to read the paper. This field is present in all templates
| provided by RePEc:fth and it seems to appear in a surprisingly large number
| of other templates.
|
| Articles have a number of specific attributes that are listed at the bottom
| of the table. Strictly speaking these are not descriptive elements of the
| articles themselves, they rather relate to the position the article has
| within the journal. Finally the dq(paper-handle) allows to point from the
| preprint version to the article template.
|
| +latexcommand(\begin{table}\begin{center}) table(9)(lrllrllrl)(
| row(cells(3)(file)cells(3)(person)cells(3)(organization))
| row(celll(em(name))cellr(em(all))celll(em(max))
| celll(em(name))cellr(em(all))celll(em(max))celll(em(name))
| cellr(em(all))celll(em(max))
| )
| row(celll(url)cellr(19112)celll(1)
| celll(name)cellr(112176)celll(1)
| celll(name)cellr(8598)celll(1)
| )
| row(celll(format)cellr(19024)celll(1)
| celll(postal)cellr(8)celll(1)
| celll(postal)cellr(2118)celll(2)
| )
| row(celll(size)cellr(2630)celll(1)
| celll(homepage)cellr(1557)celll(2)
| celll(homepage)cellr(596)celll(2)
| )
| row(celll(function)cellr(1661)celll(1)
| celll(email)cellr(3166)celll(2)
| celll(email)cellr(1451)celll(3)
| )
| row(celll(restriction)cellr(2548)celll(1)
| celll(phone)cellr(282)celll(1)
| celll(phone)cellr(164)celll(1)
| )
| row(celll()cellr()celll()
| celll(fax)cellr(259)celll(1)
| celll(fax)cellr(197)celll(1)
| )
| row(celll()cellr()celll()
| celll(workplace-name)cellr(8598)celll(4)
| celll()cellr()celll()
| ))+latexcommand(\caption{The data in clusters}
| \label{tab:g}\end{center}\end{table})
|
|
|
| subsect(The clustered data)
|
| The data available in Table 2 is not the complete set of information
| available in the dataset. It only lists the individual attributes and the
| key attributes of clusters in the paper and article templates. In Table 3 we
| have the data that is contained in the clusters in this subset of the RePEc
| data. This data is therefore consistent with the data in Table 2.
|
| There are three types of clusters, dq(file), dq(organization) and
| dq(person). The numbers that are present suggest that there are significant
| possibilities for a relational structure in the dataset between persons and
| their organizations. An interesting consideration in the person cluster is
| the high number of workplace templates. Providers of the data seem to
| attribute more importance to the workplace of a person rather than to her
| strictly personal data, eg()her homepage. The only explanation that we can
| offer here is that most likely the data is provided by an agent of the
| workplace. The low number of homepages is an indicator which also suggests
| that in most cases the provider is not the author herself. Note also that
| the workplace information+emdash()when it is present+emdash()is much more
| complete than the corresponding data for the individuals.
|
| subsect(Mistakes in the data)
|
|
| When a dataset is provided by various parties at the same time it is not a
| good idea to use the data directly. Recall that mirroring software is being
| used to keep updated copies of archives on sites that unite more than one
| archive. An archive could provide a site with an arbitrary stream of
| nonsense data. To avoid that data to appear in a user service we need to
| check the data at the time of reading. There are two types of problems
| that the software notices when it reads ReDIF templates dq(errors) and
| dq(warnings). An dq(error) result in the template being discarded. A
| dq(warning) results in the value of the
| field being ignored. We deal with both
| problems later on. Note that the distinction between errors and
| warnings is not part of the published ReDIF documentation. It is specified
| in the the specification file of the ReDIF checking software. These
| technical aspects of the control of the dataset are not well documented to
| date. They are all written down in a rather cryptic file that is read by
| the reading and checking software when it is fired up.
|
| subsubsect(ReDIF Errors)
|
| In Table 4 we show the errors that are in the data are in the dataset.
| At the start of the template, the first element has to be the template
| type. In theory the border of the template is the zero-width space between
| the template-type statement and what precedes it. In practice the checking
| software takes any number of blank lines as separator between templates and
| therefore it is able to signal the error that the template is not valid
| because it has as invalid start.
|
| Another type of error is the omission of a required field. The handle
| field is of course a mandatory field. For papers and articles we also
| require the name of at least one author, and the title. The requirement
| that leads to most errors is the specification of the file format. A
| document+emdash()whether a paper or an article+emdash()will be represented in
| a number of files. For each of those files we require a statement about
| the file format (say PDF, postscript etc) as well as some indication about
| the compression or archiving software that is being used.
|
| This requirement was inspired from our experience with user services.
| The early user services of RePEc were confronted
| with the problem to teach users what to do with the files when they had
| downloaded them. If the format of the file was documented it became
| possible to link each file to a documentation page that would explain users
| how to deal with the file. When such links were introduced at the WoPEc
| project in 1996 the number of queries fell dramatically.
| The need to require fire formats was therefore introduced into the
| ReDIF specification.
|
| The next errors listed in Table 3 concern fields that repeated but that
| ReDIF does not allow to repeat. No template may have two handles and no
| document may have two titles.
|
| +latexcommand(\begin{table}\begin{center})
| table(2)(lr)(
| row(cell(em(description of error))
| cellr(em(number)))
| row(cell(Start template with 'template-type' attribute)
| cellr(122))
| row(cell(Required attribute is absent)cellr(6))
| row(cell(Required attribute is absent)cellr(23))
| row(cell(Required attribute is absent)
| cellr(8))
| row(cell(Required attribute is absent in )
| cellr(264))
| row(cell(You cannot repeat (2) this attr in templ above)
| cellr(1))
| row(cell(You cannot repeat (2) this attr in templ above)
| cellr(1))
| row(cell(Attribute misplaced; valid in cluster )cellr(104))
| row(cell(Attribute misplaced; valid in cluster )
| cellr(32))
| row(cell(Attribute misplaced; valid in cluster )
| cellr(2))
| row(cell(Attribute misplaced; valid in template )
| cellr(14))
| row(cell(Attribute misplaced; valid in template ) cellr(4))
| row(cell(INVALID (unknown) attribute)cellr(126))
| row(cell(Invalid value of type (attr: contact-email, eval))cellr(1))
| row(cell(Invalid value of type (attr: file-format, regex)) cellr(112))
| row(cell(Invalid value of type (attr: handle, regex)) cellr(10))
| row(cell(Invalid value of type (attr: author-homepage, eval)) cellr(82))
| row(cell(Invalid value of type (attr: file-url, eval))cellr(77))
| row(cell(Bad line:)cellr(1189))
| )
| latexcommand(\caption{The errors in the dataset}\label{tab:r}
| \end{center}\end{table})
|
| An important source of mistakes is the clustering of attributes. A cluster
| must be introduced with the key attribute for the cluster; if that is not
| the case then the template is in error. However given the fact that the
| cluster concept is more involved than than the meaning of individual
| data element we are surprised that there are not more clustering mistakes.
|
| Each attribute may be checked for its syntax to correspond to a regular
| expression. Email addresses have to be of the standard Internet form
| em(user)@em(site). URLs have to be of a syntax that is specified in
| url(RFC1783)(http://src.doc.ic.ac.uk/rfc/rfc1738.txt). The format
| indicator that is required in the file-format is an in-house product. It is
| based on the mime types as defined in
| url(RFC1521)(http://src.doc.ic.ac.uk/rfc/rfc1521.ps.gz) but it has
| additional qualifiers that specify archiving and compression of files. It
| is therefore not astonishing that this specification produces quite a few
| mistakes.
|
| Finally an important source of mistakes are bad lines. This error typically
| occurs in lines that continue the value of a field that has started on a
| previous line. Any such line must be indented by at least one blank
| character. Note that the number quoted here is the actual number of bad
| lines. If an abstract that goes over several lines has no indentation, this
| problem affects all the lines. The number of templates that are affected
| by the problem is therefore much smaller than the number reported
| here. Our calculations show that 170 templates are invalid through
| bad lines. Note that the same remark also applies for the
| dq(missing template-type) error.
|
| subsubsect(ReDIF warnings)
|
| When a warning is issued, the template is not rejected but the value of the
| field is ignored. We list the warning messages in Table 4.
| Dates have to be of the form em(yyyy-mm-dd). The JEL
| classification values are all known to the checking software. If a key
| attribute is empty then the rest of the cluster data is ignored.
|
| subsubsect(Guildford protocol mistakes)
|
| When preparing this paper we also found some violations of the Guildford
| protocol. Recall that the Guildford protocol sets rules on how ReDIF
| metadata should be stored on a RePEc archive.+footnote(When ReDIF is
| checked these errors are not detected because they are not violations of
| ReDIF.) Three files contained series templates but they are not called
| em(???seri.rdf) and placed in the directory of individual series. There is
| also a file that contains a mixture of ReDIF-paper and ReDIF-software
| templates. This is not licit because no file may contain templates of
| different types.
|
| Since we have been working very thoroughly through the
| data we are confident that there are no further Guildford protocol mistakes
| in the data. To prove that we would need to write special software.
|
| subsect(The composition of the dataset into archives)
|
| In Tables 5 and 6 (in the Appendix) we report the contents of the total
| document-related datasets for loose and controlled archives respectively.
| For each archive, we give its name first; two names have been shortened in
| order to save space. It is clear that the name of the archive is not really
| a well defined concept. For most loose archives the choice of the name
| reflects the name of the provider or sometimes simply the name of the type
| of papers.
|
| It is clear that the largest archives tend to be found among the controlled
| archives. The reasons are simple enough. Many of the controlled archives
| come from large providers. A member of the RePEc team has been working to
| make their contents available, because the bargaining power of large
| providers is such that they have little incentive to provide data but RePEc
| has strong incentives to include them. The majority of loose archives are
| run by small institutions, in general for their departmental paper series.
| At the opposite end there are some personal archives. We will look at them
| separately.
|
|
| +latexcommand(\begin{table}\begin{center})
| table(2)(lr)(
| row(cell(em(description of error))cellr(em(number)))
| row(celll( A bad date value format:) cellr(273))
| row(celll(An invalid JEL value) cellr(3344))
| row(celll(Empty value of a key attr. ) cellr(301))
| row(celll(Empty value of a key attr. ) cellr(1411))
| row(celll(Empty value of a key attr. ) cellr(176))
| )
| +latexcommand(\caption{The warnings in the dataset}\label{tab:n}
| \end{center}\end{table})
|
|
| subsubsect(Controlled versus loose archives)label(sec:coar)
|
| There are two basic reasons why mistakes occur in an archive. Either the
| maintainer is incompetent or (s)he is lazy. In the case of the controlled
| archives we exclude the incompetence cause. We assume that these people are
| competent but that they have not yet corrected the mistakes because they
| have been too lazy, too busy with other things or for whatever other
| reasons. The main issue is whether people who have neither formal
| cataloging background in general nor have had
| personal training in particular are
| able to catalog the documents. If they can do that as well as people who
| have perfect knowledge of the cataloging procedure than it is possible to
| build a catalog simply by pointing a willing individual to the
| documentation.
|
| It is therefore important to consider the comparative number of mistakes in
| these two groups of archives. Because of the fact that the controlled
| archives are so much larger a comparison of the quality of the controlled
| versus the loose archive would be misleading if it would solely based on
| statistical measures like the total number of errors divided by the total
| number or documents. Since the large collections are generated out of ASCII
| dumps from bibliographic databases, this comparison would be misleading.
|
| From an examination of the data in Table 5, there seems to be an
| accumulation of mistakes in certain archives whereas others are almost
| completely error-free. Even some of the controlled archives are affected by
| a series of problems. It therefore seems fair to write that in principle
| the decentralized cataloging works for a large number of archives. However
| a small number are affected by clusters of mistakes. There is some human
| intervention required to fix these mistakes. Note that because web
| cataloging is still in its infancy, we can be hopeful that sooner or later
| the archives that are affected by serial errors will take corrective
| action.
|
| subsubsect(Personal archives)
| Four archives are in fact personal archives where paper of only one person
| and his co-authors appear. Three of them take their name
| from the person who
| is the main author. RePEc is ill-prepared for the wide-spread use idea of a
| personal RePEc archive. Since all archives have to be registered with a
| central archive, if many of authors open such archives this would put the
| central archive under considerable strain. The three archives are operated
| by leading gurus and therefore the RePEc team did find it difficult to
| refuse them to open an archive. If authors would make more material
| available in homepages, one would need to found intermediate collectors
| that would gather the ReDIF data not through the Guildford protocol, but
| through a protocol that is more suitable for the storage of ReDIF data
| in homepages.
|
| One important motivation to store papers in personal archives is
| that many journals+emdash()such as the url(Journal of Internet Cataloging)
| (http://www.haworthpressinc.com/jic/)+emdash()allow authors to
| redistribute their work as part of a collection that is their own. The
| statement for the Journal of Internet Cataloging
| is at tturl(http://www.haworthpressinc.com/jic/jicpubag.html),
| the relevant passage is
| quote(
| As a professional courtesy, the authors retain the right to reprint their
| article submitted again, after publication in the journal, in any work for
| which they are sole Author, or in any edited work for which the author is
| Senior Editor. No further permission is necessary in writing from The
| Haworth Press, Inc., nor will the Press require fees of any kind for the
| reprinting.)
| Providers of personal archives provide reprints of their paper and
| hope that these reprints are protected by such clauses. In a similar way
| we provide an furl(online version of this
| paper)(http://openlib.org/home/krichel/papers/jagt.html).
|
|
| sect(User services)+label(sec:user)
|
| There would be little point in collecting all that data if there were no
| users to use them. Note that there is no official user service for RePEc.
| The implicit ability and explicit intention to allow for many user services
| at one time is a key features of RePEc. This provides an important selling
| point once a potential provider understands that submitting data to RePEc
| means submitting the data to all the user services at once. Here we list
| the most important user services in
| link(Subsection ref(sec:main))(sec:main), before we critically
| discuss them in link(Subsection
| ref(sec:upta))(sec:upta).
|
|
| subsect(The main user services)label(sec:main)
|
| By order of historical appearance, they are
|
| furl(BibEc)(http://netec.mcc.ac.uk/BibEc.html)+amp() +latexcommand(\par
| )+furl(WoPEc)(http://netec.mcc.ac.uk/WoPEc.html)+nl() +noindent() provide
| static html pages for all working papers that are only available in print
| (BibEc) and all papers that are available electronically (WoPEc). Both
| datasets use the same search engines. There are three search engines, a
| full text WAIS engine, a fielded search engine based on the mySQL
| relational database and a ROADS fielded search engine. Note that the mySQL
| database is also used for the control of the relational components in the
| RePEc dataset. BibEc and WoPEc are mirrored in the United States and Japan
| as part of the NetEc project.
|
| furl(IDEAS)(http://ideas.uqam.ca)+nl()
| +noindent() provides an Excite index of static html pages that represent all
| Paper, Article and Software templates. This is by far the most popular RePEc
| user interface.
|
| furl(NEP: New Economics Papers)(http://netec.wustl.edu/NEP)+nl()
| +noindent() is set of reports on new additions of papers to RePEc.
| Each report is edited by subject specialists who receive information on all
| new additions and then filter out the papers that are relevant to the
| subject of the report. These subject specialists are PhD students and young
| researchers. They work as volunteers. On 27 June 1999 there were 1766
| different email addresses that subscribed to at least one list.
|
| furl(Tilburg University Working papers and research memoranda)(http://www.kub.nl/~dbi/demomate/repref.htm)+nl()
| This site also operates a Z39.50 server for all downloadable papers in
| RePEc is available at dbiref.kub.nl:9997. The database name is
| dq(repref). The attribute set is Bib-1, and the record syntax supported are
| USmarc, SUTRS, GRS-1 (only string tags, tag type 3).
|
| furl(RuPEc)(http://www.ieie.nsc.ru/RuPEc)+nl()
| is a server in Russian. It does not only provide search facilities
| for Russian users but also archival facilities for Russian contributors.
|
| furl(INOMICS)(http://www.inomics.com/query/search)+nl()
| not only
| provides an index of RePEc data but also allows simultaneous searches
| in indexes of other web pages related to Economics.
|
| The dq(Tilburg University Working papers and research memoranda) service is
| operated by a library-based group that has received funding from the
| European Union. INOMICS is operated by the Economics consultancy
| url(Berlecon)(http://www.berlecon.de). All the other user services are
| operated by junior academics.
|
| subsect(The usage of user services)label(sec:upta)
|
| Thomas Krichel founded both the WoPEc user service in 1993 and NEP in
| 1998. Jos\'e Manuel Barrueco has been the intensively involved in WoPEc
| user education. Our experience suggests that the average users from
| developed countries are at the postgraduate and doctoral level. There are
| many users in developing countries. In these countries the user commonity
| includes more senior levels, ie()more junior academics and professional
| researchers rather than students. For them the RePEc user services are one
| of the very few means to get hold of research papers. We think that this is
| the most rewarding aspect of our work. The free provision of RePEc helps to
| reduce the gap between the informationally rich and the informationally
| poor.
|
| The use of RePEc services among senior academics in the developed countries
| seems to be low. Is this because these people are too much set in their
| ways to use these modern facilities? We do not think so.
| Some people think that the low usage by tenured academics
| We believe that
| the current user services do not meet the information needs of these
| people. Academics do not need large-scale information services that they
| can search. The larger the scale the more likely they are to find
| information they did not seek and the less likely they are to find
| information that they want. Since they are working within a very narrow
| field and only have little time to read a small amount of literature
| small-scale information services are more tailored to their needs. In
| addition the contents of the service should be highly selective. Among the
| current user services that are built on the RePEc data, NEP comes closest
| to such services. Our anecdotal evidence suggests that this is the service
| that has the largest proportion of tenured academics.
|
| RePEc as such can not provide small-scale user services. It can only
| provide the basis for such user services to exist. We are aware of two
| approaches to build such services. Section 4 of
| latexcommand(\citeN{serpar99online}) whenhtml(url(Krichel, Lyapunov and
| Parinov (1999))(http://gretel.econ.surrey.ac.uk/papers/zhenya.pdf))
| describes design features for a current awareness portal system where each
| researcher could register the subject and type of records that she is
| interested in. The portal would then be able to inform the researcher about
| new resources in her field. A second approach is outlined is Section 6 of
| latexcommand(\citeN{kribau99edel}) whenhtml(url(Baum and Krichel
| (1999))(http://netec.mcc.ac.uk/AcMeS/edel.html)) Here the idea is to build
| peer review web (dq(SurWeb)) services. These are supposed to extend NEP to
| full peer review. It is too early to speculate if such a system can be put
| into place.
|
|
| sect(Conclusions)label(sec:conc)
|
| The free provision of educational material can be implemented through a
| central institution. Such an institution needs to be subsidized by central
| funds. The alternative is to provide the resources by a large number of
| agents. Then the cost of providing access can be absorbed within each
| institution. In that case the question of a comprehensive catalog
| arises. Such a catalog is needed to provide access to the collection in a
| unified way.
|
| In this paper we have dealt with the provision of a key resource
| ie()academic papers. We have presented a collection of metadata that is
| provided by decentralized archives. We have found that it is possible to
| build such a collection to a reasonable degree of accuracy if some archives
| where mistakes occur are aided by others. There needs to be a small group
| of people who actively support the collection. However this support can be
| given in decentralized fashion without the need for much coordination
| between supporters.
|
| The academic library commonity in the United Kingdom as a whole has made a
| important contribution to RePEc by donating funds to the work of the WoPEc
| project. This has allowed the WoPEc project to collect metadata about
| papers that are published by institutions that are not yet contributing to
| RePEc. This was a vital aspect of WoPEc project. The data collected by
| WoPEc constituted 90% of the RePEc data when RePEc was founded. However
| nowadays that proportion is falling. The funding for WoPEc has run out but
| the WoPEc web site continues to expand because of the contributions by made
| by RePEc archives. The software is maintained by volunteers.
|
| Librarians should carefully consider the vision of the project. This is a
| kind of academic self-organization where academics publish and catalog their
| own work. RePEc benefits from network externalities. The more academics join
| the more those who have not joined will feel pressure to join. If the data is
| freely available than authors can commonicate with their peers without the need
| of intermediaries. The providers of intermediation services have every reason
| to be worried. They include publishers em(and)+latexcommand(\/) librarians. If
| librarians do not play a more active part by supporting developments like RePEc
| there will be no more r\^ole for them in the future. Write to
| url(RePEc@netec.mcc.ac.uk)(mailto:repec@netec.mcc.ac.uk)
|
|
| latexcommand(\bibliography{bib})
|
| whenhtml(
|
| The work
| discussed here has received financial support by the Joint
| Information Systems Committee of the UK Higher Education Funding
| Councils through its
| url(Electronic Library Programme)(http://www.ukoln.ac.uk/services/elib).
| We are grateful to
| url(Christopher F. Baum)(http://fmwww.bc.edu/EC-V/Baum.fac.html),
| url(Robert P. Parks)(http://wueconb.wustl.edu/~bob/),
| url(Thorsten Wichmann)(http://www.berlecon.de) and
| url(Christian Zimmermann)(http://www.er.uqam.ca/nobel/r14160/index.html)
| for comments on the questionnaires. The topic of
| link(Subsection ref(sec:upta))(sec:upta)
| was suggested by url(Jane Greenberg)(http://ils.unc.edu/~janeg).
| url(William L. Goffe)(http://wuecon.wustl.edu/~goffe/) and
| Christian Zimmermann
| made many helpful suggestions.
| Sophie C. Rigny kindly pointed
| out many stylistic and grammatical errors in an earlier version.
| )
|
|
| htmlcommand(
Appendix:
| The composition of the dataset by archive
|
| )
| latexcommand(\appendix%\setcounter{table}{4})
|
| whenlatex(sect(The composition of the dataset by archive))
|
|
| latexcommand(\setcounter{table}{4})
| latexcommand({\small)
| longtable(11)(lrlrlrlrlrl)(
| row(cellsl(11)(url(School of Economics and Management, University of Aarhus, Denmark)(ftp://ftp.eco.aau.dk/RePEc/aah)))
| row(celll(RePEc:aah)cellr(2)celll(series)cellr(200)celll(papers)cellr(0)celll(articles)cellr(162)celll(errors)cellr(5)celll(warnings))
| row(cellsl(11)(url(Ecological Economics Program RePEc Archive)(http://cres20.anu.edu.au/anzsee/RePEc/anu)))
| row(celll(RePEc:anu)cellr(1)celll(series)cellr(14)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Bank of Canada)(ftp://ftp.bank-banque-canada.ca/pub/publications/RePEc/bca)))
| row(celll(RePEc:bca)cellr(2)celll(series)cellr(47)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Brazilian Electronic Journal of Economics)(http://www.beje.decon.ufpe.br/RePEc/bej/)))
| row(celll(RePEc:bej)cellr(2)celll(series)cellr(0)celll(papers)cellr(3)celll(articles)cellr(20)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(RePEc archive at Berlecon Research)(http://www.berlecon.de/repec/ber)))
| row(celll(RePEc:ber)cellr(1)celll(series)cellr(4)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Working Papers Archive of the Bank of England )(http://www.bankofengland.co.uk/RePEc/boe/)))
| row(celll(RePEc:boe)cellr(1)celll(series)cellr(94)celll(papers)cellr(0)celll(articles)cellr(25)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(RePEc archive at Bonn University)(ftp://ftp.wipol.uni-bonn.de/pub/RePEc/bon)))
| row(celll(RePEc:bon)cellr(2)celll(series)cellr(682)celll(papers)cellr(0)celll(articles)cellr(86)celll(errors)cellr(348)celll(warnings))
| row(cellsl(11)(url(Brown University, Department of Economics)(http://econ.pstc.brown.edu/bro/)))
| row(celll(RePEc:bro)cellr(1)celll(series)cellr(56)celll(papers)cellr(0)celll(articles)cellr(1)celll(error)cellr(14)celll(warnings))
| row(cellsl(11)(url(Banking & Finance Conference Papers)(http://www.usq.edu.au/repec/caf)))
| row(celll(RePEc:caf)cellr(1)celll(series)cellr(6)celll(papers)cellr(0)celll(articles)cellr(1)celll(error)cellr(0)celll(warnings))
| row(cellsl(11)(url(Department of Applied Economics Working Paper Archive)(http://www.econ.cam.ac.uk/dae/repec/cam)))
| row(celll(RePEc:cam)cellr(3)celll(series)cellr(81)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Concordia University, Department of Economics)(http://artsci-ccwin.concordia.ca/economics/Discusp/ccd/)))
| row(celll(RePEc:ccd)cellr(1)celll(series)cellr(2)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Centre for Economic Performance, London School of Economics)(ftp://cepnt.lse.ac.uk/upload/cep)))
| row(celll(RePEc:cep)cellr(3)celll(series)cellr(362)celll(papers)cellr(0)celll(articles)cellr(57)celll(errors)cellr(613)celll(warnings))
| row(cellsl(11)(url(CEPII)(http://www.cepii.fr/RePEc/cii)))
| row(celll(RePEc:cii)cellr(1)celll(series)cellr(81)celll(papers)cellr(0)celll(articles)cellr(42)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Canadian Journal of Economics)(ftp://pacific.commerce.ubc.ca/pub/cje/)))
| row(celll(RePEc:cje)cellr(1)celll(series)cellr(0)celll(papers)cellr(76)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Levine's Working Paper Archive)(http://levine.sscnet.ucla.edu/RePEc/cl)))
| row(celll(RePEc:cla)cellr(1)celll(series)cellr(43)celll(papers)cellr(0)celll(articles)cellr(1)celll(error)cellr(0)celll(warnings))
| row(cellsl(11)(url(CEPREMAP Archive)(http://www.cepremap.cnrs.fr/~adrepec/cpm/)))
| row(celll(RePEc:cpm)cellr(1)celll(series)cellr(770)celll(papers)cellr(0)celll(articles)cellr(1)celll(error)cellr(7)celll(warnings))
| row(cellsl(11)(url(Department of Economics Discussion Papers Archive at City University)(http://www.city.ac.uk/economics/RePEc/cty/)))
| row(celll(RePEc:cty)cellr(1)celll(series)cellr(34)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Working Papers of the Department of Economics at Dalhousie University)(http://is.dal.ca/~econhome/RePEc/dal)))
| row(celll(RePEc:dal)cellr(1)celll(series)cellr(0)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(DEGREE)(http://greywww.kub.nl:2080/dgr/)))
| row(celll(RePEc:dgr)cellr(18)celll(series)cellr(1203)celll(papers)cellr(0)celll(articles)cellr(663)celll(errors)cellr(292)celll(warnings))
| row(cellsl(11)(url(Archive for RePEc at UPV-EHU)(http://www.et.bs.ehu.es/RePEc/ehu)))
| row(celll(RePEc:ehu)cellr(1)celll(series)cellr(7)celll(papers)cellr(0)celll(articles)cellr(2)celll(errors)cellr(1)celll(warning))
| row(cellsl(11)(url(Fondazione Eni Enrico Mattei)(ftp://www.feem.it/RePEc/fem)))
| row(celll(RePEc:fem)cellr(1)celll(series)cellr(54)celll(papers)cellr(0)celll(articles)cellr(371)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Financial markets Group, London School of Economics)(http://cep.lse.ac.uk/fmg/fmg/)))
| row(celll(RePEc:fmg)cellr(3)celll(series)cellr(429)celll(papers)cellr(0)celll(articles)cellr(75)celll(errors)cellr(449)celll(warnings))
| row(cellsl(11)(url(Universitaet Frankfurt, Wirtschaftswissenschaften)(http://www.wiwi.uni-frankfurt.de/~rschmidt/RePEc/fra/)))
| row(celll(RePEc:fra)cellr(1)celll(series)cellr(31)celll(papers)cellr(0)celll(articles)cellr(5)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Economics Working Paper Archive at the University of Glasgow)(http://www.gla.ac.uk/Acad/PolEcon/RePEc/gla)))
| row(celll(RePEc:gla)cellr(1)celll(series)cellr(54)celll(papers)cellr(0)celll(articles)cellr(30)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Heriot Watt University, Edinburgh)(ftp://ftp.hw.ac.uk/pub/eco/ecoaab/RePEc/hwe/)))
| row(celll(RePEc:hwe)cellr(2)celll(series)cellr(62)celll(papers)cellr(0)celll(articles)cellr(1)celll(error)cellr(0)celll(warnings))
| row(cellsl(11)(url(IGIER-Innocenzo Gasparini Institute for Economic Research)(ftp://cervino.igier.epol.uni-bocconi.it/RePEc/igi/)))
| row(celll(RePEc:igi)cellr(1)celll(series)cellr(58)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Economic Working Paper Archive at University of Jena)(http://www.wiwi.uni-jena.de/Papers/jen/)))
| row(celll(RePEc:jen)cellr(2)celll(series)cellr(56)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(1)celll(warning))
| row(cellsl(11)(url(CoFE Discussion Paper)(ftp://enterprise.wiwi.uni-konstanz.de/RePEc/knz)))
| row(celll(RePEc:knz)cellr(1)celll(series)cellr(6)celll(papers)cellr(0)celll(articles)cellr(78)celll(errors)cellr(1)celll(warning))
| row(cellsl(11)(url(University of Leicester Disccussion Papers in Economics)(http://www.le.ac.uk/economics/research/RePEc/lec/)))
| row(celll(RePEc:lec)cellr(3)celll(series)cellr(89)celll(papers)cellr(0)celll(articles)cellr(2)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Lester Ingber Papers Archive)(http://www.ingber.com/RePEc/lei/)))
| row(celll(RePEc:lei)cellr(1)celll(series)cellr(50)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Universite Laval, Departement d'economique)(ftp://ftp.ecn.ulaval.ca/pub/RePEc/lvl/)))
| row(celll(RePEc:lvl)cellr(2)celll(series)cellr(152)celll(papers)cellr(0)celll(articles)cellr(1)celll(error)cellr(1)celll(warning))
| row(cellsl(11)(url(Economics Working Paper Archive NUIM)(http://www.may.ie/academic/economics/RePEc/may/)))
| row(celll(RePEc:may)cellr(1)celll(series)cellr(31)celll(papers)cellr(0)celll(articles)cellr(5)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Non-monetary economics)(http://www.postman.ru/~yurimax/RePEc/mc)))
| row(celll(RePEc:mce)cellr(1)celll(series)cellr(2)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Economics Working Paper Archive at McGill)(http://www.arts.mcgill.ca/programs/econ/RePEc/mcl/)))
| row(celll(RePEc:mcl)cellr(1)celll(series)cellr(7)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(McMaster University Department of Economics Working Paper Series )(ftp://socserv2.socsci.mcmaster.ca/pub/RePEc/mcm)))
| row(celll(RePEc:mcm)cellr(5)celll(series)cellr(274)celll(papers)cellr(0)celll(articles)cellr(4)celll(errors)cellr(1)celll(warning))
| row(cellsl(11)(url(Economics Working Paper Archive at Universidad Publica de Navarra (UPNA))(ftp://ftp.unavarra.es/pub/RePEc/nav)))
| row(celll(RePEc:nav)cellr(1)celll(series)cell(1)celll(paper)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Economics works by Nir Dagan and Oscar Volij)(ftp://ftp.nirdagan.com/RePEc/nid)))
| row(celll(RePEc:nid)cellr(2)celll(series)cellr(25)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Netnomics)(ftp://www.baltzer.nl/netnomics/RePEc/nnm/)))
| row(celll(RePEc:nnm)cellr(0)celll(series)cellr(0)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Economics Discussion Papers Archive at Nottingham)(http://www.nottingham.ac.uk/~lezec/economics/RePEc/not/)))
| row(celll(RePEc:not)cellr(2)celll(series)cellr(110)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(National Institute of Economic and Social Research)(http://www.niesr.ac.uk/RePEc/nsr/)))
| row(celll(RePEc:nsr)cellr(1)celll(series)cellr(126)celll(papers)cellr(0)celll(articles)cellr(7)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(SUNY-Oswego Economics Department Working Paper Archive)(ftp://economic.oswego.edu/RePEc/nyo)))
| row(celll(RePEc:nyo)cellr(1)celll(series)cellr(5)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Ohio State University, Department of Economics)(http://economics.sbs.ohio-state.edu/osu/)))
| row(celll(RePEc:osu)cellr(1)celll(series)cellr(18)celll(papers)cellr(0)celll(articles)cellr(1)celll(error)cellr(0)celll(warnings))
| row(cellsl(11)(url(Working Papers and Published Papers by Peter Cramton and Co-Authors)(ftp://ftp.cramton.umd.edu/RePEc/pcc/)))
| row(celll(RePEc:pcc)cellr(1)celll(series)cellr(38)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Queen Elizabeth House Papers Archive at Oxford University)(ftp://pc4.qeh.ox.ac.uk/RePEc/qeh/)))
| row(celll(RePEc:qeh)cellr(1)celll(series)cellr(21)celll(papers)cellr(0)celll(articles)cellr(5)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Centre for International Business Centre)(ftp://ftp.sbu.ac.uk/pub/RePEc/sbu )))
| row(celll(RePEc:sbu)cellr(3)celll(series)cellr(4)celll(papers)cellr(0)celll(articles)cellr(2)celll(errors)cellr(11)celll(warnings))
| row(cellsl(11)(url(CSEF-Centre for Studies in Economics and Finance Working Papers)(ftp://netec.mcc.ac.uk/pub/NetEc/RePEc/sef)))
| row(celll(RePEc:sef)cellr(1)celll(series)cellr(20)celll(papers)cellr(0)celll(articles)cellr(1)celll(error)cellr(9)celll(warnings))
| row(cellsl(11)(url(University of Ličge (Belgium) Faculty of Econonomics, Management and Social Sciences+whenhtml(Department of Economics Service of International and Interregional Economics (SEII)))(ftp://ntsem9.egss.ulg.ac.be/ecoint/RePEc/sei)))
| row(celll(RePEc:sei)cellr(1)celll(series)cellr(7)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Economics Discussion Paper Archive at the University of Siegen, Germany
)(http://www.uni-siegen.de/dept/fb05/vwliv/RePEc/sie)))
| row(celll(RePEc:sie)cellr(1)celll(series)cellr(19)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Economics Working Paper Archive at the University of Sussex)(http://www.sussex.ac.uk/economics/RePEc/sus)))
| row(celll(RePEc:sus)cellr(1)celll(series)cellr(51)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(University of Toronto, Department of Economics)(ftp://econra.eco.utoronto.ca/RePEc/tor/)))
| row(celll(RePEc:tor)cellr(1)celll(series)cellr(91)celll(papers)cellr(0)celll(articles)cellr(2)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Economic Working Paper Archive at UPO)(http://www.al.unipmn.it/~segrsp/Fac_Scienze_Politiche_II/pubbl/RePEc/uca)))
| row(celll(RePEc:uca)cellr(1)celll(series)cellr(2)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Department of Economics, University of Iowa)(http://www.biz.uiowa.edu/econ/RePEc/uia/)))
| row(celll(RePEc:uia)cellr(1)celll(series)cellr(135)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Department of Economics Discussion Papers Archive at the University of Kent)(ftp://ftp.ukc.ac.uk/pub/apd/RePEc/ukc)))
| row(celll(RePEc:ukc)cellr(1)celll(series)cellr(58)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Electronic Working Papers, Department of Economics, University of Maryland
)(http://www.bsos.umd.edu/econ/RePEc/umd )))
| row(celll(RePEc:umd)cellr(1)celll(series)cellr(11)celll(papers)cellr(0)celll(articles)cellr(34)celll(errors)cellr(3)celll(warnings))
| row(cellsl(11)(url(Economics Working Paper Archive at Universitat Pompeu Fabra)(ftp://www.econ.upf.es/RePEc/upf/)))
| row(celll(RePEc:upf)cellr(3)celll(series)cellr(227)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Department of Economics, University of Victoria)(ftp://ftp.uvic.ca/econ/RePEc/vic)))
| row(celll(RePEc:vic)cellr(2)celll(series)cellr(16)celll(papers)cellr(0)celll(articles)cellr(2)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Centre for the Study of Globalisation and Regionalisation (CSGR))(http://www.warwick.ac.uk/fac/soc/CSGR/RePEc/wck/)))
| row(celll(RePEc:wck)cellr(2)celll(series)cellr(51)celll(papers)cellr(0)celll(articles)cellr(78)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(SFB504 Working Paper Archive)(ftp://mailhost.sfb504.uni-mannheim.de/pub/RePEc/xrs)))
| row(celll(RePEc:xrs)cellr(1)celll(series)cellr(110)celll(papers)cellr(0)celll(articles)cellr(6)celll(errors)cellr(3)celll(warnings))
| row(cellsl(11)(url(Economics Working Paper Archive at York)(http://www-users.york.ac.uk/~econ32/RePEc/yor/)))
| row(celll(RePEc:yor)cellr(1)celll(series)cellr(190)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| )(The loose archives)
| latexcommand(})
|
| latexcommand({\small)
|
| longtable(11)(lrlrlrlrlrl)(
| row(cellsl(11)(url(Australian Prudential Regulation Authority)(http://www.apra.gov.au/research/RePEc/apr/)))
| row(celll(RePEc:apr)cellr(1)celll(series)cellr(4)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Birkbeck College Economics Working Paper Archive)(ftp://netec.mcc.ac.uk/pub/NetEc/RePEc/bbk)))
| row(celll(RePEc:bbk)cellr(3)celll(series)cellr(111)celll(papers)cellr(0)celll(articles)cellr(1)celll(error)cellr(4)celll(warnings))
| row(cellsl(11)(url(Boston College Department of Economics)(ftp://ftp.bc.edu/pub/user/baum/RePEc/boc)))
| row(celll(RePEc:boc)cellr(3)celll(series)cellr(373)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(1)celll(warning))
| row(cellsl(11)(url(Economics Working Paper Archive at Brunel Universtiy)(ftp://netec.mcc.ac.uk/pub/NetEc/RePEc/br)))
| row(celll(RePEc:bru)cellr(3)celll(series)cellr(119)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(C. E. P. R.)(ftp://netec.mcc.ac.uk/pub/NetEc/RePEc/cpr)))
| row(celll(RePEc:cpr)cellr(2)celll(series)cellr(1406)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Research Center on Economic Fluctuations and Employment (CREFE))(ftp://crefe.dse.uqam.ca/pub/RePEc/cre)))
| row(celll(RePEc:cre)cellr(5)celll(series)cellr(142)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(1)celll(warning))
| row(cellsl(11)(url(Department of Economics and Finance Discussion Papers Archive at the University of Durham
)(http://www.dur.ac.uk/Economics/RePEc/dur/)))
| row(celll(RePEc:dur)cellr(1)celll(series)cellr(54)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Econometrica)(ftp://ftp.bc.edu/pub/user/baum/RePEc/ecm)))
| row(celll(RePEc:ecm)cellr(1)celll(series)cellr(0)celll(papers)cellr(346)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(ELSE - ESRC Center for Economic Learning and Social Evolution)(ftp://ada.econ.ucl.ac.uk/pub/RePEc/els)))
| row(celll(RePEc:els)cellr(1)celll(series)cellr(57)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Fed in Print)(ftp://netec.mcc.ac.uk/pub/NetEc/RePEc/fip )))
| row(celll(RePEc:fip)cellr(107)celll(series)cellr(4682)celll(papers)cellr(8819)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(BibEc Project)(ftp://netec.mcc.ac.uk/pub/NetEc/RePEc/fth)))
| row(celll(RePEc:fth)cellr(400)celll(series)cellr(28759)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(S-WoBA, Swedish Working Papers in Business Administration)(ftp://swopec.hhs.se/RePEc/hhb)))
| row(celll(RePEc:hhb)cellr(2)celll(series)cellr(12)celll(papers)cellr(0)celll(articles)cellr(2)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(S-WoPEc, Swedish Working Papers in Economics)(ftp://swopec.hhs.se/RePEc/hhs)))
| row(celll(RePEc:hhs)cellr(9)celll(series)cellr(536)celll(papers)cellr(0)celll(articles)cellr(2)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(National Bureau of Economic Research, Inc.)(http://nberws.nber.org/RePEc/nbr/)))
| row(celll(RePEc:nbr)cellr(4)celll(series)cellr(7684)celll(papers)cellr(0)celll(articles)cellr(1)celll(error)cellr(2966)celll(warnings))
| row(cellsl(11)(url(Russian Working Paper Archive for Economists and Sociologists)(ftp://www.ieie.nsc.ru/pub/RePEc/nos/
| URL: http://www.ieie.nsc.ru/~rupec/RePEc/nos/)))
| row(celll(RePEc:nos)cellr(1)celll(series)cellr(8)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Reserve Bank of Australia)(http://www.rba.gov.au/RePEc/)))
| row(celll(RePEc:rba)cellr(1)celll(series)cellr(249)celll(papers)cellr(0)celll(articles)cellr(334)celll(errors)cellr(758)celll(warnings))
| row(cellsl(11)(url(Review of Economic Dynamics)(ftp://crefe.dse.uqam.ca/pub/RePEc/red/)))
| row(celll(RePEc:red)cellr(2)celll(series)cellr(0)celll(papers)cellr(62)celll(articles)cellr(0)celll(errors)cellr(4)celll(warnings))
| row(cellsl(11)(url(University of Surrey Economics Department)(ftp://www.econ.surrey.ac.uk/pub/RePEc/sur)))
| row(celll(RePEc:sur)cellr(1)celll(series)cellr(10)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(Trinity College Dublin)(ftp://netec.mcc.ac.uk/pub/RePEc/tcd/)))
| row(celll(RePEc:tcd)cellr(2)celll(series)cellr(8)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(1)celll(warning))
| row(cellsl(11)(url(Economics Working Paper Series at Texas )(ftp://mundo.eco.utexas.edu/pub/care/RePEc/tex)))
| row(celll(RePEc:tex)cellr(1)celll(series)cellr(20)celll(papers)cellr(0)celll(articles)cellr(6)celll(errors)cellr(1)celll(warning))
| row(cellsl(11)(url(Universidad de Valencia, Facultad de Ciencias Economicas)(ftp://ftp.uv.es/pub/econom/RePEc/val)))
| row(celll(RePEc:val)cellr(7)celll(series)cellr(151)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| row(cellsl(11)(url(WoPEc Project)(ftp://netec.mcc.ac.uk/pub/NetEc/RePEc/wop)))
| row(celll(RePEc:wop)cellr(205)celll(series)cellr(4763)celll(papers)cellr(804)celll(articles)cellr(58)celll(errors)cellr(12)celll(warnings))
| row(cellsl(11)(url(WUSTL archive)(ftp://netec.wustl.edu/RePEc/wpa)))
| row(celll(RePEc:wpa)cellr(25)celll(series)cellr(1142)celll(papers)cellr(0)celll(articles)cellr(1)celll(error)cellr(0)celll(warnings))
| row(cellsl(11)(url(WoPEc UK Archive)(ftp://netec.mcc.ac.uk/pub/NetEc/RePEc/wuk)))
| row(celll(RePEc:wuk)cellr(46)celll(series)cellr(1585)celll(papers)cellr(0)celll(articles)cellr(0)celll(errors)cellr(0)celll(warnings))
| )(The controlled archives)
|
| latexcommand(})
|
| COMMENT(
| There is a central archive RePEc:all, that mirrors all the
| em(???arch.rdf) and em(???seri.rdf) files from all archives. It
| also contains the software that allows sites to mirror archives. RePEc:all
| also provides reading and checking software for templates as well as
| general RePEc documentation. This archive lives at
| tturl(ftp://netec.mcc.ac.uk/pub/RePEc/all).
| )
|
|
| COMMENT(
| LocalWords: notableofcontents whenlatex latexcommand otnote Thorsten Wichmann
| LocalWords: Zimmermann thispagestyle vfill ll Tarongers tturl barrueco endash
| LocalWords: abs interoperable dq ref indi soci conc Longrightarrow gt guil lr
| LocalWords: htmlcommand redi subsect citeN petdeu homepage XML emdash WUStL
| LocalWords: allowbreak Shuetrim Parinov cont loos celll cellr wpa wuk hhb fth
| LocalWords: fip bbk cpr nbr ecm val apr boc nos cre bru tex tcd subsubsect ie
| LocalWords: WoBa sunkar whenhtml Fethy's suppo Kurmanov farty bendtt rech jel
| LocalWords: rela URLs admin webmaster lrlrl attent dgr lrllrllrl attr templ
| LocalWords: redif eval fileformat regex RFC yyyy dd longtable lrlrlrlrlrl aah
| LocalWords: cellsl anu bca bej Berlecon ber boe bon bro caf ccd Centre cep Co
| LocalWords: CEPII cii cje Levine's cla CEPREMAP cpm cty dal UPV EHU ehu Eni
| LocalWords: Fondazione Mattei fem fmg Universitaet Wirtschaftswissenschaften
| LocalWords: fra gla hwe IGIER Innocenzo Gasparini igi Jena jen CoFE knz lec
| LocalWords: Leicester Disccussion Ingber lei Universite Laval Departement lvl
| LocalWords: d'economique NUIM mce mcl McMaster mcm Universidad Publica UPNA
| LocalWords: Navarra nav Nir Dagan Volij nid Netnomics nnm nsr SUNY Oswego nyo
| LocalWords: osu Cramton pcc qeh sbu CSEF sef Li ge Econonomics SEII sei sie
| LocalWords: Siegen sus tor UPO Scienze Politiche uca uia ukc umd Pompeu Fabra
| LocalWords: upf vic Globalisation Regionalisation CSGR wck SFB xrs yor Brunel
| LocalWords: Birkbeck Universtiy CREFE dur ESRC rba Facultad Ciencias noindent
| LocalWords: Economicas Tilburg RuPEc upta serpar Lyapunov kribau edel SurWeb
| LocalWords: coar Haworth mySQL consultancy informationally Programme hr appe
| LocalWords: tcounter tlength tabcolsep eal txt MSdos heterodox co Este creo
| LocalWords: ejemplo que es claro lo quitaria pues aporta nada nuevo solamente
| LocalWords: matiza un nivel puede confundir lector Por adir aqui grafico mas
| LocalWords: Quedaria mucho Si quieres tenemos tiempo puedo practicar poco Una
| LocalWords: vez hemos dise uno podemos aplicarlo toda documentacion jmbc por
| LocalWords: Tipica pregunta pueden hacer otro formato aceptado como DC eg si
| LocalWords: necesaria lista involveh Qu ebec esta frase da impresion archivos
| LocalWords: obra una institucion debe garantizar su permanencia pero verdad
| LocalWords: indicador seria cuando dejado actualizarse desde hace Quizas otra
| LocalWords: habria notar falta bibliotecarios enfatizar catalogacion ahora yo
| LocalWords: manos los autores distribuidores anecdota Aunque muy para unos UK
| LocalWords: significativa entenderla necesitan conocimientos seguramente aun
| LocalWords: tiene encuantra ninguna siga leyendo articulo ser Rigny Mili's de
| LocalWords: ole INCLUDEFILE jagt mac url RePEc Baum sec Goffe Jos Krichel Ci
| LocalWords: Biblioteca encies Socials Gregori Maians Universitat encia dels
| LocalWords: Guildford GU XH thomas krichel PDF WoPEc downloadable offline ftp
| LocalWords: repec http al NEP metadata mir undisputedly ReDIF ocumentation se
| LocalWords: nformation ormat sur surarch rdf surseri surrec WorkPlace pdf hhs
| LocalWords: Karlsson IAFA Valencia Sune Montr EconWPA xxx Fethy Mili perl nl
| LocalWords: Universit homepages seri BibEc html NetEc repref USmarc SUTRS GRS
| LocalWords: INOMICS WoBA WAIS Heriot
| ) |