I absolutely agree that `modelOrCollectionName` is unwieldy. I chose it for consistency with `modelOrCollection`, a variable which is used in the fetcher and view engine, but I agree that `resourceName` is better.

I think that this is just a naming issue, though, and not a problem of trying to do two things in one method. This method takes a constructor and returns its underscorized id. I see that as one task with multiple applications.