Page History

...

...

1. First, you will need to install the necessary prerequisites.
   1. Git is required.  If you do not already have it installed (try running git version at your command line), you can install it via https://git-scm.com/downloads (or via your local package manager tools for Linux or Mac OS)
   2. Node.js (v12.x , v14.x or v14v16.x) is required.
      1. NPM (v5.x or above) is required.  Don't worry, this gets installed with Node.js though, so you don't need to do anything extra here.
   3. Yarn (v1.x) package manage.  Just install the latest stable version of 1.x

2. Then, download our "dspace-angular" application (which is the DSpace 7 user interface) and run it.  All you should need to do is the steps in the "Quick Start" at: https://github.com/DSpace/dspace-angular/#quick-start

   Code Block
   # clone the repo git clone https://github.com/DSpace/dspace-angular.git # change directory to our repo cd dspace-angular # install the local dependencies yarn install # start the server yarn start

   
   

3. After a few minutes, the user interface will be running on your local machine.  Again, it will be accessing the REST API Demo site, so a stable internet connection is required.
   1. User Interface: http://localhost:4000/
   2. REST API (remote demo site): https://api7.dspace.org/server/
   3. Admin Login: dspacedemo+admin@gmail.com, Password: dspace
   4. Submitter Login: dspacedemo+submit@gmail.com, Password: dspace
4. Objects/Pages of interest (within the test data):
   1. Journal Example represents a journal with journal volumes, issues and articles, as detailed in the Configurable Entities Design.
   2. Publications Example contains publications which contain a combination of plain-text authors and related author entities. It also contains relations to Research Projects and Organizational Units, as detailed in the Configurable Entities design. Navigating to e.g. a Person will reveal their relations to Publications, Research Projects and Organizational Units.
   3. Submission/Workflow functionality can be tested using one of the collections in this community where the workflow is enabled. You can use the accounts mentioned above to perform the submission and workflow steps. The admin account can perform the submission and all workflow steps as well.
   4. Once logged in, MyDSpace functionality is found in the user menu (upper right).  Submissions can be started from that page, or via the "New → Item" admin menu (if logged in as an Admin)
5. One you are done testing, you can stop the locally running DSpace 7 user interface via Ctrl+C

...

• First, if you aren't sure whether it's a bug or want advice, feel free to ask on Slack or use one of our other available Support options.  The
  • On Slack, the DSpace 7 development team uses the #angular-ui channel (for UI discussions) and #rest-api channel (for REST API discussions). Though even reporting it on #dev (general developer channel) is perfectly fine.
• If you are sure it's an issue, create an issue ticket 
  • Frontend / User Interface issues (including accessibility issues) can be reported via GitHub Issues at https://github.com/DSpace/dspace-angular/issues
  • Backend / REST API issues should be reported via GitHub issues at https://github.com/DSpace/DSpace/issues
  • (If you aren't sure where to report the issue, don't worry. Just report it via either route, and we'll move it to the proper place as needed.)
• Once it is reported, we'll analyze it and schedule it to be completed (based on priority).  Please make sure to note how you found this issue and/or any steps to reproduce it.

...

• Translate DSpace 7.  If you know another language (or two or three) and want to help us with our translations, see DSpace 7 Translation - Internationalization (i18n) - Localization (l10n)
• Help us improve the DSpace 7 Documentation.  While we do our best to get our development team to write some basic Documentation for every new feature, we know that documentation is sometimes a bit technical or not as user friendly as it could be. (No offense to our developers, they are doing what they do best, help us build great new features!)  If you are interested in helping us improve our Documentation, see DSpace 7 Documentation.  We especially could use help writing new end user documentation (e.g. how to do ___ in the DSpace 7 user interface), as we have a brand new user interface!
• Help us fix bugs or review new features as they are built. If you are a bit more technical, we could use more developers willing to chip in on small bugs and/or do some quick testing (or review) of new GitHub Pull Requests.  The more testers & bug fixers we have, the quicker we can move (as all Pull Requests require testing/review from at least 2 others).  So, this sort of contribution can quite literally help us get DSpace 7 out the door more quickly!  No prior Angular or Java experience is necessary (in fact, it's a great way to learn the code or gain such experience), but you should be OK with testing PRs and providing your feedback.  Contact Tim Donohue or join a future DSpace 7 Working Group meeting.See Testing DSpace 7 Pull Requests