Public Access to the USDA, ARS, USMARC Genome Database It is desirable that markers be placed on publicly available linkage maps as soon as possible; however, publication rights of scientists developing markers must be protected. The MARC genome database will restrict data access as outlined below to accomplish both objectives. Each marker in the database will have associated with it two attributes (fields) called CURATOR and PUBLIC MARKER that will be used to control access to data. CURATOR will be the "owner" or "developer" of the marker. (Markers will be group owned by the laboratory in which they are developed.). The attribute PUBLIC MARKER will have the value Y or N depending on whether or not the marker has been published. The curator of the marker will decide when a marker shall become public. It is expected that a marker will become public when it is published. A user of the database will have access to all information on markers that are public and markers for which he/she is the curator. Information on other non-public markers that relates to the identity, ownership, or development of the marker will be restricted. This includes the marker name, curator of the marker, type of marker, and all information needed to develop the marker such as primer sequences and clone sequence. Implications and consequences: - Once genotypic data for a marker have been entered, the data will be accessible to all users for linkage analysis, including data on unpublished markers. Unpublished, or non-public, markers will be designated on the maps only by their arbitrary MARKER NUMBER, eg. 343. Again, it will not be possible to link this data back to marker name, primer sequences, and other background information. - Outside users of the database will be able to extract data and do their own linkage analyses. A feature of the database is a table (shell) for a consensus map. If they desire, each NAGRP specie committee can submit and monitor the consensus map. We can store the map as provided by a consensus of the NAGPR specie committee and can make changes in the consensus map at the direction of the committee chairman/coordinator. The database will allow a user to request information on an unpublished marker from the marker's curator without the curator's identity being revealed. For example, user X could make a request for information for unpublished marker 822 and submit a statement of what he/she is interested in and why he/she is interested in marker 822. The database would send an email message to the curator of marker 822 informing him/her that Dr. X of email address ....@.......... is interested in marker 822 and attaching Dr. X's statement of interest. The curator of the marker could then contact Dr. X if interested in providing the information or in collaborating with Dr. X.