...
- For user-supplied collections based on large projects, and NRAO collections (e.g. NVSS, legacy image archive) one DOI will be issued per collection, linked to the collection such that clicking on the DOI will direct the user to an archive results page listing the dataset. This DOI should be displayed prominently during archive searches, and on the page describing the collection's data release. Users will be strongly encouraged to cite the DOI in papers (for example, as a footnote, see Long et al. (2020) using the dataset keyword http://archive.stsci.edu/doi/faq.html#faq31 for AAS journals), along with any journal article describing the dataset. A A new DOI will be issued if a new reduction of the bulk of the dataset is supplied, but not in the case of small updates.
- For VLASS, several DOIs will be issued based on product collections (Quick Look, Single Epoch, Cumulative, per EDP set supplied). Again, these should be displayed prominently in archive searches and on the VLASS science website.
- VLA pipeline images will receive one generic DOI per major pipeline version (e.g. data processed with 2020.x; 2021.x would get different DOIs, but not those with 2020.1 and 2020.2). These will be prominently shown in product searches.
- User-requested images (AUDI and VUDI) will receive one DOI per primary FITS image created. These will be prominently shown in product searches.
- DOI metadata following the DataCite schema (http://schema.datacite.org, for an example see http://archive.stsci.edu/doi/resolve/resolve.html?doi=10.17909/t9-9skz-qw10) should be provided when creating each DOI.
- Users will be strongly encouraged to cite the DOI in papers (for example, as a footnote, see Long et al. (2020) using the dataset keyword http://archive.stsci.edu/doi/faq.html#faq31 for AAS journals), along with any journal article describing the dataset. This description should be linked prominently from the archive webpages and other related pages (VLASS science, per-collection confluence pages and NRAO Library pages).
- DOI links should be regularly tested to ensure they still perform the correct searches, and updated if necessary.