...
The IR services group has started setting policy and determining our repository’s scope. The group has divided into team of two-person teams, each of which is tackling one key area connected to the IR’s configuration. Here are the areas the group we’ve tackled so far:
Purpose- What is our repository’s raison d'etre?
...
User Communities- Who can submit content to the repository? (i.e. faculty, staff, grad students, undergrads)
Noa and GabeI, for example, are working on the ‘Intellectual Content’ section. We’re trying to determine which types of scholarly content will be accepted, and how submitted materials will be vetted. This also involves looking at the file extensions DSpace can handle and comparing them listing out the DSpace-compatible file extensions, then comparing this list to the file types we’re interested in collecting in the IR (. This process leads to a number of questions, for example, will we be supporting Illustrator working files, even though they can’t be displayed through the system?). ‘Intellectual Content’ also involves a digital preservation component: many institutions advise submitters on the support level they offer for a given file type, that is, let them know whether they’re confident that they’ll be able to host and display the file type down the line. Determining what Temple is able to support long-term --or whether we should commit to anything at all-- is extremely a complex process, requiring the input of multiple IR stakeholders and technical staff.
...