Event banner
Event details
- Roberto_Yglesias
Microsoft
There's already some great suggestions on this thread but a couple of other suggestions would be: - Create separate labels for each department so you can ensure you have flexibility for the future. - Use adaptive policy scopes to scope the labels publishing & auto-classification to the appropriate locations per department. - You likely need a person whose job it is to review disposition notices on files and coordinate with the file owners and take action to dispose of those records when appropriate.
- From my experience, we implemented a parent-child relationship style of labelling for a specific department. Take Engineering which has specific disciplines (e.g. Civil, Mechanical, etc.). So Engineering-Corporate would be the parent and the disciplines would be the children. Taking the concept of Content Type Hub or Data Dictionary, we ID'd labels or metadata that would be "common" to all of Engineering (i.e. Corporate, regardless of discipline). Then specific labels are ID'd for each discipline. Later, other considerations may come into play in terms of policies, procedures, change control, constraints and scope of implementation. Identification is a good but time-consuming initial step.
- Trainable classifications would be the method I'd go with to mark the records appropriately with the label associated. From that point, any new records should fall in the label category then you'll have policies, disposition and/or DLP actions assigned to said label.
Thanks Clarence. I have been trying to figure out how that would work but I keep coming up short. One reason is that our records are not consistent in form or content (throughout the ORG) in order to support trainable classifiers or syntax. We also don't classify information based on subject, we need to ensure the purpose is being identified not just the content.
The program areas need to easily retrieve their own information and receive unique disposition notices. i.e. Department of Economic Development Accounts Payable - not just Accounts Payable. We will also have different retentions for finance branches and the finance department for the same record type based on legislative requirements.
Would we need to create a unique set of labels for every department? That seems excessive and difficult to manage. Or maybe labels just won't work in this situation.
If I'm way off base here please weigh in. I'm very open to ideas. I've been trying to noodle this out for awhile.
