Questions about DSpace@MIT? Want to set up a DSpace community at MIT?
A DSpace@MIT Community is an administrative unit at MIT that produces research, has a defined leader, has long-term stability, and can assume responsibility for setting Community policies. Each Community must be able to assign a coordinator who can work with DSpace@MIT staff. A list of research entities can be found at http://web.mit.edu/research/, which may serve as a guide to established Communities. Individual faculty and researchers whose unit is not established in DSpace@MIT can create a Sub-Community within the Faculty and Researchers Community.
A DSpace@MIT community agrees to:
A DSpace@MIT Community retains the right to:
DSpace@MIT agrees to:
DSpace@MIT retains the right to:
MIT is expected to:
MIT Libraries foresees times when it may be necessary to remove items from the repository. It has been decided that under some circumstances items will be removed from view, but to avoid loss of the historical record, all such transactions will be traced in the form of a note in the <Description.provenance> field of the Dublin Core record. The content of the note should be one of the following:
Because any DSpace@MIT item that has existed at some time may have been cited, we will always supply a "tombstone" when someone requests a removed item. This information will include the original metadata (for verification) plus one of the above withdrawal statements in place of the link to the object. The metadata should be visible, but not searchable. These items will also be made unavailable for metadata harvesting.
All items in DSpace@MIT will have a version of the complete content for free TO THE MIT COMMUNITY, WITH STRONG ENCOURAGEMENT FOR FREE TO ALL, with the following exceptions:
Content submitters will be required to click through a Non-Exclusive Deposit License before submitting to DSpace@MIT. In order for DSpace@MIT to reproduce, translate and distribute submissions worldwide agreement to the following terms is necessary. The following is the text of the license submitters will encounter.
By clicking through this license, you (the author(s) or copyright owner(s)) grants to Massachusetts Institute of Technology (MIT) the non-exclusive right to reproduce, translate (as defined below), and/or distribute your submission (including the abstract) worldwide in electronic format.
You agree that MIT may translate the submission to any medium or format for the purpose of preservation.
You also agree that MIT may keep more than one copy of this submission for purposes of security, back-up, and preservation.
You represent that the submission is your original work, and/or that you have the right to grant the rights contained in this license. You also represent that your submission does not, to the best of your knowledge, infringe upon anyone's copyright.
If the submission contains material for which you do not hold copyright, you represent that you have obtained the unrestricted permission of the copyright owner to grant MIT the rights required by this license, and that such third-party owned material is clearly identified and acknowledged within the text or content of the submission.
IF THE SUBMISSION IS BASED UPON WORK THAT HAS BEEN SPONSORED OR SUPPORTED BY AN AGENCY OR ORGANIZATION OTHER THAN MIT, YOU REPRESENT THAT YOU HAVE FULFILLED ANY RIGHT OF REVIEW OR OTHER OBLIGATIONS REQUIRED BY SUCH CONTRACT OR AGREEMENT.
MIT will not make any alteration, other than as allowed by this license, to your submission.
Creative Commons provides alternative licenses whereby you can release some of the rights you are automatically assigned by copyright law.
The most open license is the Attribution license. With this you receive the greatest exposure for your work, since allows your work to be distributed anywhere or modified to someone's specific needs, while still giving you credit for its creation.
Other Creative Commons license choices specify whether you allow commercial use of the work, whether you allow modifications of the work, and whether you allow derivative works to be created based on your work.
When you submit content to DSpace@MIT, you see a Creative Commons form that allows you to identify the license to be used with the item you are submitting, so people can know what they're allowed to do with your work. This form is optional in DSpace@MIT; you can skip it if you wish to retain your full copyright.
This system collects personal information from:
Personal information collected by DSpace@MIT will not be used for any commercial or philanthropic purpose not directly connected with or approved by the Massachusetts Institute of Technology.
We do not disclose information about your individual visits to our site, or personal information that you provide us, such as your name, address, email address, telephone number, etc. to any outside parties except when we believe, in good faith (i) that the law requires it, or (ii) that disclosure is necessary to protect the rights and property of DSpace@MIT users.
DSpace data may be used by researchers of the HP-MIT Alliance's SIMILE research project under the conditions set forth in the "Terms for Use of DSpace Production Data".
Any DSpace@MIT records used in a publicly accessible forum, such as demonstrations, presentations, or research papers, will be scrubbed of specific references to real people and personal information.
The following categories of MIT faculty and researchers are eligible to create a collection in the "Faculty and Researcher" part of DSpace@MIT:
The DSpace@MIT team hopes to provide support for as many file formats as possible. Over time, items stored in DSpace@MIT will be preserved as is, using a combination of time-honored techniques for data management and best practices for digital preservation. As for specific formats, however, the proprietary nature of many file types makes it impossible to make guarantees. Put simply, our policy for file formats is this:
When a file is uploaded to DSpace@MIT, we assign it one of the following categories to note the level of support for its format:
By "support", we mean "make usable in the future, using whatever combination of techniques (such as migration, emulation, etc.) is appropriate given the context of need." For supported formats, we might choose to bulk-transform files from a current format version to a future one, for instance. But we can't predict which services will be necessary down the road, so we'll continually monitor formats and techniques to ensure we can accommodate needs as they arise.
In the meantime, we can choose to "support" a format if we can gather enough documentation to capture how the format works. In particular, we collect file specifications. Unfortunately, this means that proprietary formats for which these materials are not publicly available cannot be supported in DSpace@MIT. We will still preserve these files, and in cases where those formats are native to tools supported by MIT Information Systems, we will provide you with guidance on converting your files into formats we do support. It is also likely that for extremely popular but proprietary formats (such as Microsoft .doc, .xls, and .ppt), we will be able to help make files in those formats more useful in the future simply because their prevalence makes it likely tools will be available. Even so, we cannot guarantee this level of service without also having more information about the formats, so we will still list these formats as "known", not "supported."
What to do if your format isn't recognizedWe understand that there are always more formats to consider, and we would appreciate your help in identifying and studying the suitability of support for formats you care about. If we can't identify a format, DSpace@MIT will record it as "unknown", or "application/octet-stream," but we would like to keep the percentage of supported format materials in DSpace@MIT as high as possible. Don't hesitate to contact us if you have any questions or concerns.
DSpace@MIT Format Reference CollectionThe table below describes how DSpace@MIT supports each listed file type. MIME type is the Multipurpose Internet Mail Extensions (MIME) type identifier. For more information on MIME, see the MIME RFCs or the MIME FAQ. Description is what most people use as the name for the format. Extensions are typical file name extensions (the part after the dot, for example, the extension for "index.html" is "html"). These are not case-sensitive in DSpace@MIT, so either "sample.XML" or "sample.xml" will be recognized as XML. The Level is DSpace@MIT's support level for each format:
MIME type |
Description |
Extensions |
Level |
application/marc |
MARC |
marc, mrc |
supported |
application/mathematica |
Mathematica |
ma |
known |
application/msword |
Microsoft Word |
doc |
known |
application/octet-stream |
Unknown |
(anything not listed) |
unsupported |
application/pdf |
Adobe PDF |
|
supported |
application/postscript |
Postscript |
ps, eps, ai |
supported |
application/sgml |
SGML |
sgm, sgml |
known |
application/vnd.ms-excel |
Microsoft Excel |
xls |
known |
application/vnd.ms-powerpint |
Microsoft Powerpoint |
ppt |
known |
application/vnd.ms-project |
Microsoft Project |
mpp, mpx, mpd |
known |
application/vnd.visio |
Microsoft Visio |
vsd |
known |
application/wordperfect5.1 |
WordPerfect |
wpd |
known |
application/x-dvi |
TeXdvi |
dvi |
known |
application/x-filemaker |
FMP3 |
fm |
known |
application/x-latex |
LateX |
latex |
known |
application/x-photoshop |
Photoshop |
psd, pdd |
known |
application/x-tex |
TeX |
tex |
known |
audio/x-aiff |
AIFF |
aiff, aif, aifc |
supported |
audio/basic |
audio/basic |
au, snd |
known |
audio/x-mpeg |
MPEG Audio |
mpa, abs, mpeg |
supported |
audio/x-pn-realaudio |
RealAudio |
ra, ram |
known |
audio/x-wav |
WAV |
wav |
supported |
image/gif |
GIF |
gif |
supported |
image/jpeg |
JPEG |
jpeg, jpg |
supported |
image/png |
PNG |
png |
supported |
image/tiff |
TIFF |
tiff, tif |
supported |
image/x-ms-bmp |
BMP |
bmp |
known |
image/x-photo-cd |
Photo CD |
pcd |
known |
text/html |
HTML |
html, htm |
supported |
text/plain |
Text |
txt |
supported |
text/richtext |
Rich Text Format |
rtf |
supported |
text/xml |
XML |
xml |
supported |
video/mpeg |
MPEG |
mpeg, mpg, mpe |
supported |
video/quicktime |
Video Quicktime |
mov, qt |
known |
text/x-sas-syntax |
SAS Syntax File |
sas |
Supported |
application/x-sas-system |
SAS System File |
sas7bdat, sd1, sd2, sd7, ssd01, ssd, ssd04 |
Known |
application/x-sas-transport |
SAS Transport File |
xpt, cport, v5x, v6x, v7x |
Known |
text/x-spss-syntax |
SPSS Syntax File |
sps |
Supported |
application/x-spss-sav |
SPSS system file |
sav |
Known |
application/x-spss-sav |
SPSS portable file |
por |
Known |
text/x-stata-syntax |
Stata Syntax file |
do |
Supported |
application/x-stata |
Stata Binary files |
dta |
Known |
text/x-r-syntax |
R syntax file |
r, R |
Supported |
application/x-rlang-transport |
R binary file |
Rdata, rdata |
Known |
text/x-fixed-field |
fixed field text data |
dat, asc |
Supported |
text/csv |
Comma separated values |
csv |
Supported |
text/tab-separated-values |
Tab separated values |
tab |
Supported |
Any file format can be submitted. However, depending on the format of the file there may be limitations on the MIT Libraries' ability to preserve it and for the ability of others to use it. When a dataset is uploaded, it is assigned to one of three categories of support as follows:
Please contact data-management@mit.edu