voyager data dictionary

.css-1lrpez4{margin-top:unset;}.css-1lrpez4:hover > span,.css-1lrpez4:focus-within > span{opacity:1;-webkit-transform:none;-ms-transform:none;transform:none;-webkit-transform-duration:0.1s;-ms-transform-duration:0.1s;transform-duration:0.1s;} Simplified Database Schema and Data Governance in Voyager .css-14vda7h{font-size:15px;margin-inline-start:0.5rem;opacity:0;position:absolute;-webkit-transform:translateX(-4px);-ms-transform:translateX(-4px);transform:translateX(-4px);-webkit-transition:opacity 0.2s ease-out 0s,-webkit-transform 0.2s ease-out 0s;-webkit-transition:opacity 0.2s ease-out 0s,transform 0.2s ease-out 0s;transition:opacity 0.2s ease-out 0s,transform 0.2s ease-out 0s;}

Voyager's registry and Data Governance Platform offer comprehensive solutions for managing and documenting your data environment. Key functionalities include:

Database Schema Documentation : Easily capture and outline your database structures directly in Voyager. This feature helps in visualizing and understanding the architecture of your databases, essential for maintenance and integration.

Data Dictionaries and Structures : Voyager's data dictionary module is a powerful tool that allows for the creation of detailed descriptions of each data element within your system. This feature goes beyond basic documentation; it enables you to link actual data with its corresponding entries in the data dictionary.

Detailed Descriptions : Start by crafting comprehensive definitions for each data element, including its type, format, usage, and any relevant constraints or relationships. This creates a rich, detailed understanding of each piece of data in your system.

Linking Data Elements : With Voyager, you can directly associate these dictionary entries with the actual data they describe. This linking turns the data dictionary into a dynamic, interactive map of your data landscape.

Unified Understanding : The integration of data elements with their dictionary descriptions ensures that every team member has immediate access to vital information about the data they are using. This facilitates consistency in data interpretation and usage across different departments and projects.

Enhanced Data Governance : This feature also strengthens data governance, as the linked dictionary entries provide clear guidelines and standards for data handling, ensuring compliance and maintaining data quality throughout the organization.

Data Governance Policies : Voyager allows you to document and enforce critical data governance policies. This includes setting rules for data integrity and protection, support for data retention policies in line with compliance needs, tracking data lineage and provenance for auditing, and establishing clear transparency for data usage and handling.

Voyager equips organizations with the tools to comprehensively document your data landscape, ensuring consistency, security, and compliance in your organization's data management practices. To learn more please contract our professional services team.

What's Where: Using the Voyager Class Diagrams and Data Dictionary With Access Queries

Sep 19, 2012

270 likes | 590 Views

What's Where: Using the Voyager Class Diagrams and Data Dictionary With Access Queries . ELSUG October 9, 2008 Cathy Salika CARLI Consortium of Academic and Research Libraries in Illinois. Voyager is a relational database. A relational database is a bunch of tables.

Share Presentation

• extraneous tables
• voyager technical user
• inefficient views circcharges vw
• data dictionaryprovides
• data dictionarygives
• fine fee type

Presentation Transcript

What's Where: Using the Voyager Class Diagrams and Data Dictionary With Access Queries ELSUG October 9, 2008 Cathy SalikaCARLI Consortium of Academic and Research Libraries in Illinois

Voyager is a relational database A relational database is a bunch of tables. A table looks like a spreadsheet.

Voyager has about 400 tables Some are things you probably expect PATRON, ITEM, CIRC_TRANSACTION Some are less obvious INV_LINE_ITEM_NOTES Some are used to look up common codes LOCATION, FINE_FEE_TYPE

The _ID Fields Many tables have a sequentially assigned number in a column with “_ID” in its name.

The _ID Fields Sometimes the relationship is made directly.

The _ID Fields Sometimes there’s an intermediary.

Starting to Write a Query • First you have to figure out • what data you need • what tables the data are in • how to correctly relate those tables • This is easier if you know about Voyager because you use it regularly.

Starting to Write a Query • A good query • is built a few tables at a time • is tested at each step of the way • has no extraneous tables

Starting to Write a Query There are two tools to show you what’s in the tables and how the tables relate. Voyager Class Diagrams available on SupportWeb Voyager Data Dictionary in the Voyager Technical User’s Guide But I recommend that you use the CARLI version of these documents.

CARLI’s Class Diagrams

CARLI’s Data Dictionary

CARLI’s Data DictionaryLists the columns in alphabetical order (except that the _ID fields come first)

CARLI’s Data DictionaryServes as an index to the class diagrams

CARLI’s Data DictionaryTells you which fields are in UNICODE so you can format them properly

CARLI’s Data DictionaryIncludes comments on what’s in the fields

CARLI’s Data DictionaryProvides lots of tips about where to find things.

CARLI’s Data DictionaryGives warnings about tables to avoid

CARLI’s Data DictionaryProvides help with tricky links

Where to Get Them • CARLI’s Data Dictionary and the additional Class Diagrams • Are in SupportWeb, in the KnowledgeBase. • Search for “CARLI” and you’ll find it. • Will soon be in the EL Commons • Are on these flash drives

Views Both versions of the Data Dictionary include views. Their names end with _VW Inside Voyager, a view is actually a query, but you can use them as if they were tables. Some views are helpful, some are inefficient, some are WRONG. So let’s see which are which.

Good Views Call Nos. DEWEYCLASS_VWLCCLASS_VWNLMCLASS_VWSUDOCCLASS_VWUDCCLASS_VW A call number is included in a view if the CALL_NO_TYPE in MFHD_MASTER says it should be there.

Good Views Fixed Field Data for BibsMARCBOOK_VWMARCCOMPUTER_VWMARCMAP_VWMARCMUSIC_VWMARCSERIAL_VWMARCVISUAL_VW

Inefficient Views CIRCCHARGES_VW CIRCRENEW_VW FUNDLEDGER_VWISSUES_VWITEM_VWSERIALS_VW • Why I don’t like them • Some use a dozen tables or more, so queries that use them are slow. • You have to know too much to understand their quirks. • (CIRCCHARGES_VW drops charge transactions if the item has been deleted.) • It’s too hard to make your statistics consistent.

If you want to know what the views doand you have access to SQLPLUS on your serverand you don’t mind reading a bit of SQL…here’s how. SQL> set heading off SQL> set long 4500 SQL> column view_name fold_a newl SQL> column text newl newl newl newl SQL> select view_name, text from all_views where owner=‘XXXDB’ order by view_name;

Bad Views AUTHBLOB_VWBIBBLOB_VWMFHDBLOB_VW They don’t work correctly for long records. When to use them: NEVER

And now, a commercial… If you’re new to query writing in Voyager, consider attending 2 other sessions: “Scary Queries Laid to Rest” by Jean Vik at 8:30am “Idiomatic Access Reports” at 9:30am

Questions?Thank you!

• More by User

Class Diagrams

Class Diagrams. (Design) Class Diagrams (1). A class diagram is a visual representation of various classes and their relationships as identified during design. Information in class diagram includes: classes, associations, and attributes interfaces with operations and constants methods

314 views • 14 slides

Class Diagrams. Terms and Concepts A class diagram is a diagram that shows a set of classes, interfaces, and collaborations and their relationships . Graphically , a class diagram is a collection of vertices and arcs. Common Properties

295 views • 16 slides

Access: Queries

Access: Queries. Chapters A1-A3 All Sections. Today’s Topic. Security. Hardware & Software. IS Basics. Information Quality. Types of IS. Telecommu-nications. Systems Development. PowerPoint. Functional, Crossfunctional & Interorganizational. Database Processing & Design.

449 views • 30 slides

Class Diagrams. TariffSchedule. Trip. Class diagrams represent the structure of the system. Class diagrams are used during requirements analysis to model problem domain concepts during system design to model subsystems and interfaces during object design to model classes.

291 views • 13 slides

Class diagrams

Class diagrams. Terézia Mézešová. Class diagram. static diagram, part of UML describing classes structure of system shows classes, their attributes and methods and relationships between classes classes represent main interactions in system and classes to be programmed. Classes. name

331 views • 12 slides

Lab 7 – Access Data Entry and Queries

Lab 7 – Access Data Entry and Queries. MBAC 611. Lab 7 Preparation. Click on the My Computer Icon Open your private network directory Create a new folder named lab7 Copy your lab6 Access file to the lab7 folder Rename the copied lab6 Access file to lab7

414 views • 27 slides

Voyager Statistics: the Conspectus Queries

Voyager Statistics: the Conspectus Queries. Cathy Salika. Conspectus. A tool for collection analysis To evaluate one’s own collection To compare collections to other libraries To compare collections to standard bibliographies Developed by RLG in the 1980s. Conspectus.

216 views • 13 slides

Access Queries

Access Queries. Queries. Most common type of Query is selection(projection) Specify sources for data retrieval table(s) and/or query( ies ) Specify attributes(fields) to be retrieved Selection criteria Calculations that need to be performed Action Queries Other types such as crosstabs.

3.74k views • 53 slides

Access Queries. Agenda 6/17/13 Review quiz, answer questions Create relationships through “Lookup tables ” Discuss queries: Turning data stored in a database into information for decision making. Highlight key issues about queries

457 views • 20 slides

Class Diagrams. Perspectives. Conceptual classes represent concepts in a domain software (& language) independent Specification classes represent interfaces (or types) Implementation full classes automatic code generation. Interface vs Implementation.

287 views • 17 slides

Using Data Dictionary and Dynamic Performance Views

Using Data Dictionary and Dynamic Performance Views. Objectives. After completing this lesson, you should be able to do the following: Identify built-in database objects Identify the contents and uses of the data dictionary Understand how data dictionary views are created

490 views • 15 slides

Using Data Dictionary and Dynamic Performance Views. Objectives. After completing this lesson, you should be able to do the following: Identify built-in database objects Identify the contents and uses of the data dictionary Describe how data dictionary views are created

342 views • 16 slides

Access Queries. Office 2013/365. Queries. Most common type of Query is selection(projection) Specify sources for data retrieval table(s) and/or query( ies ) Specify attributes(fields) to be retrieved Selection criteria Calculations that need to be performed Action Queries

626 views • 38 slides

Access Queries. Agenda 2/24/14 Review quiz, answer questions Create relationships through “Lookup tables ” Discuss queries: Turning data stored in a database into information for decision making. Highlight key issues about queries

429 views • 19 slides

Class Diagrams. Overview. Class diagrams are the most commonly used diagrams in UML. Class diagrams are for visualizing, specifying and documenting the system from a static perspective.

442 views • 28 slides

Using Queries in Access

Using Queries in Access. Applications for Qualitative Content Analysis. What is a Query?. Queries are “objects” in Access databases They provide flexible ways to VIEW data stored in tables manipulate data to make new tables append data from one table onto another. In a Relational Database.

413 views • 18 slides

Class Diagrams. CS 123/CS 231. Classes in a Class Diagram. Class name only Example With Details Example. Bank Account. Class Name. Bank Account double balance deposit() withdraw(). Class Name attributes methods. Relationships. Inheritance (arrow)

298 views • 15 slides

USING MICROSOFT ACCESS WITH RCRAINFO QUERIES AND REPORTS

USING MICROSOFT ACCESS WITH RCRAINFO QUERIES AND REPORTS. RCRAInfo National Users Conference August 1 - 5, 2005. USING MICROSOFT ACCESS WITH RCRAINFO WORKING WITH QUERIES REPORT BUILDING USING REPORT WIZARD. Prepared by: Buddy Jones USEPA, Region 6 (6PD-M) Dallas, TX 75202.

378 views • 37 slides

Enhancing ER Diagrams to View Data Transformations Computed with Queries

Enhancing ER Diagrams to View Data Transformations Computed with Queries. Disclaimer. Teaching Database Systems courses many years Database processing requires understanding data structure before processing But I have hardly worked on conceptual modeling or database modeling

130 views • 12 slides

167 views • 16 slides

• The Contents
• The Making of
• Where Are They Now
• Frequently Asked Questions
• Q & A with Ed Stone

golden record

Where are they now.

• frequently asked questions
• Q&A with Ed Stone

Mission Status

Instrument status.

Where are the Voyagers now?

To learn more about Voyager, zoom in and give the spacecraft a spin. View the full interactive experience at Eyes on the Solar System . Credit: NASA/JPL-Caltech

View Voyager

Space Flight Operations Schedule (SFOS)

SFOS files showing Voyager activity on Deep Space Network (DSN)

2024 Tracking Schedule

2023 tracking schedule, 2022 tracking schedule, 2021 tracking schedule, 2020 tracking schedule, 2019 tracking schedule, 2018 tracking schedule, 2017 tracking schedule, 2016 tracking schedule, 2015 tracking schedule, 2014 tracking schedule, 2013 tracking schedule, 2012 tracking schedule, 2011 tracking schedule, 2010 tracking schedule, 2009 tracking schedule, 2008 tracking schedule, 2007 tracking schedule, 2006 tracking schedule, 2005 tracking schedule, 2004 tracking schedule, 2003 tracking schedule, 2002 tracking schedule, 2001 tracking schedule, 2000 tracking schedule, 1999 tracking schedule, 1998 tracking schedule, 1997 tracking schedule, 1996 tracking schedule, 1995 tracking schedule, 1994 tracking schedule.

Connecting data. Empowering decisions.

Voyager delivers spatially enabled data registry and information retrieval solutions that help organizations unlock the full potential of their data.

We help users find the information they need to improve decision making, boost productivity, and increase cost efficiency.

Let Your Data Take Your Business to Higher Grounds

Quickly create an enterprise data catalog across all data types including structured, un-structured, geospatial and non-spatial data.

Use BI and AI/ML rules to automatically classify, condition and identify patterns across content.

Deploy in the Cloud, On-Prem, or Hybrid Environments

Our cloud, on-premises, and hybrid deployments offer organizations different options for hosting software and accessing data regardless of where your content is stored.

No Costly Data Migration

Save time and resources by not having to move data or retroactively engineer systems. We catalog data where it resides with simple read-only access.

No Custom Code Required

No-code deployments allow organizations to rapidly and easily create and deploy solutions without coding knowledge or expertise

Out of the Box User Interfaces and Industry Standard Open APIs

User interfaces and APIs allow faster insertion of new technology, easier integration with other systems, and lower life-cycle costs to improve productivity. 

Unprecedented Velocity. Impeccable Reliability.

Organizations increasingly struggle with the volume of data they store, which can often hinder productivity rather than enhance it. Information overload is a growing concern for knowledge workers, burdening IT resources and making it harder to find and work with critical information. Fortunately, our data cataloging and information retrieval solutions provide a powerful solution for navigating this reality, helping people quickly and efficiently find the information they need to make better decisions and conduct their work more productively

Spatially Enabled Information Retrieval

Leverage the power of geospatial technologies to provide more accurate and efficient information retrieval by discovering context and spatial relationships in your data

Some of our Partners

Are You Ready to Accelerate Your Business?

Discover how we can help you easily find and understand data across multiple sources, delivering end-to-end visibility and maximizing the value of your data. Put the trust back into your data today.

Navigation Menu

Search code, repositories, users, issues, pull requests..., provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications

Visualization Tool for Data Exploration

vega/voyager

Folders and files, repository files navigation.

Voyager 2 is a data exploration tool that blends manual and automated chart specification. Voyager 2 combines PoleStar, a traditional chart specification tool inspired by Tableau and Polaris (research project that led to the birth of Tableau), with two partial chart specification interfaces: (1) wildcards let users specify multiple charts in parallel,(2) related views suggest visualizations relevant to the currently specified chart. With Voyager 2, we aim to help analysts engage in both breadth-oriented exploration and depth-oriented question answering.

For a quick overview of Voyager, see our preview video , or a 4-minute demo in our Vega-Lite talk at OpenVisConf , or watch our research talk at CHI 2017 . For more information about our design, please read our CHI paper and other related papers ( 1 , 2 , 3 ).

Voyager 2 can be used from JupyterLab via the JupyterLab extension for Voyager . The DataVoyager.jl package integrates Voyager 2 into the Julia programming language .

This repository now hosts an alpha version of the migration of Voyager 2 to a React/Redux application. Older versions of Voyager built in AngularJS at the following URL.

• The Voyager 2 visualization tool, which blends manual and automated chart specification – demo at http://vega.github.io/voyager2 and source code at https://github.com/vega/voyager2
• The Voyager 1 visualization browser -- demo at http://uwdata.github.io/voyager and source code in the vy1 branch of this repository.

Documentation

You can find Voyager documentation on our GitBook .

This documentation is divided into several sections:

• Univariate Summaries
• Specify Visual Encodings
• Related Views
• Customizing Visualizations
• Bookmark Gallery
• Using Voyager in JupyterLab

Basic Setup

For basic setup for local development or installation, we use yarn for package management. Installing dependencies can be done with:

Once the installation is complete, use yarn test to run the included tests.

To build a deployable version of the code, run yarn build .

Please see our contributing documentation for more info about setup and coding conventions if you are interested in contributing to this project.

Build Outputs

There are 3 artifacts build using yarn build :

• Stand alone version of voyager in dist/ . This distribution can be hosted on a web server to deploy Voyager.
• Compiled Javscript and .d.js declaration files for a subset of the Voyager source code in build/src/ . These declarations and sources can be included in other packages that use Voyager as a dependency. See voyager-server for an example.
• Embeddable Voyager build in build/ . See below for more details on embedding Voyager in other applications.

Embed Voyager ( datavoyager library)

Voyager can be embedded in another web application. The following sections document how to use it.

Installation

Using npm or yarn? Add the following to your package.json then run npm install datavoyager or yarn add datavoyager .

If you want to use the latest development version, you may want to clone and link Voyager.

Example Use

Instantiation

Initializing with data

Updating Data

You currently also need to include the CSS. Note that this has not yet been optimized for embedding (it will take over the whole screen)

The voyager module exposes 1 function.

CreateVoyager(container, config, data)

Please see src/lib-voyager.tsx to see the exposed public methods.

For information regarding the config parameter, please see src/models/config.ts

The data parameter must follow the inline data format as seen in the vega lite documentation

Voyager-server Mode

Computationally expensive portions of the Voyager process can be configured to run on a server.

To get this running in a local development environment, first clone and install the dependencies of the voyager-server project.

In voyager-server directory, yarn start will start the server running on port 3000 .

With voyager-server now running, we can start voyager in server mode by running:

This will run Voyager in "server-mode" sending requests to voyager-server, which it expects, by default, to be at http://localhost:3000 .

The server url is controlled by the SERVER environment variable.

See voyager-server for more information on what portions of the functionality the server handles.

Code of conduct

Contributors 20.

• TypeScript 86.3%
• JavaScript 6.5%

• RELATED SITES
• Target/Planet
• Volume Series

QUICK LINKS

Instrument Host Overview ======================== For most Voyager experiments, data were collected by instruments on the spacecraft. Those data were then relayed via the telemetry system to stations of the NASA Deep Space Network (DSN) on Earth. Radio Science experiments (such as radio occultations) required that DSN hardware also participate in data acquisition. The following sections provide an overview first of the spacecraft and then of the DSN groundsystem as both supported Voyager science activities. Instrument Host Overview - Spacecraft ===================================== The Voyager 1 and Voyager 2 spacecraft were identical and were built by the Jet Propulsion Laboratory (JPL). With a mass of 815 kilograms, each carried its own power, propulsion, andcommunications systems and its own science instruments. Spacecraft electrical power was supplied by RadioisotopeThermoelectric Generators (RTGs) that produced about 400 watts. The Attitude and Articulation Control Subsystem (AACS), Computer Command Subsystem (CCS), and Flight Data Subsystem (FDS) managed spacecraft operations. Thrusters and gyrosprovided physical propulsion and attitude control. Communications between the spacecraft and Earth were carried out via a high-gain radio antenna using both S-band and X-bandfrequencies at data rates as high as 115.2 kilobits per second. A Digital Tape Recorder (DTR) could save up to 500 million bits when no Earth station was available for real-time data transmission. Voyager control systems could record sets of several thousand instructions, allowing autonomous operation for days or weeks at a time. More information on the spacecraft can be found in [MORRISON1982], [KOHLHASE1989], and[JPLPD618-128]. The spacecraft itself was built around its 'bus' -- a decagonal prism, which was about 2 meters in diameter and about 60 cm deep. Each of the ten sides of the bus was associated with a 'bay' containing engineering systems or science instrument electronics. Bay 1, for example, contained the radio transmitter. The High-Gain Antenna (HGA) was mounted to the end of the bus facing Earth. The bays were numbered 1 through 10 in a clockwise direction when viewed from Earth. Extending away from the bus were three booms: a science boom and scan platform to which most instruments were mounted, a magnetometer more ...

Engineers Diagnosing Voyager 2 Data System -- Update

Engineers successfully reset a computer onboard Voyager 2 that caused an unexpected data pattern shift, and the spacecraft resumed sending properly formatted science data back to Earth on Sunday, May 23

Updated May 24, 2010 at 5:30 p.m. PDT

Engineers successfully reset a computer onboard Voyager 2 that caused an unexpected data pattern shift, and the spacecraft resumed sending properly formatted science data back to Earth on Sunday, May 23. Mission managers at NASA's Jet Propulsion Laboratory in Pasadena, Calif., had been operating the spacecraft in engineering mode since May 6. They took this action as they traced the source of the pattern shift to the flip of a single bit in the flight data system computer that packages data to transmit back to Earth. In the next week, engineers will be checking the science data with Voyager team scientists to make sure instruments onboard the spacecraft are processing data correctly.

Updated May 20, 2010 at 6:00 p.m. PDT

Engineers have successfully corrected the memory on NASA's Voyager 2 spacecraft by resetting a computer bit that had flipped. Reset commands were beamed up to the spacecraft yesterday, Wed., May 19, and engineering data received today confirm that the reset was successful. The Voyager team will continue monitoring the engineering data, and if the bit remains reset, commands to switch to the science data mode will be beamed up to Voyager 2 on Sat., May 22. Receipt of science data would then resume on Sun., May 23.

Updated May 17, 2010 at 5:00 p.m. PDT

One flip of a bit in the memory of an onboard computer appears to have caused the change in the science data pattern returning from Voyager 2, engineers at NASA's Jet Propulsion Laboratory said Monday, May 17. A value in a single memory location was changed from a 0 to a 1.

On May 12, engineers received a full memory readout from the flight data system computer, which formats the data to send back to Earth. They isolated the one bit in the memory that had changed, and they recreated the effect on a computer at JPL. They found the effect agrees with data coming down from the spacecraft. They are planning to reset the bit to its normal state on Wednesday, May 19.

May 06, 2010

Engineers have shifted NASA's Voyager 2 spacecraft into a mode that transmits only spacecraft health and status data while they diagnose an unexpected change in the pattern of returning data. Preliminary engineering data received on May 1 show the spacecraft is basically healthy, and that the source of the issue is the flight data system, which is responsible for formatting the data to send back to Earth. The change in the data return pattern has prevented mission managers from decoding science data.

The first changes in the return of data packets from Voyager 2, which is near the edge of our solar system, appeared on April 22. Mission team members have been working to troubleshoot and resume the regular flow of science data. Because of a planned roll maneuver and moratorium on sending commands, engineers got their first chance to send commands to the spacecraft on April 30. It takes nearly 13 hours for signals to reach the spacecraft and nearly 13 hours for signals to come down to NASA's Deep Space Network on Earth.

Voyager 2 launched on August 20, 1977, about two weeks before its twin spacecraft, Voyager 1. The two spacecraft are the most distant human-made objects, out at the edge of the heliosphere, the bubble the sun creates around the solar system. Mission managers expect Voyager 1 to leave our solar system and enter interstellar space in the next five years or so, with Voyager 2 on track to enter interstellar space shortly afterward. Voyager 1 is in good health and performing normally.

"Voyager 2's initial mission was a four-year journey to Saturn, but it is still returning data 33 years later," said Ed Stone, Voyager project scientist at the California Institute of Technology in Pasadena. "It has already given us remarkable views of Uranus and Neptune, planets we had never seen close-up before. We will know soon what it will take for it to continue its epic journey of discovery."

The original goals for the two Voyager spacecraft were to explore Jupiter and Saturn.

As part of a mission extension, Voyager 2 also flew by Uranus in 1986 and Neptune in 1989, taking advantage of a once-in-176-year alignment to take a grand tour of the outer planets. Among its many findings, Voyager 2 discovered Neptune's Great Dark Spot and 450-meter-per-second (1,000-mph) winds. It also detected geysers erupting from the pinkish-hued nitrogen ice that forms the polar cap of Neptune's moon Triton. Working in concert with Voyager 1, it also helped discover actively erupting volcanoes on Jupiter's moon Io, and waves and kinks in Saturn's icy rings from the tugs of nearby moons.

Voyager 2 is about 13.8 billion kilometers, or 8.6 billion miles, from Earth. Voyager 1 is about 16.9 billion kilometers (10.5 billion miles) away from Earth.

The Voyagers were built by JPL, which continues to operate both spacecraft. Caltech manages JPL for NASA.

For more information about the Voyagers, visit: http://voyager.jpl.nasa.gov/ .

News Media Contact

Jia-Rui Cook

Jet Propulsion Laboratory, Pasadena, Calif.

818-354-0724

[email protected]

• Subscribe by RSS

Overview of Voyager Keyword Indexes

• Last updated
• Save as PDF
• Product: Voyager
• Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

Would like some help understanding Voyager Keyword Indexes.

An index is a pointer to data in a table. An index in a database is very similar to an index in the back of a book.  An index in a database works the same way as a book index in that a query is pointed to the exact physical location of data in a table. You are actually being directed to the data's location in an underlying file of the database.  This model of data management makes searching much more efficient and much faster.  But the indexes need to be kept current and correct.  If you add a new chapter to a book, the index needs to be updated as well.  The same thing is true of databases.

The Voyager keyword indexes are outside of Oracle for better performance.  They can be found in the /m1/voyager/xxxdb/data directory on the server (where xxxdb is the Voyager Database Instance).

The /m1/voyager/xxxdb/data/ directory contains two main types of files :

• bib_text.#.tdr
• bib_text.#.tdt
• xxxdb.#.bif
• dynamic.bif
• dynamic.que
• xxxdb.#.kil
• The static dc (dictionary) file is created at each regen and is indexed.
• The dynamic dc file is what changes between regens and is not indexed.  It is "searchable", though.  The larger it gets, the less efficient the searching.
• Bulk Import (including GDC) or Cat client writes new words to que via keysvr, keysvr checks the que periodically and COPIES new words to dynamic dc (new words are not searchable until they appear in the dictionary); once new words are copied to dc they are searchable via the keyword index.
• In Bulk Import and GDC when you opt to run new records through keyword index, the Dynamic file is updated and its size increases.  Eventually it will become so large that you will need a keyword regen .  If you do not run records through keyword index, the new records won't be added to the dynamic file and will not be searchable until you run a keyword regen .
• After a keyword regen the .dc and .kil files are not set to 0 bytes because they must contain internal structures.

The individual files in /data are described like this:

bib_text.?.tbt – TurboBibText - Contains the actual bib text bib_text.?.tdr - TurboDiRectory - Index to the bib_text.?.tbt file *.dc – DiCtionary words - The actual indexed words (static and dynamic files) and pointers to records *.bif – BinaryInfoFiles - Info for the matching .dc file. Links to dictionary, describes size and structure *.kil – KILl file - List of words that no longer exist in the database dynamic.que – QUEue file - Temporary list of words to be indexed awaiting access to dynamic dictionary file

The keyword index is made up of the static, dynamic and kill files, but only the first two are searched.

Size limits:

• The dynamic.dc file stops working at 2GB and from Voyager 9 on, no new records are indexed ( before Voyager 9 consequences were more severe).
• Static files are capped at 2GB.  Larger databases create more static files.
• Turbo text files generally are kept below 1.5GB. Larger databases create more turbo files.

The voyager.ini file on the server:

• The voyager.ini file found in /m1/voyager/xxxdb/ini is a server configuration file.
• It provides configuration settings for keyword indexes including port number specification and existence of multiple keyword index files.
• If configured incorrectly, it can cause problems with keyword searches.

Additional Information

Example of Keyword indexes in data/ for "UNKNOWDB":

-rw-rw-r-- 1 voyager exlibris    23812160 Apr   1 16:15 bib_text.1.tdr

-rw-rw-r-- 1 voyager exlibris 1629102566 Apr   1 16:15 bib_text.1.tbt

-rw-rw-r-- 1 voyager exlibris        1544 Feb 12 23:14 bib_text.2.tdr

-rw-rw-r-- 1 voyager exlibris           0 Feb 12 23:14 bib_text.2.tbt

-rw--w---- 1 voyager exlibris         264 Feb 12 23:15 unknowdb.1.bif

-rw--w---- 1 voyager exlibris         264 Feb 12 23:15 unknowdb.2.bif

-rw------- 1 voyager exlibris         264 Feb 12 23:15 unknowdb.3.bif

-rw------- 1 voyager exlibris         264 Feb 12 23:15 unknowdb.4.bif

-rw--w---- 1 voyager exlibris 1061131984 Feb 12 23:15 unknowdb.1.dc

-rw--w---- 1 voyager exlibris 1037491048 Feb 12 23:16 unknowdb.2.dc

-rw------- 1 voyager exlibris 1024779136 Feb 12 23:16 unknowdb.3.dc

-rw------- 1 voyager exlibris   432824496 Feb 12 23:16 unknowdb.4.dc

-rw------- 1 voyager exlibris       31604 Apr   1 16:15 unknow.db1.kil

-rw------- 1 voyager exlibris        7520 Apr   1 15:30 unknowdb.2.kil

-rw------- 1 voyager exlibris        8316 Apr   1 15:30 unknowdb.3.kil

-rw------- 1 voyager exlibris       12296 Apr   1 16:14 unknowdb.4.kil

-rw------- 1 voyager exlibris         144 Apr   1 16:15 dynamic.bif

-rw------- 1 voyager exlibris           2 Apr   1 16:15 dynamic.que

-rw--w---- 1 voyager exlibris   233009152 Apr   1 16:15 dynamic.dc

• Article last edited: 08-Jan-2020

• Cambridge Dictionary +Plus

Meaning of voyager in English

Your browser doesn't support HTML5 audio

• daily passenger
• day-tripper
• grief tourist
• super-commuter

Examples of voyager

Translations of voyager.

Get a quick, free translation!

Word of the Day

veterinary surgeon

formal for vet

Dead ringers and peas in pods (Talking about similarities, Part 2)

Learn more with +Plus

• Recent and Recommended {{#preferredDictionaries}} {{name}} {{/preferredDictionaries}}
• Definitions Clear explanations of natural written and spoken English English Learner’s Dictionary Essential British English Essential American English
• Grammar and thesaurus Usage explanations of natural written and spoken English Grammar Thesaurus
• Pronunciation British and American pronunciations with audio English Pronunciation
• English–Chinese (Simplified) Chinese (Simplified)–English
• English–Chinese (Traditional) Chinese (Traditional)–English
• English–Dutch Dutch–English
• English–French French–English
• English–German German–English
• English–Indonesian Indonesian–English
• English–Italian Italian–English
• English–Japanese Japanese–English
• English–Norwegian Norwegian–English
• English–Polish Polish–English
• English–Portuguese Portuguese–English
• English–Spanish Spanish–English
• English–Swedish Swedish–English
• Dictionary +Plus Word Lists
• English    Noun
• Translations
• All translations

Add voyager to one of your lists below, or create a new one.

{{message}}

Something went wrong.

There was a problem sending your report.

NASA’s Voyager 1 resumes sending data to Earth after 5 months

• Published: Apr. 23, 2024, 5:53 p.m.
• Ryan Mancini | [email protected]

In the depths of space, the spacecraft Voyager 1 continued sending usable data about the health and status of its onboard engineering systems back to Earth, according to a statement from NASA.

Voyager 1 , the most distant human-made object in existence, stopped sending readable science and engineering data back to Earth on Nov. 14, 2023, the statement released on Monday read. In March, the Voyager engineering team at NASA’s Jet Propulsion Laboratory in Pasadena, California, confirmed the problem was “tied to one of the spacecraft’s three onboard computers, called the flight data subsystem,” NASA said.

This subsystem is critical in packaging the science and engineering data before all the data goes back to Earth, the space agency continued. The team at JPL found that one chip responsible for storing part of the subsystem’s memory did not work, which rendered all of the data unusable and the code was too large to place in one new location.

More weather

• 7 Massachusetts counties under a frost advisory until early Saturday morning
• The current freeze warning will be expiring at 5 a.m.
• 9 Massachusetts counties under a freeze warning until early Friday morning
• Update: Freeze watch for 6 Massachusetts counties until early Friday morning
• Update: Freeze watch issued for 3 Massachusetts counties until early Friday morning

The team chose to “divide the affected code into sections and store those sections in different places in the” subsystem,” NASA said. On April 18, the team moved the spacecraft’s engineering data to a new location within the subsystem.

“A radio signal takes about 22 and a half hours to reach Voyager 1, which is over 15 billion miles (24 billion kilometers) from Earth, and another 22 and a half hours for a signal to come back to Earth,” NASA said in its statement. “When the mission flight team heard back from the spacecraft on April 20, they saw that the modification worked: For the first time in five months, they have been able to check the health and status of the spacecraft.”

In the weeks ahead, the team at JPL will relocate and adjust any other affected parts of the subsystem software, the agency said.

Voyager 1′s twin spacecraft, Voyager 2, continues to function normally, NASA said. Like its twin, Voyager 2 the only other spacecraft to fly into interstellar space. Both were launched in 1977.

Aboard both probes are phonograph records called The Golden Records that each carry time capsules “intended to communicate a story of our world to extraterrestrials,” according to NASA. Material placed on the records was chosen for NASA by a committee chaired by Carl Sagan .

If you purchase a product or register for an account through a link on our site, we may receive compensation. By using this site, you consent to our User Agreement and agree that your clicks, interactions, and personal information may be collected, recorded, and/or stored by us and social media and other third-party partners in accordance with our Privacy Policy.

NASA's Voyager 1 sends readable data back to Earth for 1st time in 5 months

After more than five months without contact, NASA has finally reconnected with Voyager 1, the farthest spacecraft from Earth.

NASA's Jet Propulsion Lab (JPL) said Voyager 1 had not been sending readable data back to Earth since Nov. 14, 2023, despite the spacecraft still receiving mission controller commands.

In December 2023, the JPL announced the problem was with one of Voyager 1's onboard computers called the flight data subsystem (FDS). Engineers attempted to restart the computer, but the problem persisted, NASA said.

However, the JPL announced this week that Voyager 1 had resumed sending engineering updates to Earth.

Engineers pinpointed the problem earlier this month, NASA said: A chip responsible for storing part of the computer's memory had become corrupted, making the data unreadable. The team was unable to repair the chip and decided the affected code needed to be stored elsewhere in the FDS memory, but no single location was large enough to do so, the JPL said in a release Monday.

The team "devised a plan to divide the affected code into sections and store those sections in different places in the FDS," the release read. "To make this plan work, they also needed to adjust those code sections to ensure, for example, that they all still function as a whole."

The code that packages Voyager 1's engineering data was the first to be sent to its new location on April 18. The JPL said it takes 22.5 hours for a radio signal to reach Voyager 1 and another 22.5 hours for the signal to come back to Earth. When the team heard from Voyager 1 on April 20, they knew the fix was a success, the JPL said.

"Hi, it's me. - V1," the X account for Voyager 1 posted on Monday afternoon.

Over the next few weeks, more portions of the FDS software will be relocated and the team will work to enable the spacecraft to begin returning science data again, the JPL said.

Voyager 1 was launched in September 1977 under the Voyager program to study the farther planets of the solar system and interstellar space. Voyager 1 entered interstellar space in 2012 becoming the first man-made object to exit the solar system.

Meanwhile, its twin spacecraft, Voyager 2, continues to "operate normally," according to the JPL. It reached interstellar space in 2018 and is the second-farthest spacecraft from Earth.