You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
8 hours ago | |
|---|---|---|
| css | 1 day ago | |
| src | 1 day ago | |
| LICENSE | 4 months ago | |
| README.md | 8 hours ago | |
| composer.json | 4 months ago | |
| metadata_profile.info.yml | 5 months ago | |
| metadata_profile.libraries.yml | 5 months ago | |
| metadata_profile.links.task.yml | 5 months ago | |
| metadata_profile.module | 6 days ago | |
| metadata_profile.permissions.yml | 4 months ago | |
| metadata_profile.services.yml | 5 months ago | |
README.md
Metadata Profiles
This module creates metadata reports on a new tab for every bundle, for example: /admin/structure/types/manage/islandora_object/metadata-profile.
Adding /download to that URL downloads a CSV report.
The report lists all fields, their types and properties, a number representing a usage count, and (if the appropriate modules are available)
- whether the field is indexed in Search API
- whether the field has a Facet.
Notes about usage counts:
- For regular fields, the usage count represents the number of entries in the field table. This counts each "delta" as an individual usage, so fields with high repeatability will have higher usage counts than the number of distinct entities using that field.
- Further to that, if revisions are being stored, then the usage count will include past revisions as well. Therefore the usage count will show a non-zero number if any revision uses a field, even if that field has been emptied out in all recent revisions.
- Further to that, if a field is shared across bundles, the usage count will include usage across all bundles, not just the one being profiled.
- For built-in properties, such as title, name, and description, the usage count will show count each entity in the bundle, regardless of whether or not that field is populated.
License
GPLv3