Resource functions
                        - get_resource_field_data
 - create_resource
 - delete_resource
 - copy_resource
 - get_resource_log
 - update_resource_type
 - get_resource_path
 - get_resource_data
 - get_alternative_files
 - get_resource_types
 - add_alternative_file
 - delete_alternative_file
 - upload_file
 - upload_file_by_url
 - upload_multipart
 - get_related_resources
 - resource_log_last_rows
 - replace_resource_file
 - get_resource_all_image_sizes
 - put_resource_data
 - update_related_resource
 - relate_all_resources
 - get_edit_access
 - get_resource_access
 - resource_file_readonly
 
Collection functions
                        Search functions
                        
                                            IIIF
                        
                                            Metadata functions
                        User functions
                        
                                            System
                        
                                            Message functions
                        
                                            Plugin functions
                        - consentmanager_get_consents
 - licensemanager_get_licenses
 - consentmanager_get_consent
 - consentmanager_delete_consent
 - consentmanager_batch_link_unlink
 - consentmanager_link_consent
 - consentmanager_unlink_consent
 - consentmanager_create_consent
 - consentmanager_update_consent
 - consentmanager_get_all_consents
 - consentmanager_get_all_consents_by_collection
 - consentmanager_save_file
 
create_resource_type_field
Get metadata field information for all (matching) fields.
Available from version 10.3+.
Requires permission a.
| Variable | Description | Data type | 
|---|---|---|
| $name | Field name | string | 
| $resource_types | CSV of applicable resource types for this field. Use 0 (zero) for global, for others see get_resource_types() | string | 
| $type | Metadata field type. For values see the FIELD_TYPE_* constants | string | 
Response
Returns a 403 HTTP status if not authorised or 200 HTTP status with an appropriate payload.
Examples
Successful request processed:
{"status":"success","data":{"ref":129}}
Bad input (e.g empty name or invalid resource type or type) causing a failure:
{"status":"fail","data":{"message":"Unable to save"}}