Work with project/technical staff to identify gaps and develop overall requirements

• Beginning with your existing policy structure, determine the following:

• Is data viewed as a strategic resource?

• What are your data access and use policies, and how are they determined?

• Which data will you keep in the directory, why, and for how long? Will you delete entries? What types of services will you use it for?

• What are the guiding principles for your directory?

• Who are your data stewards for your systems of record? Typically, the data steward for the system of record is the same one for corresponding attributes in the directory.

• Who should be the data steward for information where the directory is the system of record? Will there be any data that fit this category? Why or why not?

• Who can create, read, update, and delete the data in the directory? Is IT a steward for any new information such as e-mail addresses or UNIX UIDS?

Can a developer access non-public directory data? If so, what is the approval process to do so? How do you get in touch with the developer in the future, if the data policies change?

Determine policy approval mechanism
If you believe that a number of policy/procedure changes will be needed to support the directory, determine what you can do to streamline the approval process. Some campuses have set up a group to review and approve these as the project progresses. See the introductory section of the Project Planning, Preparation & Requirements section for how to structure your project to support this.

 

Bookmark & Print Version • Graphic Version