|
| |
NASIS 6.1 Frequently Asked Questions
What are the major changes?
NASIS accounts
How do I start NASIS
6.1?
Checking out data
Editing the selected set
Re-initializing NASIS local database
Table functionality
Pedon
AnalysisPC
Reports and queries
Support
What are the major changes?
- Client – Server system –
The client version of the NASIS
6.1 software and a “local” database reside on your PC, and the
central server NASIS
6.1 software and National Database reside in Kansas City. You will query
the National Database and download a piece of the database to your PC. All processing is on the
local PC. Queries and reports can be run on either the local or National Database.
- Addition of the Mapunit object –
The map unit is no longer directly dependent upon the Legend. The map unit is now linked to a
legend thus allowing the MLRA Concept to thrive – allowing one MLRA mapunit to be linked to
multiple legends. The linkage between the Legend and Mapunit tables is through a new Legend Mapunit
table.
- Addition of the National Mapunit Symbol –
The new National Mapunit Symbol is automatically assigned to the map unit. The symbol is created
each time a new row is inserted into the Mapunit table. The new record identification (Rec ID)
number for that row is automatically converted to a base31 alpha-numeric symbol. This label cannot
be edited.
- The Local Plant table –
The local plant table will be managed as a national list instead of 18 individual MO lists. A unique
constraint will be imposed on the combination of Local Common Name and National Plant Symbol. A child
table to the Local Plant table called Local Plant Area Occurrence will be added. Records listed in
this table will reference area types and area names from the Area Type and Area tables respectively
to indicate areas (states) using a particular local plant name. Local plant symbols and local
scientific names have been discontinued. National equivalents will be used.
- Addition of the Project object –
The Project object will be used to manage soil survey projects, whether initial or update,
which will include scheduling and progress reporting. Map units can be associated with a project
regardless of the legend that they were originally in.
- Addition of the Technical Soil Services (TSS) object
–
The TSS object will provide the ability to track the scheduling and reporting of TSS activities.
NASIS accounts
The following instructions explain who may have a NASIS account and the
process for establishing a NASIS account.
Who may have a NASIS account?
The Natural Resources Conservation Service (NRCS) is the lead agency
for the National Cooperative Soil Survey (NCSS) (7 CFR 2.61). In its
leadership role, NRCS maintains National Soil Information System (NASIS)
for the collection, management, and distribution of NCSS information.
Access to NASIS is granted to NCSS partners and authorized agents for
the purpose of creating, maintaining, or interpreting NCSS information.
NASIS is a United States Government computing system. Only official NCSS
activities are authorized and permitted on this system.
Access to official NCSS data is available on the Soil Data Mart
(http://soildatamart.nrcs.usda.gov) and does not require a NASIS
account.
How do you request a NASIS account?
Requests to become a NASIS user should be submitted to a “sponsor”
who then submits the request to the Soils Hotline. The “sponsor” at the
state level or below is the State Soil Scientist. State Soil Scientist
contact information is available at (http://soils.usda.gov/contact/state_offices/).
The Soils Hotline will sponsor employees at the national headquarters
and centers. Cooperators that need access to NASIS are to be sponsored
by their local state soil scientist.
What does a user need to do to become a NASIS user?
- Obtain a Level 2 eAuthentication account via the eAuthentication
web site at
http://www.eauth.egov.usda.gov/eauthCreateAccount.html.
If you previously logged on to
NASIS 5.x using Citrix, you already
have an eAuthentication account which will work with
NASIS
6.1. If you
previously logged on to
NASIS 5.x using
NASIS Secure Access and you have
a level 2 eAuthentication account, then you need to e-mail your
eAuthentication login (no passwords, please) to
SoilsHotline@lin.usda.gov.
Tell them you are already a
NASIS user and that you need to be granted
access via eAuthentication. If you don’t have an eAuthentication
account, follow the instructions to create Level 2 Access at:
http://www.eauth.egov.usda.gov/eauthCreateAccount.html.
You may contact the Soils Hotline staff for assistance.
- Submit your request for a
NASIS account to the appropriate
sponsor. Refer to the section above “How do you request a
NASIS
account?” Include in your request, your full name, phone number, and
eAuthentication login.
What does the sponsor do to request a NASIS account for a user?
E-mail requests for new NASIS user accounts to the
SoilsHotline@lin.usda.gov.
Include the user’s full name, phone number and eAuthentication login.
Please specify in the e-mail if the user is an existing NASIS user but
needs to be granted eAuthentication access.
What does the Soils Hotline do when a NASIS account is requested?
- Check NASIS to see if a
NASIS user account already exists for the
user.
- Create a NASIS user record in
NASIS.
- Grant eAuthentication access to
NASIS.
- Notify the user and/or the sponsor that the account has been
created.
- Users can have read-only access to
NASIS which allows the user to
run existing reports and queries and view data, or the user can be
granted permission to edit data. If the user needs to enter or edit data
in NASIS, the user will need to contact the appropriate
NRCS State Soil
Scientist to request permission.
Roles and Responsibilities
NASIS User:
- ensure security of NASIS data by not sharing
NASIS logins
- notify NASIS Site Dataset Manager when membership in a
NASIS group is
no longer needed
- notify NASIS Site Dataset Manager when a
NASIS account is no longer
needed or when a NASIS account needs modification
(i.e., name change)
- NASIS contains information that may be protected under various laws,
regulations, treaties, and agreements (25 USC 450 related to the Indian
Self Determination and Education Assistance Act, 42 USC 1996 related to
the American Indian Religious Freedom Act, DR 1340-6 related to Policies
on American Indians and Alaskan Natives, 5 USC 552 related to the
Freedom of Information Act, and others).
NASIS users must not release
protected information to individuals or the general public without
specific authority to do so.
Soils Application “Sponsor”:
- verify users requesting
NASIS accounts are
NCSS members or person
working on behalf of NCSS
- submit e-mail to the Soils Hotline requesting a new
NASIS user
account, or requesting eAuthentication access for an existing
NASIS user
account
- notify Soils Hotline when a user no longer needs a
NASIS account or
when a NASIS
account needs modification (i.e., name change)
NASIS Site Dataset Manager:
- maintain members of the
NASIS groups within
NASIS. Remove users from
NASIS groups when the user no longer needs edit privileges on data owned
by that group
- notify Soils Hotline when a user no longer needs a
NASIS account or
when a NASIS account needs modification i.e., name change.
Soils Hotline:
- create NASIS accounts in a timely manner
- edit NASIS user table; set e-mail to null and phone number to
“OBSOLETE” when NASIS user account is no longer needed
- remove user from role in eAuthentication system
How do I start NASIS
6.1?
- Begin at the Start, All Programs, USDA Applications, Soils, NASIS.
- The first time NASIS
6.1 is started, the database will initialize with the National Database.
Why do I need to run a query against the “National Database” and then run a query against the
“Local Database”?
Answer: The Local Database must be populated with data. The data is retrieved from the National Database.
How do I populate the Local Database?
- Identify a suitable query in the queries object in the Explorer panel.
- Select “Run Query Against National Database” – this is the icon with the blue triangle and the globe. It can be found in the Queries Explorer Menu or the Queries Explorer toolbar. You can also right-click on the query name and pick this option.
- Only one Target Table can be selected when running a query against the National Database. It is best to choose the highest table in the database structure. All related objects are automatically included in the download.
- Once the National Database has been successfully queried and “Accepted”, “Run Query Against Local Database” to populate a selected set, similar to previous versions of NASIS.
Why don't I see the data I edited yesterday?
Answer: The data should be available unless you have deleted the data or cleared the Local Database. If the data does not exist in your selected set, then run a query on the Local Database to retrieve the data.
How often should I synchronize with the “National Database”?
Answer: Get into the habit of “refreshing” (NASIS, Refresh Local Database) the database each time you start NASIS.
Why can't I get the data I want loaded in to my selected set?
Answer: This could be a lack of understanding the query that is being used. Review the query and select the appropriate target table or choose a new query.
Checking out data
I created a record yesterday and chose to “Upload all changes to National Database”. Do I
have to check out the data?
Answer: No, a record you created will remain checked out to you until you check it in.
Upload does not check data in.
How do I “check-out” data?
- Load data into the selected set, highlight a record(s) then from the Editor menu,
choose “Check Out Selected Trees” . A “Tree” is the parent record and its child records.
- Run a query against the Local Database and check the “Check Out” box next to the parameters.
This checks out everything selected by the query, provided you have permission to edit it.
Editing the Selected Set
- How do I edit data?
- Highlight the record to be edited
- From the Table Editor menu, Check out the record
- Perform edits
- From the NASIS menu, choose “Upload All Changes to National Database”
- “Check In Selected Trees” or “Check In All”
- Why can’t I edit data?
- Is the record locked?
- Do you have edit permissions for the record? If so,
- Have you checked out the record?
- Why doesn’t the Find and Replace (global assign) on a cell paste to
all of the items in the selected set?
- Is the record locked?
- Do you have edit permissions for the record? If so,
- Have you checked out the record?
- Is “saving” data the same as “uploading” data?
No, “saving”
means storing the data in the Local Database. Uploading sends the changes to the National Database.
“Saving” is only required with multi-page forms like queries or reports.
When editing in a table, changes are saved to the Local Database as soon
as the cursor leaves the row.
- Is “uploading” data the same as “checking-in” data?
- No, the system is designed for you to identify the record(s) to be
edited.
- Once identified, the record is “Checked out”.
- The edit is made.
- Then “Upload All Changes to National Database”.
- And if no further editing is to be completed, the record is then
“checked in”.
- How long can data be “checked-out”?
- The system does not impose a time limit. However, to facilitate
access to the data by other users, the data should only remain “checked
out” for as long as needed for the editing to be accomplished. Once the
edit is made, the changes are “Upload All Changes to National Database”
and then the record is “Checked In”.
- There is a method to administratively release locks on the data for
cases where data has been checked out for an unduly long period of time.
This will be accomplished by the Soils Hotline staff.
- How often should I “save” (Upload All Changes to National Database)?
Refer to item 4 above. Edits should be “Upload All Changes to the
National Database” during the course of editing data. There is an
advantage of uploading data after an edit. The “Discard Changes” option
will discard changes back to the last upload to the National Database.
If during the course of many edits there is an edit that you wish not to
commit, that work can be discarded back to the last upload to the
National Database. Periodic uploads of changes can occur without
“checking in” the data record.
- How can I discard changes without saving?
- The ability to “Discard changes” is available in the NASIS menu
(Discard All Changes) , the Explorer Menu (Discard Changes), the Editor
Menu (Discard Changes) and their toolbars.
- The NASIS menu option allows the user to discard all changes made
since each changed object was last checked out, had changes uploaded to
the National Database or had the changes discarded.
- The discard changes on the Explorer and Editor menus allows the user
to discard changes for the specific data object currently highlighted in
the appropriate panel since the last time the record was last checked
out, had its changes uploaded or had its changes discarded. Discard
Changes applies to a whole object; for example if you want to discard
changes in a Component, it will discard all changes to the Data Mapunit
that contains the Component.
Re-initializing NASIS local database
You should only do this when you have been instructed to do so by a
NASIS team member. Please contact the Soils Hotline if you have questions.
Save and check-in all edits prior to initializing!
- Close all NASIS sessions.
- Click on Start | Run
- Type in cmd, click OK button
- In command prompt window, type c: and press enter key to change to C: drive
- Change directories by typing: cd c:\program files\USDA\NASIS 6.1.1 Client\
- Press enter key
- Type: nasiseditor.exe /rebuild (Note: There is a blank space
after .exe and before /rebuild)
- Press enter key
- As soon as NASIS initialization is
complete and NASIS starts up, click
NASIS | Refresh local database.
- The initialization process removes anything you previously had in your local database. You must
re-populate your local database by running queries against the National Database
to get your desired data back into your local database.
The initialization process usually takes about one half hour but can take up to
four hours if the network connection is slow.
Table functionality
- Can I clear all “filters” at once?
Answer: Yes, in the lower left corner of the Editor Panel inside the Table Grid
- Can we still create our own “Edit Setup”?
Answer: Yes, in NASIS
6.1 the Edit Setup is now called a “Manage Table Layouts”.
Tables are modified in the Editor Panel. The columns are sorted, sized, hidden or frozen based on the
user’s needs. The Layout is then saved using the “Manage Table Layouts” option on the NASIS Menu or use
the toolbar icon
Pedon
- How do import data from Pedon PC or windows pedon?
- Choose the NASIS menu, then “Import Pedons”, or select the icon on the NASIS toolbar.
- Review and/or edit pedons
- Choose the NASIS menu and “Upload All Changes to National Database”
- Can I make edits to pedons in Pedon PC then upload the changes into NASIS
- Yes, however it may be easier to make edits in NASIS
6.1
AnalysisPC
I ran the report "PEDON - AnalysisPC uncoded DataDump with support data" on my local database successfully but get errors when I try to import the data into AnalysisPC database.
Remove the blank lines at the end of the text file before importing into AnalysisPC
Reports and queries
A report or query I was using during NASIS 5.4 is not working; how do I fix it?
- Adding the table “lmapunit” to the FROM and JOIN statements maybe the quick fix to a simple report or query.
- Outer joins don’t work the same way as they did in the Informix database. There is an explanation in the CVIR Language Manual.
- The GROUP BY and ORDER BY clauses do not allow column numbers or aliases as they did in Informix. You have to use a column name or expression.
- The SUBSTRING function must be used in queries instead of the [n:m] form used in Informix.
Support
- Is there a “forum” for NASIS
6.1 questions?
- From the Help menu, users now have the ability to send an e-mail to the
Soils Hotline to obtain an answer to a question they may have.
- Click here for more NASIS documentation.
- My office has one computer that is shared by all staff. Can we run NASIS
6.1?
Yes, however as a shared computer the Local Database must contain all data used by the individual users – all users will be using the same Local Database. Users must “check in” all data before logging off since the possibility of locking others is greater.
- My system seems to be running slow. What can I do to fix this?
SQL Express is a memory hog. When the system runs slow it is a build up of RAM that SQL Express is using but not releasing. The best “fix” is to get in the habit of restarting your computer each night. Doing so releases the RAM and improves the performance of the computer. A minimum of 2 GB of RAM is necessary to run NASIS
6.1 efficiently.
- What does “Keep Detailed Error Information” (on the Help menu) do?
Detailed error information helps the NASIS development team diagnose problems with NASIS. If you have a problem and contact the
Soils Hotline about it, you may be asked to turn on detailed error information and try to reproduce the problem. After that you can send in the detailed information using the
“Send Error Log to Hotline” option on the Help menu. Normally you should leave
“Keep Detailed Error Information” switched off because it will slow down the performance of NASIS a little.
| |
|