# OD-1078: Investigate whether Sources need to be associated with both Data Profiles and Resources [Keith has already confirmed in this comment](https://open-data-ed.atlassian.net/browse/OD-1078?focusedCommentId=12164), that they want the option to associate sources to be available for both Data profiles and Resources. This investigating however focuses on the best approach to implement associating it with the resources. Since this field is not mandatory, the recommended approach would be to add a field to the extras column in the resource table as described in the ckan docs on [adding custom fields to datasets](https://docs.ckan.org/en/2.8/extensions/adding-custom-fields.html#adding-custom-fields-to-datasets). The ckan docs also [advises against adding a column directly to the `resources` table](https://docs.ckan.org/en/2.8/extensions/best-practices.html#don-t-edit-ckan-s-database-tables) This approach is already being used [in the ed extension](https://github.com/CivicActions/ckanext-ed/blob/47efde6ff477ce919928a08649d8af43209aedc7/ckanext/ed/plugin.py#L200-L204) for other fields such as the `data_dictionary` and the `approval_status`. We can then store the id referencing the source object in the source table within this field.