Versions Compared

Old Version 4

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 5

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

UI Platform Prototype Requirements

Info

A single prototype should be achievable within a 2-4 weeks of active development (ideally closer to 2 weeks).  We've tried to scope these requirements to a bare minimum so that you need not sink a lot of development time into a prototype.

Warning
titlePrototypes should be considered "throw-away" experiments/proof-of-concepts. There is no guarrantee any prototype code will be used.

Keep in mind that all prototypes should be considered potentially "throw-away" code. We do not recommend trying to build all the functionality of DSpace, as it would be a waste of your time if it is not the chosen platform. The goal of these prototypes is merely to provide a "proof of concept" of how the platform could be used, and to get enough familiarity with the platform to determine how well it may (or may not) be able to achieve other features on the RoadMap.

Note
titleBe willing to abandon a prototype if it's not going well. Just give us feedback on what issues you encountered

A single prototype should be achievable within a 2-4 weeks of active development (ideally closer to 2 weeks). Again, because Because these prototypes should be considered "throw-away", we do not recommend working longer than necessary to provide a "proof of concept" of the UI platform. Therefore, if you hit a major roadblock on a platform, you are more than welcome to abandon it and simply describe the issues you encountered with that platform.

...