DOCSLIB.ORG

Dspace Technical Documentation Fredrick Odongo Okite [[email protected]], David Bukenya [[email protected]] Uganda Christian University Library

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Dspace Technical Documentation Fredrick Odongo Okite [Odongofredrick@Gmail.Com], David Bukenya [Dbankens@Gmail.Com] Uganda Christian University Library DSpace Technical Documentation Fredrick Odongo Okite [[email protected]], David Bukenya [[email protected]] Uganda Christian University Library. Credit to Hilton Gibson, Stellenbosch University. 1 Table of Contents UCUDIR DSpace System details .................................................................................................................... 4 Preparation Stage ......................................................................................................................................... 5 Terms to note ................................................................................................................................................ 5 Essential requirements for DSpace 6.2 to run ............................................................................................... 5 Installing Postgresql in Ubuntu: ................................................................................................................ 5 Git (code version control) ......................................................................................................................... 9 Installing tomcat ....................................................................................................................................... 9 Setup Tomcat to listen on insecure port 80 ........................................................................................ 10 For secure Port 443: ............................................................................................................................ 10 Step2: Apply for a signed certificate .................................................................................................. 14 Step 3. Get the intermediate CA certs ................................................................................................ 15 Intermediate CA certs links ......................................................................................................... 15 Step 4. Configure Tomcat to use the SSL certs ................................................................................... 16 Setup Tomcat "server.xml" to use the converted certificate ............................................. 16 Step 5. Enable secure XMLUI logins .................................................................................................... 18 Step 6. Enable HTTPS by default (Optional) ........................................................................................ 18 Java environment settings for Tomcat webapp server ....................................................................... 18 Setup user permissions ....................................................................................................................... 19 Installing DSpace ......................................................................................................................................... 19 1. Getting DSpace software ................................................................................................................ 19 2. Unpacking DSpace ........................................................................................................................... 19 3. Editing DSpace Configuration ......................................................................................................... 19 4. Building DSpace ............................................................................................................................... 23 5. Installing DSpace ............................................................................................................................. 24 6. Creating DSpace Super-admin user ................................................................................................ 24 7. Telling Tomcat where to find Dspace ............................................................................................. 24 8. Testing DSpace ................................................................................................................................ 25 Essential Directory trees ............................................................................................................................. 26 Servlet Engine [Tomcat7] Directories for UCUDIR .................................................................................. 26 CATALINA_HOME ......................................................................................................................... 27 Important directories for backup and restore ............................................................................................ 28 How to configure the Handle server ........................................................................................................... 29 2 Prepare an initial handle request ........................................................................................................... 29 Send handle request email ..................................................................................................................... 29 Update DSpace config file ........................................................................................................................... 31 Rebuild DSpace ....................................................................................................................................... 31 Checking for correct operation ............................................................................................................... 32 Listening Ports ..................................................................................................................................... 32 Handle service ..................................................................................................................................... 32 Handle config ...................................................................................................................................... 32 Handle log ........................................................................................................................................... 32 Rebuild config ..................................................................................................................................... 32 Start service manually ......................................................................................................................... 32 DSpace security policy ............................................................................................................................ 33 Create new thumbnails ........................................................................................................................... 38 Setting up usage config file ..................................................................................................................... 39 Re-indexing statistics .............................................................................................................................. 40 Step 2 - Enable the DSpace authority control event listener .................................................................. 41 Step 3 - Configure the ORCID authority control plugin ........................................................................... 41 Step 3.1 ............................................................................................................................................... 41 Step 3.2 ............................................................................................................................................... 42 Step 4 - Rebuild DSpace .......................................................................................................................... 43 Step 5 - Create an ORCID authority index cache .................................................................................... 43 Tomcat Security .................................................................................................................................. 43 Folder and file permissions/ownership .............................................................................................. 43 WARNING: ........................................................................................................................................... 43 Step 6 - Maintain ORCID authority index cache...................................................................................... 43 Step 6.1 - Ad-hoc update .................................................................................................................... 43 Step 6.2 - Regular update.................................................................................................................... 43 Step 6.3 - Export authority records ..................................................................................................... 43 Upgrading DSpace. ...................................................................................................................................... 44 Upgrading an existing Dspace ................................................................................................................. 44 Migrating to a new installation. .............................................................................................................. 46 3 UCUDIR DSpace System details Server IP: e.g 196.43.140.182 Server OS: Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-87-generic x86_64) UCUDIR Version: Dspace 6.2 Servlet Container: Apache-Tomcat7 JDK: java-7-openjdk-amd64 $JAVA_HOME:
Load more

Recommended publications
  • Complexity Theory Lecture 9 Co-NP Co-NP-Complete
    Complexity Theory 1 Complexity Theory 2 co-NP Complexity Theory Lecture 9 As co-NP is the collection of complements of languages in NP, and P is closed under complementation, co-NP can also be characterised as the collection of languages of the form: ′ L = x y y <p( x ) R (x, y) { |∀ | | | | → } Anuj Dawar University of Cambridge Computer Laboratory NP – the collection of languages with succinct certificates of Easter Term 2010 membership. co-NP – the collection of languages with succinct certificates of http://www.cl.cam.ac.uk/teaching/0910/Complexity/ disqualification. Anuj Dawar May 14, 2010 Anuj Dawar May 14, 2010 Complexity Theory 3 Complexity Theory 4 NP co-NP co-NP-complete P VAL – the collection of Boolean expressions that are valid is co-NP-complete. Any language L that is the complement of an NP-complete language is co-NP-complete. Any of the situations is consistent with our present state of ¯ knowledge: Any reduction of a language L1 to L2 is also a reduction of L1–the complement of L1–to L¯2–the complement of L2. P = NP = co-NP • There is an easy reduction from the complement of SAT to VAL, P = NP co-NP = NP = co-NP • ∩ namely the map that takes an expression to its negation. P = NP co-NP = NP = co-NP • ∩ VAL P P = NP = co-NP ∈ ⇒ P = NP co-NP = NP = co-NP • ∩ VAL NP NP = co-NP ∈ ⇒ Anuj Dawar May 14, 2010 Anuj Dawar May 14, 2010 Complexity Theory 5 Complexity Theory 6 Prime Numbers Primality Consider the decision problem PRIME: Another way of putting this is that Composite is in NP.
    [Show full text]
  • On the Randomness Complexity of Interactive Proofs and Statistical Zero-Knowledge Proofs*
    On the Randomness Complexity of Interactive Proofs and Statistical Zero-Knowledge Proofs* Benny Applebaum† Eyal Golombek* Abstract We study the randomness complexity of interactive proofs and zero-knowledge proofs. In particular, we ask whether it is possible to reduce the randomness complexity, R, of the verifier to be comparable with the number of bits, CV , that the verifier sends during the interaction. We show that such randomness sparsification is possible in several settings. Specifically, unconditional sparsification can be obtained in the non-uniform setting (where the verifier is modelled as a circuit), and in the uniform setting where the parties have access to a (reusable) common-random-string (CRS). We further show that constant-round uniform protocols can be sparsified without a CRS under a plausible worst-case complexity-theoretic assumption that was used previously in the context of derandomization. All the above sparsification results preserve statistical-zero knowledge provided that this property holds against a cheating verifier. We further show that randomness sparsification can be applied to honest-verifier statistical zero-knowledge (HVSZK) proofs at the expense of increasing the communica- tion from the prover by R−F bits, or, in the case of honest-verifier perfect zero-knowledge (HVPZK) by slowing down the simulation by a factor of 2R−F . Here F is a new measure of accessible bit complexity of an HVZK proof system that ranges from 0 to R, where a maximal grade of R is achieved when zero- knowledge holds against a “semi-malicious” verifier that maliciously selects its random tape and then plays honestly.
    [Show full text]
  • Dspace 6.X Documentation
    DSpace 6.x Documentation DSpace 6.x Documentation Author: The DSpace Developer Team Date: 27 June 2018 URL: https://wiki.duraspace.org/display/DSDOC6x Page 1 of 924 DSpace 6.x Documentation Table of Contents 1 Introduction ___________________________________________________________________________ 7 1.1 Release Notes ____________________________________________________________________ 8 1.1.1 6.3 Release Notes ___________________________________________________________ 8 1.1.2 6.2 Release Notes __________________________________________________________ 11 1.1.3 6.1 Release Notes _________________________________________________________ 12 1.1.4 6.0 Release Notes __________________________________________________________ 14 1.2 Functional Overview _______________________________________________________________ 22 1.2.1 Online access to your digital assets ____________________________________________ 23 1.2.2 Metadata Management ______________________________________________________ 25 1.2.3 Licensing _________________________________________________________________ 27 1.2.4 Persistent URLs and Identifiers _______________________________________________ 28 1.2.5 Getting content into DSpace __________________________________________________ 30 1.2.6 Getting content out of DSpace ________________________________________________ 33 1.2.7 User Management __________________________________________________________ 35 1.2.8 Access Control ____________________________________________________________ 36 1.2.9 Usage Metrics _____________________________________________________________
    [Show full text]
  • The Complexity Zoo
    The Complexity Zoo Scott Aaronson www.ScottAaronson.com LATEX Translation by Chris Bourke [email protected] 417 classes and counting 1 Contents 1 About This Document 3 2 Introductory Essay 4 2.1 Recommended Further Reading ......................... 4 2.2 Other Theory Compendia ............................ 5 2.3 Errors? ....................................... 5 3 Pronunciation Guide 6 4 Complexity Classes 10 5 Special Zoo Exhibit: Classes of Quantum States and Probability Distribu- tions 110 6 Acknowledgements 116 7 Bibliography 117 2 1 About This Document What is this? Well its a PDF version of the website www.ComplexityZoo.com typeset in LATEX using the complexity package. Well, what’s that? The original Complexity Zoo is a website created by Scott Aaronson which contains a (more or less) comprehensive list of Complexity Classes studied in the area of theoretical computer science known as Computa- tional Complexity. I took on the (mostly painless, thank god for regular expressions) task of translating the Zoo’s HTML code to LATEX for two reasons. First, as a regular Zoo patron, I thought, “what better way to honor such an endeavor than to spruce up the cages a bit and typeset them all in beautiful LATEX.” Second, I thought it would be a perfect project to develop complexity, a LATEX pack- age I’ve created that defines commands to typeset (almost) all of the complexity classes you’ll find here (along with some handy options that allow you to conveniently change the fonts with a single option parameters). To get the package, visit my own home page at http://www.cse.unl.edu/~cbourke/.
    [Show full text]
  • A Short History of Computational Complexity
    The Computational Complexity Column by Lance FORTNOW NEC Laboratories America 4 Independence Way, Princeton, NJ 08540, USA [email protected] http://www.neci.nj.nec.com/homepages/fortnow/beatcs Every third year the Conference on Computational Complexity is held in Europe and this summer the University of Aarhus (Denmark) will host the meeting July 7-10. More details at the conference web page http://www.computationalcomplexity.org This month we present a historical view of computational complexity written by Steve Homer and myself. This is a preliminary version of a chapter to be included in an upcoming North-Holland Handbook of the History of Mathematical Logic edited by Dirk van Dalen, John Dawson and Aki Kanamori. A Short History of Computational Complexity Lance Fortnow1 Steve Homer2 NEC Research Institute Computer Science Department 4 Independence Way Boston University Princeton, NJ 08540 111 Cummington Street Boston, MA 02215 1 Introduction It all started with a machine. In 1936, Turing developed his theoretical com- putational model. He based his model on how he perceived mathematicians think. As digital computers were developed in the 40's and 50's, the Turing machine proved itself as the right theoretical model for computation. Quickly though we discovered that the basic Turing machine model fails to account for the amount of time or memory needed by a computer, a critical issue today but even more so in those early days of computing. The key idea to measure time and space as a function of the length of the input came in the early 1960's by Hartmanis and Stearns.
    [Show full text]
  • On Unapproximable Versions of NP-Complete Problems By
    SIAM J. COMPUT. () 1996 Society for Industrial and Applied Mathematics Vol. 25, No. 6, pp. 1293-1304, December 1996 O09 ON UNAPPROXIMABLE VERSIONS OF NP-COMPLETE PROBLEMS* DAVID ZUCKERMANt Abstract. We prove that all of Karp's 21 original NP-complete problems have a version that is hard to approximate. These versions are obtained from the original problems by adding essentially the same simple constraint. We further show that these problems are absurdly hard to approximate. In fact, no polynomial-time algorithm can even approximate log (k) of the magnitude of these problems to within any constant factor, where log (k) denotes the logarithm iterated k times, unless NP is recognized by slightly superpolynomial randomized machines. We use the same technique to improve the constant such that MAX CLIQUE is hard to approximate to within a factor of n. Finally, we show that it is even harder to approximate two counting problems: counting the number of satisfying assignments to a monotone 2SAT formula and computing the permanent of -1, 0, 1 matrices. Key words. NP-complete, unapproximable, randomized reduction, clique, counting problems, permanent, 2SAT AMS subject classifications. 68Q15, 68Q25, 68Q99 1. Introduction. 1.1. Previous work. The theory of NP-completeness was developed in order to explain why certain computational problems appeared intractable [10, 14, 12]. Yet certain optimization problems, such as MAX KNAPSACK, while being NP-complete to compute exactly, can be approximated very accurately. It is therefore vital to ascertain how difficult various optimization problems are to approximate. One problem that eluded attempts at accurate approximation is MAX CLIQUE.
    [Show full text]
  • Complexity Theory
    Mapping Reductions Part II -and- Complexity Theory Announcements ● Casual CS Dinner for Women Studying Computer Science is tomorrow night: Thursday, March 7 at 6PM in Gates 219! ● RSVP through the email link sent out earlier this week. Announcements ● Problem Set 7 due tomorrow at 12:50PM with a late day. ● This is a hard deadline – no submissions will be accepted after 12:50PM so that we can release solutions early. Recap from Last Time Mapping Reductions ● A function f : Σ1* → Σ2* is called a mapping reduction from A to B iff ● For any w ∈ Σ1*, w ∈ A iff f(w) ∈ B. ● f is a computable function. ● Intuitively, a mapping reduction from A to B says that a computer can transform any instance of A into an instance of B such that the answer to B is the answer to A. Why Mapping Reducibility Matters ● Theorem: If B ∈ R and A ≤M B, then A ∈ R. ● Theorem: If B ∈ RE and A ≤M B, then A ∈ RE. ● Theorem: If B ∈ co-RE and A ≤M B, then A ∈ co-RE. ● Intuitively: A ≤M B means “A is not harder than B.” Why Mapping Reducibility Matters ● Theorem: If A ∉ R and A ≤M B, then B ∉ R. ● Theorem: If A ∉ RE and A ≤M B, then B ∉ RE. ● Theorem: If A ∉ co-RE and A ≤M B, then B ∉ co-RE. ● Intuitively: A ≤M B means “B is at at least as hard as A.” Why Mapping Reducibility Matters IfIf thisthis oneone isis “easy”“easy” ((RR,, RERE,, co-co-RERE)…)… A ≤M B …… thenthen thisthis oneone isis “easy”“easy” ((RR,, RERE,, co-co-RERE)) too.too.
    [Show full text]
  • 1 RP and BPP
    princeton university cos 522: computational complexity Lecture 6: Randomized Computation Lecturer: Sanjeev Arora Scribe:Manoj A randomized Turing Machine has a transition diagram similar to a nondeterministic TM: multiple transitions are possible out of each state. Whenever the machine can validly more than one outgoing transition, we assume it chooses randomly among them. For now we assume that there is either one outgoing transition (a deterministic step) or two, in which case the machine chooses each with probability 1/2. (We see later that this simplifying assumption does not effect any of the theory we will develop.) Thus the machine is assumed to have a fair random coin. The new quantity of interest is the probability that the machine accepts an input. The probability is taken over the coin flips of the machine. 1 RP and BPP Definition 1 RP is the class of all languages L, such that there is a polynomial time randomized TM M such that 1 x ∈ L ⇔ Pr[M accepts x] ≥ (1) 2 x ∈ L ⇔ Pr[M accepts x]=0 (2) We can also define a class where we allow two-sided errors. Definition 2 BPP is the class of all languages L, such that there is a polynomial time randomized TM M such that 2 x ∈ L ⇔ Pr[M accepts x] ≥ (3) 3 1 x ∈ L ⇔ Pr[M accepts x] ≤ (4) 3 As in the case of NP, we can given an alternative definiton for these classes. Instead of the TM flipping coins by itself, we think of a string of coin flips provided to the TM as an additional input.
    [Show full text]
  • 18.405J S16 Lecture 3: Circuits and Karp-Lipton
    18.405J/6.841J: Advanced Complexity Theory Spring 2016 Lecture 3: Circuits and Karp-Lipton Scribe: Anonymous Student Prof. Dana Moshkovitz Scribe Date: Fall 2012 1 Overview In the last lecture we examined relativization. We found that a common method (diagonalization) for proving non-inclusions between classes of problems was, alone, insufficient to settle the P versus NP problem. This was due to the existence of two orcales: one for which P = NP and another for which P =6 NP . Therefore, in our search for a solution, we must look into the inner workings of computation. In this lecture we will examine the role of Boolean Circuits in complexity theory. We will define the class P=poly based on the circuit model of computation. We will go on to give a weak circuit lower bound and prove the Karp-Lipton Theorem. 2 Boolean Circuits Turing Machines are, strange as it may sound, a relatively high level programming language. Because we found that diagonalization alone is not sufficient to settle the P versus NP problem, we want to look at a lower level model of computation. It may, for example, be easier to work at the bit level. To this end, we examine boolean circuits. Note that any function f : f0; 1gn ! f0; 1g is expressible as a boolean circuit. 2.1 Definitions Definition 1. Let T : N ! N.A T -size circuit family is a sequence fCng such that for all n, Cn is a boolean circuit of size (in, say, gates) at most T (n). SIZE(T ) is the class of languages with T -size circuits.
    [Show full text]
  • On the Computational Complexity of Algorithms by J
    ON THE COMPUTATIONAL COMPLEXITY OF ALGORITHMS BY J. HARTMANIS AND R. E. STEARNS I. Introduction. In his celebrated paper [1], A. M. Turing investigated the computability of sequences (functions) by mechanical procedures and showed that the setofsequencescanbe partitioned into computable and noncomputable sequences. One finds, however, that some computable sequences are very easy to compute whereas other computable sequences seem to have an inherent complexity that makes them difficult to compute. In this paper, we investigate a scheme of classifying sequences according to how hard they are to compute. This scheme puts a rich structure on the computable sequences and a variety of theorems are established. Furthermore, this scheme can be generalized to classify numbers, functions, or recognition problems according to their compu- tational complexity. The computational complexity of a sequence is to be measured by how fast a multitape Turing machine can print out the terms of the sequence. This particular abstract model of a computing device is chosen because much of the work in this area is stimulated by the rapidly growing importance of computation through the use of digital computers, and all digital computers in a slightly idealized form belong to the class of multitape Turing machines. More specifically, if Tin) is a computable, monotone increasing function of positive integers into positive integers and if a is a (binary) sequence, then we say that a is in complexity class ST or that a is T-computable if and only if there is a multitape Turing machine 3~ such that 3~ computes the nth term of a. within Tin) operations.
    [Show full text]
  • Projects. Probabilistically Checkable Proofs... Probabilistically Checkable Proofs PCP Example
    Projects. Probabilistically Checkable Proofs... Probabilistically Checkable Proofs What’s a proof? Statement: A formula φ is satisfiable. Proof: assignment, a. Property: 5 minute presentations. Can check proof in polynomial time. A real theory. Polytime Verifier: V (π) Class times over RRR week. A tiny introduction... There is π for satisfiable φ where V(π) says yes. For unsatisfiable φ, V (π) always says no. Will post schedule. ...and one idea Can prove any statement in NP. Tests submitted by Monday (mostly) graded. ...using random walks. Rest will be done this afternoon. Probabilistically Checkable Proof System:(r(n),q(n)) n is size of φ. Proof: π. Polytime V(π) Using r(n) random bits, look at q(n) places in π If φ is satisfiable, there is a π, where Verifier says yes. If φ is not satisfiable, for all π, Pr[V(π) says yes] 1/2. ≤ PCP Example. Probabilistically Checkable Proof System:(r(n),q(n)) Probabilistically Checkable Proof System:(r(n),q(n)) Graph Not Isomorphism: (G ,G ). n is size of φ. 1 2 n is size of φ. There is no way to permute the vertices of G1 to get G2. Proof: π. Proof: π. Polytime V(π) Give a PCP(poly(n), 1). (Weaker than PCP(O(logn), 3). Polytime V(π) Using r(n) random bits, look at q(n) places in π Exponential sized proof is allowed. Using r(n) random bits, look at q(n) places in π If φ is satisfiable, there is a π, Can only look at 1 place, though.
    [Show full text]
  • Complexity Classes
    CHAPTER Complexity Classes In an ideal world, each computational problem would be classified at least approximately by its use of computational resources. Unfortunately, our ability to so classify some important prob- lems is limited. We must be content to show that such problems fall into general complexity classes, such as the polynomial-time problems P, problems whose running time on a determin- istic Turing machine is a polynomial in the length of its input, or NP, the polynomial-time problems on nondeterministic Turing machines. Many complexity classes contain “complete problems,” problems that are hardest in the class. If the complexity of one complete problem is known, that of all complete problems is known. Thus, it is very useful to know that a problem is complete for a particular complexity class. For example, the class of NP-complete problems, the hardest problems in NP, contains many hundreds of important combinatorial problems such as the Traveling Salesperson Prob- lem. It is known that each NP-complete problem can be solved in time exponential in the size of the problem, but it is not known whether they can be solved in polynomial time. Whether ? P and NP are equal or not is known as the P = NP question. Decades of research have been devoted to this question without success. As a consequence, knowing that a problem is NP- complete is good evidence that it is an exponential-time problem. On the other hand, if one such problem were shown to be in P, all such problems would be been shown to be in P,a result that would be most important.
    [Show full text]