Sierra Nevada Network

1
Sierra Nevada Network File Directory Structure
(FDS) . yawn Pat Lineback GIS
Coordinator Sequoia and Kings Canyon National
Parks
2
(No Transcript)
3

• Sierra Nevada Network File Directory Structure
  (FDS)
• it has been a painful evolution.
• simplistic doesnt work very well complex may
  not work very well
• broader initiative to include other natural,
  fire, and research programs.
• where possible, all work should be completed
  on network. off network electronic files
  should be moved on network.
• heavy reliance on IT staffs for backup,
  archiving, and support services.
• other than some limited internal review, we have
  not implemented new FDS
• ignoring email

4

• Sierra Nevada Network File Directory Structure
  (FDS)
• include ALL electronic files in FDS
• includes file naming guidelines and standards
• decentralized Microsoft security centralized
  electronic files
• generally, electronic files should be as close
  to program source as possible.
• metadata should be close to their data files.
• generally, only one copy of an electronic file
  should be maintained on a network
• individual_work folders for electronic files
  that may not belong in a corporate data structure
• sensitive electronic files should be put in a
  sensitive folder close to its project source.

5
Electronic File Types

• Individual Project Work
• Analyses
• databases (spatial and nonspatial)
• Presentations
• publications (Internal versus External draft
  versus final)
• reports (Internal versus External draft versus
  final)
• protocols for doing something
• Conceptual Models
• Compliance Documents
• Help Files
• Guidelines (Internal versus External)
• Standards (Internal versus External)
• Policy (Internal versus External)
• Agreements
• Meetings (agendas, notes/minutes, supporting
  docs)
• Objectives
• references (Published and Unpublished technical
  versus general)

• Web Documents (HTML)
• Plans (small versus big/comprehensive)
• Presentations (Powerpoint)
• Imagery (Orthorectified or not,
• georeferenced or not, digital photos)
• Contracts
• Permits
• Correspondance
• Forms (data, administrative,
• Internal versus External)
• Conceptual Models
• Human Resource Files (SF -52,
• Evaluations, etc)
• Budget
• Travel
• Timekeeping
• Maps (PDF, jpeg, etc)
• Map projects (.mxd)
• Property

6
Electronic File Naming

• Electronic file names should generally be unique
• No Versioning
• Okay to user upper case when concatenating text
  strings
• No Spaces, special characters (except _ or
  .)
• Different draft naming standards
• - published articles, reports, or plans
• - unpublished documents such as worklogs,
  correspondance, proposals, specifications,
  plans, etc.
• - data
• - imagery (including photos)

7
Key ltRequiredgt Optional
8
(No Transcript)
9
(No Transcript)
10
(No Transcript)
11
(No Transcript)
12
(No Transcript)
13
(No Transcript)
14
For the other 99 of electronic files we are
creating . Records Management for the Masses
15

• Two issues for consideration
• Consider basic content services needs
• assessment
• Office worker focused
• Core library (electronic file) services
• Personal and shared electronic file storage
• Short and long-term file disposition
• Document routing
• File security
• Notifications
• Search and retrieval
• Compliant with NPS Records Management
• standards and guidelines

16

• Two issues for consideration
• Consider basic content services at some
• level (e.g. document library services)
• 2) File directory structure are part of the
  larger
• concept of Records Management

17
Records Management
18
DRAFT SIEN file directory structure and file
naming available through Chapter 11 Records
Management Appendices Use NPS Active Directory
Use NPS Active Directory login and password
http//165.83.70.31/SIEN/default.aspx
19
Imagine working here! SIEN Data Manager Vacancy