Closed GoogleCodeExporter closed 9 years ago
Adding on to this UI overhaul.
5. Remove the ability to link to and edit the config file. At a team meeting
this week we discussed that in its current state it poses a security risk.
Let's just remove the "online link edit feature" and require edits to the
configuration settings be done on the server to the config file. Ben has
confirmed that all edits done on the UI can also be done in the config file.
Original comment by rc...@library.rochester.edu
on 29 Mar 2011 at 5:31
Fixed in rev. 135
1. The recent change of metadata formats to marc21 was not made in this UI and
needs to be.
[Done]
2. The link to documentation should be removed. I don't think this on line
documentation is being maintained. We are currently reviewing/updating the OAI
Toolkit Manual in Microsoft Word and will be getting the updated version on to
the Wiki as soon as we can. There should only be one source for documentation
so only one set needs to be maintained.
[Removed link to local file documentation]
3. There are a bunch of links related to List Records and List
Identifiers.....with date ranges. What are these for? Do they work for any
repository? This should be reviewed and turned into a UI that works for any
repos.
[Fixed broken links which referred to a hard-coded repository id (Rochester).
It now uses the value of 'sample identifier' in OAIToolkit.server.properties
instead. As for the links related to date ranges, the ones with a "from" date
should return results. However, the ones with an until date will not since it
is always in the past; I decided to keep it in so that others may learn the
format]
4. UI is a useful starting place for new OAI Toolkit installs, but I think we
can improve this to make it more obvious what it is and how it can be used. We
also should help new users understand how they can issue OAI PMH verb requests
to see, understand and verify their data.
[Currently the starting page contains only a single link to Sample OAI PMH verb
requests page]
5. Remove the ability to link to and edit the config file. At a team meeting
this week we discussed that in its current state it poses a security risk.
Let's just remove the "online link edit feature" and require edits to the
configuration settings be done on the server to the config file. Ben has
confirmed that all edits done on the UI can also be done in the config file.
[At the bottom of the sample OAI PMH verb requests page, there is now a
read-only listing of repository settings. You may no longer edit these
settings via the web interface]
Original comment by cede...@uillinois.edu
on 7 Apr 2011 at 9:34
Released in 0.6.11alpha
Original comment by cede...@uillinois.edu
on 25 Apr 2011 at 4:36
Original issue reported on code.google.com by
rc...@library.rochester.edu
on 25 Mar 2011 at 6:22