|
|
|
- Step by step instruction for RcLIS contributors - This documents how to contribute your working paper series. You will be taken step by step for a minimal installation. For a journal, the steps are slightly different, in particular regarding the handles, as explained at the bottom.We now also include examples for books and book chapters. See the full documentation for details. While we believe that our setup is rather simple and many should be able to apply it easily, you may hire someone for a nominal fee to do it for you on a regular basis. Contact Imma Subirats in this regard. First, you need to contact to our discussion list to signifiy your interest in joining RcLIS. You will be given a three letter name for your archive, say xxx for our examples. Then, you need an anonymous ftp server or an http server (the former being strongly prefered). There, create a directory called RcLIS (be precise with the capitalization, if possible). Now create in the RcLIS directory a directory called xxx. Go there. Now you need to write two separate files: one describing the archive, one for the series provided. To describe the archive, create a file called xxxarch.rdf, where, remember, xxx is the name of your archive. rdf stands for ReDIF, which itself stands for Research Documentation Information Format. It is a way to uniformly codify all the information your are going to provide. Here we will go through the essentials, you can get more details in the ReDIF documentation. Templates to cut and paste and fill out are available. This archive description should be like this:
The following lines are mandatory: Template-Type, Maintainer-Email, Name and URL. The handle is a uniform way of referencing the documents, so your handle would be RcLIS:xxx. If you want to use accented characters and such, go ahead: the convention is the character set ISO-LATIN-1. We urge not to use the html tags for accented characters. In the same RcLIS/xxx directory is the file describing all the series you archive, in a file named xxxseri.rdf, which looks like this:
Mandatory are the following fields: Template-Type, Handle, Name, Maintainer-Email. Provider-Name is necessary if you want the series enumerated in the list of all series. Each series get a six character string to identify it. Lets say we have a series we call abcdef, then its handle would be RcLIS:xxx:abcdef. All series all listed in the same xxxseri.rdf file. Now create a subdirectory for each series, so for example a subdirectory called abcdef. There, you will provide information about the papers themselves. You may choose to do that in one file for all, or each paper a file, or otherwise. It is only important that all files have the rdf extension. For each paper you could have entries like these:
Mandatory are: Template-Type, Author-Name, Title, File-URL, File-Format and Handle. Notice that some fields are repeated, for example for authors and files. Just be sure that the email and other information relating to an author pertains to the Author-Name preceding that info. Similarly, all info about a downloadable file has to begin with File-URL. If a paper is not downloadable, skip the File-* lines. The handle for each paper in your case would be RcLIS:xxx:abcdef:*, where * can be anything you want (for example a paper number). The date format is yyyy-mm-dd (or yyyy-mm if the day is unknown). Note that you may add fields for your own purposes, they just have to follow a X-* syntax, where * is your choice. Now you have all the basics. There are many more fields allowed in ReDIF than described here, refer to the ReDIF documentation for a complete list. To check you coding, you may want to use the rech script (needs perl5). Finally, do not forget to put all access rights appropriately (chmod and such)! Once you are all set up, email rclis@lists.openlib.org to tell you are ready. The central server will then periodically retrieve your information and feed it to the mirroring services. Now that your a RcLIS archive maintainer. - Specificities for journals - Building an archive for a journal is very similar to working papers. A journal is considered to be a series of articles. This means that you write the xxxseri.rdf file just like a working paper series, but you and the following line: Type: ReDIF-Article The description of an article follows similar rules as for a paper. Note that the Template-Type: is now ReDIF-Article 1.0, and that an article can be reference differently. The following example should be self-explanatory:
Type: ReDIF-Book The description of a book follows similar rules as for a paper. Note that the Template-Type: is now ReDIF-Book 1.0, and that a book has several attributes that are different from a working paper. If the book's chapters are also indexed, they can be linked with (repeated) HasChapter: attributes. The following example should be self-explanatory:
- Specificities for chapters - Indexing chapters is not much different either. A chapter needs to be part of a series. This means that you write the xxxseri.rdf file just like a working paper series, but you and the following line: Type: ReDIF-Chapter The description of a chapter follows similar rules as for a paper. Note that the Template-Type: is now ReDIF-Chapter 1.0, and that if the book is also described in RcLIS, it can be linked through the In-Book: attribute:
Here are some template for use by archive maintainers. Cut and paste them, or save them, and then fill out. Delete unnecessary lines, repeat clusters (like author, file) as a whole. Addition attributes are available, please see the ReDIF documentation for complete details. Attributes that go over one line should start with an empty space in all subsequent lines. Series templates need all to be in the same file (xxxseri.rdf). It does not matter whether individual templates are in separate files or not, as long as they are all in the same directory (one for each series, directory name with 6 characters).
Available file formats:
|
Last updated: 2003-11-20 DoIS team
Italian DoIS