General • arXiv • Refereed status • Submissions
General
Q: How often do new articles get added to the database?
This depends on the source. We ingest from arXiv daily; from astronomy journals and other sources weekly, over the weekend; and from physics journals and other sources about once every 3 weeks, also over a weekend.
Q: How do I submit missing articles or corrections to an existing article? Missing references?
Note that these forms do not work if you’re using the basic HTML version of ADS, and occasionally, some users encounter errors when submitting these forms; email us if you run into issues.
Q: My paper is visible at the publisher but not in ADS yet.
Published articles are added to the database at regular intervals; see the publishing schedule above. In addition, for most journals, we do not add the article until it has a published volume and page number. While we appreciate the early access versions, we have found that matching them after the fact and tracking all citations correctly is difficult to do correctly.
If sufficient time has passed since the publication date and the article is still unavailable, it may be in a journal we don’t index by default. It’s also possible that the article has been added, but is not appearing the expected collection (astronomy or physics); this is generally the case if the article appears in a general science journal (Nature, Science) where we need keyword information to assign it to a specific collection. Finally, in rare cases deliveries from publishers are missing some articles. If you believe your article should be in the database already, email us for help.
Q: What are bibliographic groups (bib groups)? These appear in a left-side filter.
Bibliographic groups are hand curated by librarians and/or curators at various institutions and generally contain a list of publications produced by researchers at a given institution or using specific telescope(s). If you’re a librarian or curator interested in curating a publicly available collection, email us.
Q: My name is incorrect in an ADS record.
We receive author names and other metadata directly from the publisher. First check that your name is correct on the published article; if it isn’t, first contact the publisher directly to fix it with them. However, if your name is correct with the publisher and wrong in the ADS database, fill out this form and we’ll correct it.
Q: My name has changed since I first started publishing. How can I ensure people find all of my papers when searching for my name?
We offer three options; one or more of these may suit your needs. Email us for help deciding which option(s) are best for you and for making any necessary updates:
- We maintain a list of author synonyms, so searches for one author name return results for both names. Let us know all of the names you’ve published under to have your names added to this list. (Note that common name variations, such as publishing under your entire first name vs. just an initial, are already included in searches.)
- You may also consider registering for an ORCID ID and using that to maintain a personal bibliography.
- If you’d prefer that previous names not be visible in ADS, we can modify our searchable metadata on papers published under the previous name(s) to reflect your current name. With this option, all pages within ADS (e.g. search results, paper abstract pages) will reflect the new name; note, however, that we cannot modify external data and links, such as publisher-provided PDFs.
For more information, see our name change policy.
Q: What journals and other material do you index?
Complete lists of the journals, conferences, and other sources we index may be found here.
Q: What papers do you have the full text for?
In general, we have searchable full text for most major journals in astronomy and physics, especially recent volumes. This includes articles in the arXiv.
Q: How do I get my conference proceeding in ADS?
Full instructions for submitting conference proceedings can be found here.
arXiv
Q: My arXiv paper is missing its references.
We extract references directly from the PDF for arXiv records, which doesn’t always work well, depending on reference and document format. If the paper will be published, we will get the reference list from the publisher and will update the references on the record at that point. Note also that we’re working on a new module for extracting references directly from PDFs and arXiv reference extraction should improve at that point.
Q: My arXiv paper had some citations before it was published. Will these be lost once the published version is out?
We automatically merge the arXiv and published versions of papers, including citations.
Q: The author list of the arXiv and the published versions of my paper are different. What happens when the two versions are merged?
Author metadata from the published version takes precedence, so arXiv-only coauthors will be removed from the record.
Q: The published version of my paper is out and indexed on ADS, but the arXiv version is listed separately.
The published and the arXiv versions of a paper should merge into a single entry automatically. Occasionally that doesn’t work; let us know and we’ll fix it.
Q: My name is correct on arXiv but wrong in ADS. How can I fix it?
Submit your corrections using this form.
Q: My name is wrong in arXiv, will you fix it?
You’ll need to contact the arXiv directly for corrections to your papers on their site.
Refereed status
Q: Why is my PhD thesis listed as refereed?
ADS has decided to list PhD theses as refereed because they go under the review of a thesis committee and are thus “peer reviewed.” However, if you prefer to not see PhD theses appear in your search results, restrict your search results to articles only using the “Publication Type” filter in the left-side column.
Q: A conference proceeding is listed as non-refereed even though it underwent peer review.
Most conference proceedings are not refereed. They may be reviewed by an editor, but rarely is there the kind of rigorous review as is done by many journals. (In general, users and editors and librarians and publishers all have different opinions on what constitutes “peer-reviewed.”)
If a publication or a conference is generally not peer-reviewed, all articles/proceedings within that publication/conference will automatically be listed as non-refereed. If a particular article/proceeding within the generally non-refereed publication/conference is peer-reviewed, have the editors email us to confirm and we can correct the listing.
Submissions
Q: How do I submit my PhD thesis?
Some institutions send us their recent PhD theses directly, though it may take a few months post-defense for us to receive them. However, if your institution does not send us your thesis, you have several options to add it to our database:
- Zenodo Astronomy Thesis collection: This is an open-source repository of astronomy theses and dissertations which is automatically ingested into ADS roughly once a month. If your thesis is already indexed by ADS but the text is not openly accessible, you can upload a copy of the PDF to make it openly available. This is a good option if you’d like your thesis to be openly available and it’s not currently accessible online.
- ADS submission: You can submit your thesis metadata directly to ADS for indexing. If you want the PDF to be linked to the record, it will first need to be hosted somewhere online and then you can provide the URL and other metadata using this form. If the text of your thesis is not already available online and you’d like it to be, consider submitting it to the Zenodo collection.
Q: My name (or title, etc.) is misspelled on my paper.
If it is wrong on the publisher’s website, you’ll need to contact them to correct the error, as we’ve agreed with the publishers to reflect the data they pass on to us.
If it’s right on the publisher’s website but wrong on ours, we’re sorry for the error! Contact us so we can fix it.
Q: How can I get my software package indexed in ADS?
Software records are automatically indexed in ADS once they have a Zenodo record and have been cited at least once. If you’d like to make your software records eligible for indexing in ADS, complete the following steps:
- Upload your software code to Zenodo. You can do this directly or by linking to a Github repository. If you link to a Github repository, you can specify a specific release or version, or you can link to the top-level repository to create a non-version-specific record.
- Get the BibTeX (or other bibliographic format) record from Zenodo and cite it in your paper as normal. Your software will not yet be in ADS, so make sure to get the citation information from Zenodo.
- Once your paper has been published and is indexed in ADS, ADS will recognize that the bibliography contains a software record and will automatically create a corresponding software record in the ADS database. The publisher will be listed as Zenodo and the bibstem (the abbreviation that appears in the bibcode) will be zndo. The publication type for these records is software.
Some things to keep in mind:
- Zenodo allows you to create different records for different versions of your software, which generally correspond to different releases in Github. This can be beneficial if the software has changed substantially with time, or if different authors have worked on different versions of the code and need to be acknowledged as appropriate. ADS will index each Zenodo version of your software separately, as long as each has citations. Currently, citations are counted for each version separately, but eventually it will be possible to see all citations for all versions of a software package in one record in ADS.
- The Astrophysics Source Code Library indexes astronomy-related software that has been used in a publication. ADS indexes these ASCL records (bibstem: ascl, publication type: software) and they can collect citations similarly to the process above. One difference between the two processes is that ASCL indexes only the non-version-specific record while Zenodo indexes each version separately. It is possible for a given software package to be in both Zenodo and ASCL, if they fit the necessary criteria for each.
Q: I submitted some ORCID claims but they don’t show up when I search by my ORCID ID.
These can take up to 24 hours to index. Please contact us if they aren’t showing up after this time.
This section is intended to be a guideline for editors and authors wishing to submit conference proceedings for inclusion in the ADS Abstract and Scanned Literature Services. Any questions about the procedure should be directed to adshelp@cfa.harvard.edu.
The ADS is pleased to include any conference proceedings volume, as well as individual conference proceedings abstracts. This includes both electronic and printed conference proceedings. We have a set of naming conventions detailed below, but are flexible if there is a different naming scheme which is more appropriate for your particular conference. If you would like to have your conference proceedings included in our database before your conference, we request that you submit them to us one month in advance of the start of your conference.
Submitting Bibliographic Records for the ADS Abstract Service
Please send us an email at adshelp@cfa.harvard.edu with the information to make a conference entry in the ADS.
In addition a file containing the following should be sent to the ADS. Individual Article Entries should include the following tags ( ( * ) items are required.)
( * ) %T Title
( * ) %A Author List
%F Author Affiliation
( * ) %P First Page of Article
%L Last Page of Article
%I Links to online resources (see below)
%B Abstract Text
%Z References
%K Keywords
Please note that there are many more details that you can add but these are the required minimum tags. A complete list of ADS tagged fields can be found here. Please note that references containing TeX/LaTeX formatting, AASTeX macros and HTML entities are acceptable.
A long entry should continue on the next line(s) with no repetition of the percent sign and keying letter. All entries should be in ascii and there should be no tabs or control characters. Blank lines can delimit paragraphs in the abstract, but should not otherwise be present within a record. A title, author list, and page number are required. Other information such as author affiliation, links to online full-text, abstract text and references are strongly recommended as well. The more information that you can provide for each article, the better. This additional information will aid in searching and using advanced features in the ADS.
This information can be submitted via email to ads@cfa.harvard.edu or placed on our anonymous ftp site, under ftp://adsftp.harvard.edu/pub/Conf. Please send us an email indicating when you have transferred things to us, so that we can include it in our database as soon as possible.
Including Full-text Papers in the ADS
It is possible for us to make the full-text of articles published in conference proceedings available via the ADS Article Service. This section describes the requirements and procedures to be followed in order to do that.
Note: We do not publish original material that is not published elsewhere, since we are not a publisher.
Provide written permission from the copyright holder allowing the ADS to publish electronically the papers in the conference proceedings. The relevant letter should state something along the following lines:
The <full description of the copyright holder> grants permission to the Astrophysics Data System at the Smithsonian Astrophysical Observatory to:
1. Convert postscript files to tiff files for <name of conference>
2. Add a note at the bottom of each page with the following content:
(©) <name of copyright holder> - Provided by the Astrophysics Data System
3. Make the images of the articles electronically available, free of charge, for all volumes starting 1 year after publication
Feel free to modify as you see fit, especially item three, then send a copy of a signed copy of the permission letter to:
Donna Thompson
Astrophysics Data System
Harvard-Smithsonian Center for Astrophysics
60 Garden Street, M.S. 83
Cambridge, MA 02138
USA
Send us either a printed copy of the conference proceedings book or (if available) the set of full-text files used to create the proceedings. If only a printed book is available, please send it to Alberto Accomazzi at the address listed above along with the permission letter. If full-text PostScript or PDF files are available for all papers, please read on.
To submit the full-text files with the necessary information for us to process them, you will need to create a tar or zip archive and transfer it to our ftp server. This is what must be included in the archive file:
-
All the files containing the full-text, including front-matter (introductory) and back-matter (index) pages if available. You should make sure that these files are either in PostScript or PDF format, and that they have been created using 600dpi or higher resolution fonts. (Note: if you are using
dvips
to create the postscript file, you can specify the options-D600 -Z
on the command-line to have 600dpi fonts included). -
A file named README, containing general information concerning this publication, the name and email address of the person submitting the full-text papers to us, and any additional information we should be aware of.
-
A file named PUBLICATION, containing the full name of the conference or book (you should use the same name given in the journal field above).
-
A file named COPYRIGHT, containing the copyright string that needs to be displayed at the bottom of each page that the ADS creates and places online in its article service (please do not try to include the copyright symbol © since we already do this for you).
-
A file named BIBSTEM, containing the bibliographic abbreviation for the publication (e.g. ASPC..117 or 2000immm.proc). This should be the same abbreviation that has been used to create the bibliographic entries described above.
-
Optionally, a PAGEMAP file containing mapping of full-text file names to page numbers, if these cannot be determined from the full-text files themselves. Whether or not this is needed is a function of how the files were originally created; usually if you used LaTeX and dvips to create the postscript files then the page numbering displayed on each page is carried into the postscript files and can be automatically extracted at least for “regular” pages. Pages which are part of the front-matter may need to have entries associated with them. The format of the PAGEMAP file is the following:
# This is a comment file1.ps C1-C4 # first file has cover pages 1-4 file2.ps C6 # second file has cover page 6 file3.ps 1-8 8A 9-15 # third file has pages 1-8, insert 8A, 9-15 file4.pdf 16- # fourth file has pages 16 and up
When in doubt, please contact us for help.
Create a compressed tar or zip archive containing of all the full-text files, the README file, and name of the file using (if possible) the standard acronym adopted by the ADS in naming bibliographic entries for the conference. For example, the archive file containing papers submitted to the ASP Conference Proceedings n.117 should be named ASPC117.tar.gz or ASPC..117.tar.gz. The archive for files containing the conference 2000immm.proc should be named 2000immm.proc.tar.gz.
Deposit the tar archive on our anonymous ftp server under the URL ftp://adsftp.harvard.edu/pub/Conf and notify us. We will contact you with any questions regarding the full-text processing of the files.
Archiving Conference Proceedings in the ADS
As more conferences are published electronically, editors are turning to the ADS for long-term archiving of their full text proceedings. We can agree to this under the following conditions:
- The conference is originally published elswhere (e.g. through a university or observatory publication, or through another publisher).
- We receive the pdf or postscript files as described above.
- The data have been published at least three years ago.
The ADS Tagged Format
We welcome the submission of Bibliographic Records from librarians and researchers willing to provide this information to the ADS. To facilitate the insertion of this data into our databases, we request that the records be submitted in electronic form and adhere to the following format:
%R Bibliographic Code (required)
%A Author List
%a Review Authors
%b Book Authors
%F Author Affiliation
%J Journal Name
%D Publication Date
%P First Page of Article
%L Last Page of Article
%T Title (required)
%t Original Language Title
%C Abstract Copyright
%O Object Name
%G Origin
%I Links to other information
%U Unified Astronomy Thesaurus (UAT) keywords
%K Keywords
%M Language (if not English)
%X Comment
%W Collection (if submitting for more than one)
%B Abstract Text
%Z References
A long entry should continue on the next line(s) with no repetition of the percent sign and keying letter. All entries should be in ascii and there should be no tabs or control characters. Blank lines can delimit paragraphs in the abstract, but should not otherwise be present within a record. The bibliographic code is the only field which is required for all records, but author list, journal name, publication date, and title are strongly recommended as well. Additional records should be separated by a blank line.
Fields in the Tagged Format
Detailed descriptions of each field follow.
Bibliographic Code
The bibliographic code is a 19 digit code (see Bibcodes)
Author List
The author list should contain semi-colon separated authors listed with last name first, followed by first name or initials. A paper with one author would be listed as Minkowski, R. A paper with multiple authors would be listed as
Neubauer, F. J.; Burwell, C. G.; Miller, W. C.
Authors whose names contain “Jr” or “III” should be entered as
Roberts, L. C., Jr.
Review Authors
This contains the review authors in the same format as the regular authors.
Book Authors
This contains the book authors in the same format as the regular authors.
Author Affiliation
The institution with which the author is affiliated. If more than one author affiliation is to be listed, here is the suggested format:
AA(first author's institution) AB(second author's institution) ...
Email addresses can be specified in the author affiliations. Please mark them as follows:
<EMAIL>email address</EMAIL>
Journal Name
This entry contains the reference information, including the journal name, volume, and page range. Also include here any editors of books or conference proceedings.
Publication Date
This contains the publication month and year of the article in the format MM/YYYY (i.e. 02/1995). If no publication month is known, please use a month of 00.
First Page of Article
This contains the first page number of the article.
Last Page of Article
This contains the last page number of the article.
Title
%T contains the title of the article. If there is also an original language title, it can be submitted with a %t and the language included in the %M tag.
Object Name
This contains the name of Objects described in the paper. These are normally handled through SIMBAD and are therefore not part of the user input except in special circumstances.
Origin of the Article in ADS
This contains the source of the record in ADS.
Abstract Copyright
This contains a copyright statement of the abstract, such as (C) 1990: American Astromomical Society
Unified Astronomy Thesaurus keywords
This contains keywords from the Unified Astronomy Thesaurus (UAT), separated by a comma.
Links to Other Information
Links should be preceded by their link type and semi-colon separated, e.g.
%I DOI: 10.1234/article_doi; PDF: https://article_pdf
Available links include arxiv, data, doi, electr, pdf and other.
Keywords
This contains keywords related to the article, separated by a comma.
Language
This contains the original language of the article.
Comment
This contains author comments.
Collection
This contains the database key if you are submitting abstracts for multiple databases (astronomy: AST, physics: PHY, general: GEN).
Abstract
This contains the abstract text. Any line beginning with at least one blank space will be assumed to be a new paragraph. New paragraphs may also be delimited with blank lines. Abstracts should not contain tables, and will appear best in the system if they contain only ascii characters.
References
This field should contain the list of references cited by the current paper. They should be formatted so that there is just one reference per line, e.g.:
%Z Bechtold,~J., \etal 1994, \aj, 108, 374
Massa, D. L., & Savage, B. D. 1984, ApJ, 279, 310
Savage, B. D., & Mathis, J. S. 1979, ARA&A, 17, 73
Please note that references containing TeX/LaTeX formatting, AASTeX macros and HTML entities are acceptable.
Examples of Records in Tagged Format
This section shows a few examples of our tagged format.
Example 1:
%R 1993ApJ...415...50C
%A Cavaliere, A.; Colafrancesco, S.; Menci, N.
%J Astrophysical Journal, Part 1, vol.415, no. 1, p. 50-57.
%D 09/1993
%L 57
%T Distant clusters of galaxies detected by X-rays
%K Cosmic Plasma, Dark Matter, Galactic Clusters, X-ray Astronomy, Baryons, Luminosity, Redshift
%B The dynamical masses of groups and clusters of galaxies decrease on average with increasing redshift, after the hierarchical cosmogonies dominated by direct collapses of dark matter overdensities. We show that the masses of intracluster plasma emitting in the X-ray band are to decrease more rapidly. We also show that consideration of the intrinsic spread in the dynamical formation times leads us to predict more numerous faint sources at given dynamical mass. The model we compute yields steeper luminosity functions in the X-ray band with a specific change in lookback time: the bright end shifts back. Such negative evolution is fast even at modest redshifts z less than about 0.5 if the external gas infalling into groups of clusters was preheated and has cooled down after z of about 1.5-2. If so, the evolution is considerably faster in the X-ray than in the optical band, comparing interestingly with data from the existing surveys.
%Z Abell, Ci. 0. 1958, ApJS, 3, 211
Barcons, X., Fabian, A. C., & Rees, M. J. 1991, Nature, 350, 685
Bardeen, J. M., Bond, J. R., Kaiser, N., & Szalay, A. 5. 1986, ApJ, 403, 15
Blumenthal, Ci., Faber, S. M., Primack, J. R., & Rees, M. J. 1984, Nature, 311, 517
Bohringer, H., et al. 1991, in Proc. NATO ASI "Clusters and Superclusters of Galaxies," ed. A. C. Fabian (Dordrecht: Kluwer), 71
Burg, R., Cavaliere, A., & Menci, N. 1993, ApJ, 404, L55
Cavaliere, A., Gursky, H., & Tucker, W. H. 1971, Nature, 231, 437
Cavaliere, A., & Colafrancesco, 5. 1988, ApJ, 331, 660
---. 1990, in Clusters of Galaxies (Cambridge: Cambridge Univ. Press), 43
Cavaliere, A., Burg, R., & Giacconi, R. 1991, ApJ, 366, L61
Example 2:
%T Adsorption behavior of a textile dye of Reactive Blue 19 from aqueous solutions onto modified bentonite
%A Gök, Özer; Safa Özcan, A.;Özcan, Adnan
%P 5439
Example 3:
%T Seeing Red: Extremely Red Objects from the Cadis K' Survey
%A Thompson, D.; Beckwith, S. V. W.
%F AA(Max-Planck-Institut fuer Astronomie, Koenigstuhl 17, D-69117 Heidelberg, Germany)
%P 13
%B We discuss various interpretations of the nature of extremely red objects (EROs), discovered in the first of 7 deep, wide-field K' images in the CADIS survey. Point sources with K' = 20.5 mag are detected at the 5 sigma level over an area of 125 arcmin^2. A total of 20 EROs meeting the selection criteria (R-K') >= 6^{m} and K' <= 19.75 mag were selected from the data, giving a surface density of 0.16 +/- 0.04 arcmin^{-2} for all EROs and 0.016 +/- 0.011 arcmin^{-2} for bright (K' < 19^{m}) EROs.}
Example 4:
%T Chandra observations of M31 and their implications for its ISM
%A Primini, F., Garcia, M., Murray, S., Forman, W., Jones, C., and McClintock, J.
%F AA(Harvard-Smithsonian Center for Astrophysics, Cambridge, USA), AB(Harvard-Smithsonian Center for Astrophysics, Cambridge, USA), AC(Harvard-Smithsonian Center for Astrophysics, Cambridge, USA), AD(Harvard-Smithsonian Center for Astrophysics, Cambridge, USA), AE(Harvard-Smithsonian Center for Astrophysics, Cambridge, USA), AF(Harvard-Smithsonian Center for Astrophysics, Cambridge, USA)
%B We have been regularly observing the bulge and inner disk of M31 for nearly one year, using both the HRC-I and ACIS-I instruments on the Chandra X-Ray Observatory. We present results from our program that are of interest to the study of the ISM in M31. In particular, we find that the unresolved emission within 3' of the center of M31 has a distinctly softer spectrum than that of most of the resolved X-ray sources in the region. Preliminary spectral analysis of bright point sources in the bulge shows no evidence (within the poor statistics) for soft spectral components, but does reveal significant extra-galactic X-ray extinction (NH ~ 1021 cm-2). We find no new X-ray counterparts to supernova remnants to date.
Example 5:
%T We Do Not Forget Johannes Kepler
%A Wszołek, B
%B Year 2009 was announced as the International Year of Astronomy. This was to mark 400th anniversary of the first astronomical observation through a telescope by Galileo. From the other hand, this year marks 400th anniversary of Astronomia Nova, the famous work of Kepler published in Prague in 1609. Two laws of planetary motions opened human efforts to understand gravitational force; so the overall cosmic space conquest, with its great importance not only for astronomy, was developed thankful to Kepler's work. This contribution is thought to show the most inspiring ideas of Johannes Kepler, published in Astronomia Nova and in other his books.
%I PDF: FILE:proc16_02.pdf
How do you evaluate journals for inclusion?
The ADS evaluates all journals for coverage using the criteria listed below. We seek comprehensive, but not all-inclusive, coverage of the field of astronomy, and we take into consideration relevancy of content, standards of presentation, and regularity of publication. We evaluate journals on an ongoing basis and add or delete journals regularly. ADS reserves the right to exclude content deemed inappropriate for its collection or inconsistent with its editorial policies. To be accepted for coverage, a journal must:
- Be relevant to astronomy
- Be of a quality and scope of interest to an international audience
- Have an ISSN
- Be registered with CrossRef
- Follow standard conventions for scholarly journals
- Have an informative title and descriptive article titles
- Include full addresses for authors
- Include abstracts and key words
- Include references that are current, from quality journals, and of an appropriate number for the article in a standard format
- Contain usable metadata including: abstracts, titles, and keywords
- Demonstrate diversity of reviewers and authors
- Include all or mostly all original articles
- Contain articles that are substantiated with empirical data or other means
- Be published on a regular schedule appropriate for the established frequency of the journal
- Have articles that are written by professionals in their field.
In addition, e-journals must:
- Provide evidence of archiving arrangements, online or otherwise
- Include a posting date for articles and revisions
- Have published at least three issues
Features that support acceptance:
- Sponsorship by a astronomy or physics association or other society
- Astronomers or physicists among editorial board members and authors
- Indexed in other scholarly databases
- Online access
- English table of contents
- Transliterated references
- Frequency of publication clearly advertised on masthead or web page
For e-journals
- Presence of version number
- Indication of where previous versions can be obtained Links
Relevance: An article that includes any of the following may be relevant:
- the scientific study of astronomy
- content in any of the subfields of astronomy or physics
- non-astronomy content of interest to astronomers in different subfields
- content in related fields that has astronomical relevance
If you have a journal to be evaluated, please feel free to send email to us at adshelp@cfa.harvard.edu.
The ADS curation model is represented by the diagram below (see Kurtz et al. 2021).
![ADS Curation Model](../img/curation_model.png)
The Core Collection consists of the main journals for the disciplines covered, the most influential journals. As we move into the inner and outer rings, curation efforts decrease. A qualitative characterization of the model is given below.
Core: main journals for discipline
- Complete, authoritative coverage of the literature
- High-level data products and software indexed
- Links to datasets and archives
Inner Ring: closely related disciplines
- Most refereed journals covered
- Some conf proceedings, some gray literature
- Citation and fulltext coverage incomplete
Outer Ring: connected to inner content
- Incomplete coverage of the literature because outside of disciplinary scope
- Includes content from multidisciplinary journals (e.g. Nature) or repositories (arXiv)
- No curation applied other than basic error corrections
How do we determine which journals go in which section? Once the Core Collection has been populated, appropriate journals for the Inner and Outer Rings can be determined as indicated in the diagram above. Up to now, journal selection for the Core Collection has been heuristic, based on qualitative arguments and domain knowledge. We felt it was important to formulate selection criteria based on quantitative arguments. These quantitative selection criteria are unavoidably based on journal metrics and just like any metric, journal metrics are not without controversy. We have settled on the so-called Journal Eigenfactor as the main indicator for journal importance. More details on how this metric was used to determine the journal selection for the Core Collection can be found in this blog.
SciX contains extensive holdings of historic astronomy and astrophysics literature. As resources permit, we continue to digitize and ingest relevant items recommended by community members. In addition, we accept scans of appropriate material that meet these technical standards. Please contact the SciX curators before beginning your project to ensure we can accommodate your proposal. We will also determine an effective delivery method then.
We request that each page be scanned and saved as a single TIFF file. In all cases, a journal is scanned cover-to-cover with no pages skipped (even the blank ones). These images will need to comply with the following quality and naming requirements.
Quality requirements
Pages need to be scanned at a resolution of 600 dpi. Further requirements depend on the contents of the page. The following table specifies these requirements for each page type.
Parameter | Setting |
---|---|
Page type | Exclusively text and line art |
Dynamic range | 1-sample/pixel and 1-bit/sample |
Compression | CCITT G4 encoding, with all image data encoded in a single strip |
Photometric interpretation | min-is-white |
Planar configuration | single image plane |
Orientation | portrait |
Page type | Page with gray-scale images |
Dynamic range | 1-sample/pixel and 8-bits/sample |
Compression | LZW or Deflate |
Photometric interpretation | min-is-black |
Planar configuration | single image plane |
Orientation | portrait |
Page type | Page with color images |
Dynamic range | 3-samples/pixel and 8-bits/sample |
Compression | LZW or Deflate |
Photometric interpretation | RGB |
Planar configuration | single image plane |
Orientation | portrait |
If a page contains both gray-scale and color content, follow the instructions for a page with color images.
Scanned images should have consistent borders around the text area and should be scanned in portrait orientation, with a maximum skewness of 2 degrees. Cropping of images is allowed, in order to clean up possible image contamination from paper borders. Resizing, however, is not allowed. The resolution of 600 dpi is to be maintained consistently. This means that the image dimensions divided by 600 should closely approximate the physical dimensions of the digitized area in inches.
Page numbering
We expect you will take quality assurance measures to guarantee that pages will not be skipped during the scanning process, causing file names to be out of sync with the sequence of pages in the journal.
We request that each page be scanned and saved as a single TIFF file, named after the journal acronym, volume and page number according to the templates described below; the journal acronym can be provided by the SciX team. If a journal acronym contains an ampersand (&), it needs to be replaced by a plus sign (+). Ideally, file extensions like .tif or .tiff should be omitted.
Typically, a page in a journal is one of the 6 following types:
- Regular pages: these are the pages numbered with arabic numerals, which constitute the main body of the volume
- Letter pages: some journals have an introductory section of the journals where notes or letters to the editor are published
- Inserts: some journals contain inserts much larger than the regular page size, which are folded up and bound with the rest of the pages
- Plates: some journals have plates at the end of each volume or issue which are labeled by consecutive plate numbers
- Front matter: all pages preceding the “Regular” or “Letter” pages and starting from the cover
- Back matter: all pages following the last numbered page (or plate) and ending with the back cover
The file naming requirements for these page types are as follows:
Page type | Naming requirements |
---|---|
Regular | The scans should be saved in files named JNLvvv.nnnn, where JNL is an abbreviation of the journal name, vvv is the volume number and nnnn is the zero-padded page number. For instance, page number 100 for volume 200 of the journal Astronomy & Astrophysics (A+A) should be saved in a TIFF file named A+A200.0100. Note: some journals may contain pages that, although not numbered, have an implied page number which can be easily inferred by their position within the sequence of numbered pages. In all cases these pages should be named after the corresponding implied page number. Sometimes regular pages are a combination of a letter and a number, like A1, in which case the letter should get included in the page numbering; for instance, the page “A10” in volume 33 of the journal “M+PS” should be saved in a file named “M+PS033.A010.”. If a journal volume consists of multiple issues that all start on page 1, please contact us for more detailed instructions. |
Letter | These pages are labeled with the letter “L” followed by an increasing number, starting from page L1. These scans should be saved in files named according to the following template: JNLvvv.Lnnn, where the file extension consists of the letter “L” followed by the zero-padded page number (three digits long). |
Insert | If the physical size of the insert is 11” x 17” or smaller, a reduced copy of the scan should be created so that the resulting image size will match the typical page size of the journal being scanned. If the size of the insert is greater than 11” x 17”, then multiple scans of the different parts of the image should be performed, each having a scanning area size equal to the one used for the typical pages of the current journal. If such inserts are not numbered according to the regular page numbering scheme, they should be assigned a file name created by appending a 3-digit sequential number to the filename of the preceding page. For instance, an insert appearing after page 100 of volume 200 of the journal Astronomy & Astrophysics should be saved in a file named A+A200.0100I001 |
Plate | The plate scans should be saved in files named according to the following template: JNLvvv.nnnnPppp, where the file extension consists of the current page number nnnn (or the preceding page if the plate does not have a page number associated with it), followed letter “P” followed by the zero-padded plate number displayed on the page (ppp). |
Front matter | All pages preceding the “Regular” or letter pages and starting from the cover should be scanned and saved in files JNLvvv.nnnnCddd, where the file extension consists of the number corresponding to the first numbered page following the cover pages (nnnn), followed by the letter “C,” followed by a zero-padded sequence number (ddd). These pages are typically numbered using roman numerals and include all pages in the journal’s “front matter” section. |
Back matter | All pages following the last numbered page (or plate) and ending with the back cover should be scanned and saved in files named JNLvvv.nnnnZddd, where the file extension consists of the number corresponding to the last numbered page preceding the back-cover pages (nnnn), followed by the letter “Z,” followed by a zero-padded sequence number (ddd) |
In case generating this file naming scheme presents problems, an alternative acceptable solution would be to provide us with a set of files and a lookup-table mapping the file names delivered into the file names in our requested format described above.
What are Bibgroups?
Bibgroups are libraries that are curated by librarians, archivists and scientists who are not ADS/SciX employees. Descriptions of each bibgroup include information that details the coverage in the collection and frequency of updates. Many of the bibgroups include contact information for the maintainer. We maintain links to ADS legacy bibgroups that are no longer updated but contain useful information.
CFHT
This bibliographic group includes peer reviewed papers by researchers worldwide using data from the Canada-France-Hawaiʻi Telescope CFHT. CFHT is located on Maunakea, land of the Kānaka Maoli people, and a mountain of considerable cultural, natural and ecological significance to the Indigenous Hawaiian people. It comprises all papers utilizing every instrument ever used at CFHT, dating back to 1979 when the first CFHT paper was published. The CFHT community consists primarily of scientists from Canada, France and the University of Hawaiʻi, and from institutions in Taiwan, China, Brazil and Korea, though research teams often include members outside this community. The list also features papers using archival data since 2013 and data from catalogs built with CFHT data since 2015. The contributions from the CFHT Legacy Survey to archival and catalog research are significant. Covering a wide array of topics, CFHT’s contributions span from the discovery of Gravitational Arcs and the characterization of Dark Energy to studies of the light curve of `Oumuamua and the discovery and follow-up of Near-Earth Objects and Potential Hazardous Asteroids, highlighting its significant impact on numerous scientific fields.
ESO/Telescopes
This group contains refereed articles using data from ESO (European Southern Observatory) telescopes. Papers since publication year 1996 using data from Paranal (VLT, VLTI, VISTA, VST) or Chajnantor facilities (ESO observing time of APEX or ALMA) as well as La Silla papers since publication year 2000 reference the program IDs from which the data originated. They are linked to the corresponding raw data or data products located in the ESO Science Archive. The database is maintained by the ESO Library and can be queried in more detail at https://telbib.eso.org. It is updated daily. For further questions, please contact the ESO librarians at library@eso.org.
HST
This group contains refereed articles using Hubble Space Telescope data, which can be obtained from the Mikulski Archive for Space Telescopes (MAST) at Space Telescope Science Institute (STScI). The bibgroup also contains engineering and instrumentation-related papers found in the literature. Note that matching HST proposal IDs to published papers is an on-going project and never completely up to date. Articles are linked to the program IDs and observational data on which they are based whenever feasible. For further information, please contact metrics@stsci.edu.
Gemini
This group contains refereed articles based on observations (including observatory archive) made at the International Gemini Observatory, NSF NOIRLab. The coverage is from 2000 to present and the group is updated monthly. The Gemini Publications by Users webpage contains more information such as instruments and observation program IDs used for the publication.
JWST
This group contains refereed articles using James Webb Space Telescope data, which can be obtained from the Mikulski Archive for Space Telescopes (MAST) at Space Telescope Science Institute (STScI). The bibgroup also contains engineering and instrumentation-related papers found in the literature. Note that matching JWST proposal IDs to published papers is an ongoing project and never completely up to date. Articles are linked to the program IDs and observational data on which they are based whenever feasible. For further information, please contact metrics@stsci.edu.
Chandra
This group contains articles where Chandra data contributes significantly to the science in the article, also known as Chandra Science Papers. Those articles that present specific Chandra observations are linked to the data in the Chandra Data Archive on which they are based. The database is maintained by the Chandra Data Archive and can be queried in more detail with our search tool. For publication statistics, please visit the Chandra Bibliography Statistics page.
Chandra/Technical
Chandra/Technical - This group contains articles pertaining to the Chandra mission and includes articles about Chandra instruments, software, and operations. The Chandra Data Archive maintains a repository of these papers grouped by individual instrument, operations, and software.
MAST
This group contains refereed science articles that have analyzed data from NASA’s International Ultraviolet Explorer (IUE), which was active from 1978 Jan. through 1996 Sept. Data products from IUE are hosted at the Mikulski Archive for Space Telescopes (MAST). The papers include results from the earliest days of the mission to the present day, with topics that span a wide range of research areas. This collection is updated approximately annually.
NOIRLab
The NOIRLab bibgroup is a curated list of the U.S. National Science Foundation National Optical-Infrared Astronomy Research Laboratory (NSF NOIRLab / NOIRLab). The bibgroup comprises refereed science data publications in a core set of journals that use NOIRLab telescope data and/or NOIRLab data products & services. The bibgroup includes publications relating to the International Gemini Observatory from 2000 to present and publications relating to NOIRLab data products & services and the other NOIRLab telescopes from 1990 to present. Telescopes included are the NOIRLab Mid-Scale Observatories (MSO) telescopes: Nicholas U. Mayall 4-meter Telescope; WIYN 3.5-meter Telescope; and WIYN 0.9-meter Telescope, located at Kitt Peak National Observatory, Tucson, Arizona, USA; the Víctor M. Blanco 4-meter Telescope and SMARTS Consortium telescopes, located at Cerro Tololo Inter-American Observatory, La Serena, Chile; and the SOAR telescope, located at Cerro Pachón, Chile; and the International Gemini Observatory Gemini North and Gemini South telescopes. The bibgroup also includes publications that make use of NOIRLab-granted community-access time on non-NOIRLab telescopes. NOIRLab data products and provided by the NOIRLab Community Science and Data Center include the Astro Data Archive, Astro Data Lab, NOIRLab Source Catalog, ANTARES, and NOIRLab IRAF. The bibgroup is updated weekly.
SETI
The SETI bibgroup is a topical bibliographic group, part of a project at the Penn State Extraterrestrial Intelligence Center to find and track the SETI literature. This includes all kinds of technosignature search, theoretical explorations of the nature of technological alien life, and social aspects of SETI such as METI and post-detection protocols. The bibgroup is continuously maintained, and one can subscribe to receive a selection of monthly updates to it as new papers are published at seti.news. The methodology is described in Reyes & Wright (2019) and LaFond et al. (2021). The intention is that the bibgroup be comprehensive including every ADS/SciX entry relevant to SETI. Questions, comments, or notices of omissions can be directed to astrowright@gmail.com.
SOHO
ADS Library of refereed publications for the ESA/NASA SOHO mission, starting in 1995. This library is maintained by acting ESA SOHO Project Scientist, Daniel Mueller (Daniel.Mueller@esa.int) and updated every two months. SOHO data is publicly available from the ESA SOHO Science Archive, SunPy, and the Virtual Solar Observatory.
Solar Orbiter
ADS Library of refereed publications for the ESA/NASA Solar Orbiter mission, starting in 2020. This library is maintained by ESA Deputy Solar Orbiter Project Scientist Yannis Zouganelis (Ioannis.Zouganelis@esa.int) and updated every two months. Solar Orbiter data is publicly available from the ESA Solar Orbiter Archive, SunPy, and the Virtual Solar Observatory.