Researchers’ issues are inevitably diverse, reflecting the wide range of research practices in different fields.

Their issues are likely to be quite technical and couched in very specific forms related to a specific research project. In offering advice RDS staff are unlikely to fully understand the research objective or the wider norms of the research culture within which the research is being conducted.

The timing of when issues are likely to be raised is unpredictable. A project idea can be developed at any time, so requests for information, while they will reflect cycles of activity for research, cannot be easily predicted. A request is quite likely to be perceived by the researcher as urgent.

Researchers will not necessarily label the issue they have as ‘research data management’, so what they ask and who they ask for help is again unpredictable. An advice service has to be both visible and able to explain clearly the scope of the RDS. Equally it's probable that the service may be asked questions somewhat beyond its remit, which it may seek to answer or refer to others. For example, researchers might well ask about relevant standards or anonymisation techniques.

Drawing the line between information and advocacy may also be problematic.

Visibility/approachability – the service needs to be visible to its potential users and offer an approachable appearance.

Interest – in responding to initial enquiries there is a need to project a sense of interest in questions asked.