Issue #367
closedReferences to old collection names and content_unit_count needs to be updated in API docs
Description
Content_unit_count is now a dictionary and is renamed to content_unit_counts. It should be updated in the examples of our rest API docs.
$ grep -r "content_unit_count" rest-api/*
rest-api/repo/retrieval.rst: "content_unit_count": 0,
rest-api/repo/retrieval.rst: "content_unit_count": 0,
rest-api/repo/retrieval.rst: "content_unit_count": 0,
rest-api/repo/retrieval.rst: "content_unit_count": 0,
rest-api/repo/cud.rst: "content_unit_counts": {},
rest-api/repo/cud.rst: "content_unit_counts": {},
There are also a lot of references to old collection names "gc_repo_importers", "gc_repos" etc.
$ grep -r "gc_" rest-api/*
rest-api/consumer/retrieval.rst: "_ns": "gc_consumers",
rest-api/consumer/retrieval.rst: "_ns": "gc_consumers",
rest-api/consumer/retrieval.rst: "_ns": "gc_consumers",
rest-api/consumer/retrieval.rst: "_ns": "gc_consumers",
rest-api/consumer/retrieval.rst: "_ns": "gc_consumers",
rest-api/consumer/retrieval.rst: "_ns": "gc_consumers",
rest-api/consumer/retrieval.rst: "_ns": "gc_consumers",
rest-api/consumer/history.rst: "_ns": "gc_consumer_history",
rest-api/consumer/history.rst: "_ns": "gc_consumer_history",
rest-api/consumer/cud.rst: "_ns": "gc_consumers",
rest-api/consumer/cud.rst: "_ns": "gc_consumers",
rest-api/repo/retrieval.rst: "_ns": "gc_repo_distributors",
rest-api/repo/retrieval.rst: "_ns": "gc_repo_importers",
rest-api/repo/retrieval.rst: "_ns": "gc_repo_distributors",
rest-api/repo/retrieval.rst: "_ns": "gc_repo_importers",
rest-api/repo/retrieval.rst: "_ns": "gc_repo_distributors",
rest-api/repo/retrieval.rst: "_ns": "gc_repo_importers",
rest-api/repo/retrieval.rst: "_ns": "gc_repo_distributors",
rest-api/repo/retrieval.rst: "_ns": "gc_repo_importers",
rest-api/repo/retrieval.rst: "_ns": "gc_repo_importers",
rest-api/repo/retrieval.rst: "_ns": "gc_repo_distributors",
rest-api/repo/cud.rst: "_ns": "gc_repo_importers",
rest-api/repo/cud.rst: "_ns": "gc_repo_distributors",
+ This bug was cloned from Bugzilla Bug #1004623 +