Previous Topic: Avoid Using Subsetting to Delete ObjectsNext Topic: Use Expansion Conflict Report before Subset Checkout


Avoid Long Check Out Times of Subsets

Subsets checked out for a long time can cause downgrades for other subset downloads. Downgrades usually result in consecutive overrides and downloads. This cycle degrades the overall throughput of the encyclopedia. In the development phase of an application, the subsets tend to be checked out for a long time. This may not cause many downgrades for other developers since subsets are usually mutually exclusive at this stage. However, in the maintenance phase of an application, the subsets must be scoped for the current task and must have a quicker download and upload turnaround time as compared with the development phase.

Business Value

Avoiding long checkout times improves throughput of the encyclopedia, increases user productivity, and reduces system costs.

Additional Considerations

Examining the cause of each downgrade is a good starting point in determining the maximum duration that a subset can stay checked out for each project and its implementation phases. Alternatively, a report of subsets that have been checked out for more than one week can be brought to project teams’ attention regularly. Some Gen sites are known to override all subsets checked out for more than one week to enforce frequent check-ins.