skip to content
Primary navigation

Opinion Library

To return to this list after selecting an opinion, click on the "View entire list" link above the opinion title.

Advisory Opinion 01-005

January 5, 2001; Minnesota State Colleges and Universities

1/5/2001 10:15:43 AM

This is an opinion of the Commissioner of Administration issued pursuant to section 13.072 of Minnesota Statutes, Chapter 13 - the Minnesota Government Data Practices Act. It is based on the facts and information available to the Commissioner as described below.


Facts and Procedural History:

For purposes of simplification, the information presented by the person who requested this opinion and the response from the government entity with which the person disagrees are presented in summary form. Copies of the complete submissions are on file at the offices of IPA and, except for any data classified as not public, are available for public access.

On November 1, 2000, the Commissioner received a letter dated October 31, 2000, from Christina Clark, attorney for Education Minnesota, on behalf of X. In her letter, Ms. Clark requested that the Commissioner issue an opinion regarding the possibility that Minnesota State Colleges and Universities (MnSCU) violated X's rights under Minnesota Statutes, Chapter 13. Subsequent to conversations with IPA staff, it was agreed that the Commissioner would address the issues listed below.

IPA, on behalf of the Commissioner, wrote to Morris Anderson, Chancellor of MnSCU, in response to Ms. Clark's request. The purposes of this letter, dated November 16, 2000, were to inform him of Ms. Clark's request and to ask him to provide information or support for MnSCU's position. On November 28, 2000, IPA received comments, dated November 27, 2000, from Kristine Legler Kaplan, Assistant Minnesota Attorney General.

A summary of the facts as presented by Ms. Clark is as follows. On January 4, 2000, X made a request to Northwest Technical College (part of MnSCU), This letter is follow-up to the message that I sent via Email yesterday regarding my request and permission that a complete copy of my personnel file be sent to John DeSantis [union staff]....Please include all additional personnel information regarding me that may be filed in other files in your office....I would also like to request a complete copy for my records as well.

In a letter dated January 13, 2000, MnSCU staff sent data to Mr. DeSantis. Staff wrote, Enclosed you will find copies of [X's] various files that we have.

In her opinion request, Ms. Clark wrote, On February 22, 2000, upon a further request, the employer furnished copies of six documents which the originally provided personnel file did not contain. Ms. Clark provided the Commissioner with a copy of MnSCU's letter that accompanied the data. MnSCU staff wrote, Enclosed please find additional information provided in response to [X's] January 4, 2000, data request. This information is maintained in Dean [X's] supervisory file.

Of the six documents, Ms. Clark advised the Commissioner that MnSCU had redacted four. Ms. Clark also related that MnSCU staff advised her only that the items that are crossed out do not pertain to [X] and as such have been properly redacted. Ms. Clark contended that MnSCU should have provided a statutory citation relating to the redacted data.


Issues:

In her request for an opinion, Ms. Clark asked the Commissioner to address the following issues:

  1. Did MnSCU respond appropriately to a data subject's January 4, 2000, request for data within the time frame set forth in Minnesota Statutes, section 13.04?
  2. Was MnSCU's February 22, 2000, response to a data subject's January 4, 2000, request for data appropriate?


Discussion:

Issue 1

Did MnSCU respond appropriately to a data subject's January 4, 2000, request for data within the time frame set forth in Minnesota Statutes, section 13.04?

In a January 4, 2000, letter, X asked for a copy of his/her complete personnel file, adding that s/he wanted all additional personnel information regarding me that may be filed in other files in your office. In this letter, X wrote that s/he gave permission for MnSCU to provide a copy of this information to X's representative. MnSCU's January 13, 2000, response was within the statutorily-mandated time frame. However, MnSCU then forwarded additional data on February 22, 2000.

In her comments to the Commissioner, Ms. Kaplan related that the data MnSCU provided on January 13 were the official' personnel file, as defined in the Collective Bargaining Agreement at Article 24, Section 1, and as requested, other miscellaneous files maintained by the Human Resources Department. She added, The College did not include all personnel data that existed on X,' including a supervisor's file maintained by Dean Y' that was not part of the official' personnel file under the Collective Bargaining Agreement. Ms. Kaplan also wrote, The facts...present a threshold issue on the extent to which [Chapter 13] or the Collective Bargaining Agreement controls the access to information. She then argued, There is nothing in the January 4 request that reasonably puts MnSCU on notice that it was intended to be a comprehensive request under [Chapter 13] for all personnel information about X' in any location.

In this case, the issue is whether MnSCU's February 22 response was timely. Ms. Kaplan argued that the February 22 response contained data that were maintained in a supervisory file as opposed to a personnel file. The Commissioner opines that this is irrelevant. As stated above, section 13.04 requires government entities to respond to data subjects' requests within ten days. Chapter 13 does not provide for a different response time when data requestors are covered by collective bargaining agreements. From the Commissioner's perspective, X's request seems clear; a copy of his/her complete personnel file as well as all additional personnel information regarding me that may be filed in other files in your office. If MnSCU was confused about X's request, someone should have obtained clarification from X within the ten day period. Therefore, it is the Commissioner's opinion that MnSCU's response to X was not timely.

Issue 2

Was MnSCU's February 22, 2000, response to a data subject's January 4, 2000, request for data appropriate?

In her opinion request, Ms. Clark argued that four of the six documents MnSCU provided to X on February 22 were improperly redacted. She added, According to Minn. Stat. section 13.03, upon the employee's request the employer must cite the specific statutory section, temporary classification, or specific provision of federal law upon which the denial was based.

In her comments, Ms. Kaplan wrote that MnSCU redacted some data pursuant to section 13.43, subdivision 6. The Commissioner does not agree that MnSCU can use this section as a basis upon which to deny access to data. Section 13.43, subdivision 6, sets forth the situations in which an entity may provide data to labor organizations when the entity does not have consent from the data subject to share the data. In the case at hand, it appears that X gave MnSCU his/her permission to share the data with X's labor representative.

Ms. Kaplan wrote also that the redactions were appropriate for other reasons. Regarding one document, a letter from students whose signatures MnSCU redacted, she cited section 13.32 and federal law stating that the identities of the students are private data. Regarding the other three documents, she cited section 13.43, stating that the redactions consisted of identities and other private personnel data about other employees who were commenting about X's work. Ms. Kaplan added, MnSCU acknowledges that it should have provided the statutory citations justifying the redactions...

The Commissioner has reviewed the four documents and has the following comments. The letter from the students expresses their concerns about X as their instructor. Although MnSCU redacted the students' signatures, MnSCU did not redact the names of the classes those students attend. Most data about students are private pursuant to Minnesota Statutes, section 13.32, subdivision 3. Given the subject matter of the letter and the context under which the letter was created, it seems appropriate that MnSCU redacted the students' names.

Ms. Kaplan asserted that the data redacted from the remaining three documents was done so pursuant to section 13.43, personnel data. Subdivision 2 of section 13.43 lists the types of data about employees that are public and subdivision 4 classifies most other types as private. In this case, because the Commissioner has not seen the unredacted documents and does not know the specifics of the situation involving X's issues with Northwest Technical College, he is not in a position to determine, with certainty, whether MnSCU's redactions are appropriate.

Finally, the Commissioner agrees with Ms. Kaplan that when MnSCU refused to disclose some of the data to X (by redaction), MnSCU should have provided X with the statutory citations upon which it relied to deny access to the data. See section 13.03, subdivision 3.


Opinion:

Based on the facts and information provided, my opinion on the issues that Ms. Clark is as follows:

  1. MnSCU did not respond appropriately to a data subject's January 4, 2000, request for data within the time frame set forth in Minnesota Statutes, section 13.04.
  2. Pursuant to Minnesota Statutes, section 13.03, in its February 22, 2000, response, MnSCU should have provided X with the statutory citations upon which MnSCU denied X access to data. It was not appropriate for MnSCU to withhold data from X pursuant to section 13.43, subdivision 6. It appears MnSCU appropriately withheld student names pursuant to section 13.32. The Commissioner is unable to determine whether MnSCU appropriately withheld data from X pursuant to section 13.43.

Signed:

Kirsten Cecil
Deputy Commissioner

Dated: January 5, 2001


Personnel data

Redaction

Requests for data

Collective bargaining agreements

Educational data, included (See also: Educational data - Personnel data)

Labor/union access (13.43, subd. 6)

Multiple data subjects

Redaction (See also: Multiple data subjects; Separation of data)

Entity responsibility

back to top