A framework for thinking about mechanisms

Range of possible implementation mechanismsSome criteria for assessing various mechanismsHolding tank descriptionApplying criteria for assessment to the holding tank (2 slides)

Possible Mechanisms for Improving Quality by Resource Lifecycle

More focused selection criteria: from filter to guidelinesCo-development of collections with user communitiesDevelopment of thematic collections; responsibility, ownership, persistencePre-cataloging review of ‘gray’ casesEncapsulation of context at design times: wrap questionable in content guiding useQA of resources in Broad CollectionReview board for marginal casesHolding TankAnnotation services / Peer reviewingDe-accessioning request form

Some Criteria for Assessing Mechanisms (in random order)

Technical implementationSocial implementation

Community Participation: opportunities for versus required to be successful

Cataloging and QA CostMaintenance CostScalabilityPreserving annotations during harvestingProactively supports collection developmentHelps to create a collection that follows the selection criteria

Holding Tank Description

Post-catalogingProvisional accessioning (30 days)

What’s new areaAvailable, but flagged, in discovery

No comments – automatic ingestionComments – someone has to review and pass a verdict

Applying Criteria to Holding Tank

Technical ImplementationBasic technical substrate is being implemented to support “what’s new” in CRS

Social ImplementationIssues with asking collections (including NSDL- funded collections) to internalize DLESE rejections to support reharvestingHow are holding tank reviewers mobilized to respond to new resources

• Registration• Commenting

How are comments assessed and by whom?

Applying Criteria to Holding Tank (part 2)

Full cataloging and QA efforts invested in resources that are ultimately rejectedMaintenance cost for 30 day holding period (e.g. applying link checking)Scalability: O(n) depends on applying to all collections vs. community collectionProvisional items unavailable for harvestingNo explicit support for building collectionsDepends on the successful implementation of the mechanisms