Dear list members,

I wonder if you could clarify something that I have been discussing with my colleagues.

We have been discussing the implementation of an EDRMS based upon LGCS and the practicalities of initiating the rules that surround the schema.

Imagine you have an area in the LGCS where you want to implement an expiration rule e.g. LGCS ID3 - Adult Care Services > Carers>Agency Provided Services>Destroy 25 years after end of employment

I have argued that given there are 1039 entries in the LGCS schema it may be impractical to expect records managers to input each of these rules into an EDRMS.

I also argued that each node in the LGCS schema may need its own bespoke metadata to capture the correct rule –

So in the example above you would need a metadata field to capture 'end of employment' and then add 25 years to calculate the expiration date.

Given that given there are 1039 nodes in the schema and that each one may need its own set of metadata,  it may be simply too time consuming and expensive to setup all of these rules in an EDRMS.

My argument is that records managers may set rules at a higher level e.g. Adult Care Services>25 years after record creation

Could you possibly provide me with some advice/guidance as to what is common practice/experience when setting up these rules in an EDRMS and if you manage your records down to this level of granularity?

Many thanks

David Nixon