Download (PDF, 9MB, Not barrier-free file.) - Nestor

As explained in the DSpace Documentation, “DSpace's authorization system is basedon associating actions with objects and the lists of EPeople who can perform them”(Tansley et al. 2006, 15). Thus files can only be uploaded by authorized and authenticatedusers. The same is true for other possible actions in DSpace, i.e. READ, ADD, REMOVE,WRITE (ibid. 15-16), and it follows that an unauthorized modification of collections, items,or bitstreams – which would affect the authenticity and possibly integrity of documents – isprevented by means of the resource policies.Ingest: Generate AIPAccording to the DSpace data model such information packages – called items – arecomposed of one or more so-called bundles which are themselves composed of one ormore bitstreams (also called data files). Each bitstream has a bitstream format, name,size, a checksum, and a bitstream ID as well as an (optional) user description. Each itemadditionally has metadata in Dublin Core qualified and a handle. Typically, one item isdescribed by one metadata record.DSpace can be set to automatically create persistent identifiers for every itemingested into the repository as well as for communities and collections. Thus,DSpace uses Handles primarily as a means of assigning globally unique identifiers to objects.Each site running DSpace needs to obtain a Handle 'prefix' from CNRI […]. Since it's usually theitem that is being preserved, rather than the particular bit encoding, it only makes sense topersistently identify and allow access to the item, and allow users to access the appropriate bitencoding from there. (Tansley et al. 2006, 18)The Handle prefix of JUWEL is 2128 so that a typical address for a resource stored inJUWEL will look as follows: http://hdl.handle.net/2128/[Local Name]. 108 The identifiers areplaced prominently on the top of each item record and marked as the preferred link forcitation of the record and the document(s) it identifies. Any unique or persistent identifiersassigned to the document before it was submitted to the repository (e.g. ISBN or ISSNnumbers, but also other [persistent] URIs such as DOIs or URNs) can be entered into thefield dc.identifier and are hence preserved along with the other metadata. In following thispractice, JUWEL complies with the respective TRAC criterion. 109In addition, DSpace also assigns identifiers (Sequence IDs) to each bitstream.However, these are unique only within a local DSpace installation so that collisions couldoccur in a DSpace to DSpace use case. 110108 The Local Name is assigned by the Handle Naming Authority and in the case of JUWEL consists of anobject identification number unique within JUWEL. See pages 63-66 of the Paradigm Workbook for anintroduction to the Handle System. Further information can also be obtained from http://www.handle.net/ –25.10.2009.109 According to the Dublin Core element description, identifiers entered into this field provide “unambiguousreference to the resource within a given context. Recommended best practice is to identify the resource bymeans of a string or number conforming to a formal identification system. Examples of formal identificationsystems include the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL), theDigital Object Identifier (DOI) and the International Standard Book Number (ISBN)” (DCMI 2005b). Seehttp://hdl.handle.net/2128/1610 for an example of a JUWEL records with more than one persistentidentifier – 25.10.2009.110 See DSpace Wiki 2008a. See also the DSpace System Documentation on “Bitstream 'Persistent'Identifiers” (Tansley et al. 2006, 19).41