How do I make the case for what I want to do?: Difference between revisions

From wiki.dpconline.org
Jump to navigation Jump to search
No edit summary
No edit summary
Line 27: Line 27:


*What guidance do you need to provide to the depositor?
*What guidance do you need to provide to the depositor?
<blockquote>Depositors should be made aware of the various legal issues surrounding the accessioning of their data into your repository. These include intellectual property rights, protection of personal data, liability for defamatory or illegal content,  and freedom of information requests.
<blockquote>Depositors should be made aware of the various legal issues surrounding the accessioning of their data into your repository. These include intellectual property rights, protection of personal data, liability for defamatory or illegal content,  and freedom of information requests.</blockquote>
 
<blockquote>Depositors should also be informed about any technical requirements that need to be met for items to be accepted by your repository (e.g. specific file format requirements) and your requirements concerning metadata and documentation that should be supplied with deposits.</blockquote>
Depositors should also be informed about any technical requirements that need to be met for items to be accepted by your repository (e.g. specific file format requirements) and your requirements concerning metadata and documentation that should be supplied with deposits.
</blockquote>


*How do you gather user requirements?  
*How do you gather user requirements?  

Revision as of 16:27, 31 July 2013

  • What are you proposing?
    You need to propose a set activities that are scoped properly and which clearly address the problem that you 
    have identified.  It could be a short, one off task or a longer series of activities which span multiple collections.
    Ask whether this is a 'capital' project - ie one off with a fixed completion point - or a 'revenue' activity which will
    be ongoing and indefinite.  You might illustrate it with a workflow diagram.  It helps to provide three components - a 
    risk assessment for the tasks (ie what might go wrong); a quality plan (how will you check that it works); and criteria
    for success (to prove it has worked).
  • What tools and skills do you need?
    This is very specific to your task but there are a few ways you can identify the sorts of tools and skills you need.  For 
    example, have you done a pilot of the project?  If so you will already know the sorts of tools and skills you need and will be
    able to answer this more confidently.  You can also talk to some of the interested stakeholders, like IT managers or users. 
    Some things you might need to consider:
    Tools for impact assessment- how will we know if the project has been a success/what it's impact has been?
    engagement: is there a need to engage certain stakeholders? What tools could we use to do this?
    measurement: how  do we know if the project is progressing as planned?
    Do we need to develop new tools or are suitable off-the shelf options available?
    What tools will be used to monitor risK? 
    
  • How much descriptive metadata do you need?
  • How much preservation metadata do you need?
    Metadata requirements will depend on your the existing preservation and resource discovery systems and the metadata   standards or schemas in use at your institution. If your organisation does not currently have any arrangements for 
    descriptive and preservation metadata for digital objects, you should refer to best practices in place at other institutions.
  • What guidance do you need to provide to the user?
  • What guidance do you need to provide to the depositor?

Depositors should be made aware of the various legal issues surrounding the accessioning of their data into your repository. These include intellectual property rights, protection of personal data, liability for defamatory or illegal content, and freedom of information requests.

Depositors should also be informed about any technical requirements that need to be met for items to be accepted by your repository (e.g. specific file format requirements) and your requirements concerning metadata and documentation that should be supplied with deposits.

  • How do you gather user requirements?
  • How do you gather feedback?
  • What are the rights issues?
    Here's a useful place to start: http://dx.doi.org/10.7207/twr12-02  - Andrew Charlesworth's technology watch report for 
    the DPC on Intellectual Property Rights and Preservation
  • How will it be reused (policy question)?
  It's important to think about how the implementation of you project might impact the policies in place within you institution.
  If your instituion has a policy in place supporting the reuse of data then identify how your project supports this and how
  existing policies may need to reflect new workflows.