Open (please investigate this page)
In progress (it is being worked on)
Ready for review (please check my work)
Reviewed and needs work (either additions, deletions, or modifications)
Closed (final review complete and accepted)
---
Please indicate in a new row if a new page is needed
| Status | Who? | Page | History | Notes |
|---|---|---|---|---|
| Quick Start | |||
| David Wilcox | Deployment Tooling | ||
| Jennifer Gilbert | Feature Tour | Screenshots should be updated from Fedora 4 to 5. | |
| Jennifer Gilbert | Reworded first sentence for clarity. | The instructions for Creating Containers or Binaries tells the user to select "container" but the screenshot displays "object" as the type. | |
| Jennifer Gilbert | Might be helpful to expand on how/why of binary description (not the binary itself) | ||
| Jennifer Gilbert | Minor change one sentence | ||
| Jennifer Gilbert | |||
| Jennifer Gilbert | |||
| Features | |||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| The "Overview" section states that this page includes "best practices when using Fedora Versioning," no practices are explicitly mentioned. Perhaps reorganizing sections to move more fluidly from an explanation of Fedora's implementation of Memento, to the use of versioning in Fedora. This page also seems to lack information about implementing versioning either directly on the page, or by linking out. The "Note bene" section states "Fedora does not automatically initiate versioning for all resources. The client MUST initiate versioning by invoking a special Link header at the time a resource is created." The phrase "invoking a special Link header" lacks explanation, "See ?????" needs a link to a relevant resource. I would also recommend moving the statement that Fedora does not automatically initiate versioning into the "Overview" section rather than the bottom "Note bene." | |||
| In the "Overview" section, a link to information about the "internal PID minter" would be helpful. The term "PID" is used without first being defined. The phrases "external REST service" and "external HTTP minter service" appear to be used interchangeably, this can be confusing. | |||
| This page would benefit from more information about what implementing LDP means practically for interacting with resources, e.g. what is the effect of "Fedora uses LDP terminology to describe resources and associated properties"? What does this allow a repo manager or user to do in/with Fedora? Strongly recommend tying this in (and linking) to existing pages with more concrete examples, e.g. LDP-PCDM-F4 In Action and associated pages. | |||
| ||||
| ||||
| ||||
| Paul Cummins | Administrator Guide | Under the first section, "Deploying..." something could be added to indicate that it covers Tomcat and Jetty and Java properties. "The Fedora 4 " (Authentication (AuthN) and Authorization (AuthZ) framework} could maybe be changed to The Fedora ... The 3rd heading could indicate that it covers info on the camel serialization module and installation and use of the import-export utility. The last heading's section (OAI Provider) says that it is not in support since Fedora 4.4, consider removing heading and linked page or add historical link. | |
| Paul Cummins | First header, "Downloads", could be "Requirements you may have to download", it mentions a java version output and lists 2 application containers you can chose from. Besdie the "Java 8" bullet, maybe a link to a statement on current java versions and when the community changes. The line "See the latest release for Fedora WAR files to download." should be below the requirements. The sections on Deploying with Tomcat 8 and Jetty should be merged with the next section on Deploying that lists 4 methods of deploying. "Configuration Elements" The actual required part this section mentions should be separated and placed at the top of the section. Under the "One-click run", the command line should end in a ".jar" instead of a ".war" | ||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| Import and Export Tools | |||
| Setup Camel Message Integrations | |||
| ||||
| ||||
| ||||
| ||||
| ||||
| Developer Guide | Updated Islandora documentation link. | ||
| Melissa Anez | User Guide | I'd like to see this section expand with more end-user and non-dev "intro" content. Maybe a new page with core concepts, or a fact sheet? And link from the Quick Start so it's more findable. | |
| Melissa Anez | Updated heading to put the content type first and the location second (seems more relevant), then re-ordered alphabetically. | This page could use a more basic and fulsome introduction to concepts, and more examples. Islandora models will probably be relatively similar across installations, so one could cover a lot of ground. | |
| Melissa Anez | Added another example, more specific link for Islandora mappings | ||
| Melissa Anez | FAQs and How-Tos | The line "We expose our underpinning technologies (at the Java API level, at least) for developers, so it is also helpful (and sometimes even necessary) to be familiar with the features and functions those technologies offer:" implies there's more than one example, but this page just has Modeshape. "Introduction" section needs context. Annotate the links? | |
| Melissa Anez | This needs a pretty big overdate/overhaul for the latest in Fedora. I'm not sure if it would be more appropriate to change it to a 3 →5 map, or to add a new layer and map 3->-4→ 5 | ||
| ||||
| This page appears as though it could be related to the Linked Data Platform page and mutually linked. Given that the pages it links to mention RDF, this could be a place to explain more about using RDF, or link out elsewhere. A relationship between LDP and RDF needs to be drawn somewhere. The phrase "This section documents some available patterns for using the former to meet the latter" is confusing. The main content is a note about "blank nodes" prior to any explanation of "nodes", this note is convoluted and rather difficult to follow. The page provides links to "patterns" without an explanation of what a pattern is, or how to use a pattern. Two of the links point to blank pages: | |||
| This page needs content or to be removed. It appears that "Date and time ranges" are supposed to be a "pattern" mentioned by the Common metadata design patterns page. | |||
| The title for this page, "Ordering" is not descriptive enough of the content in the page. The first sentence: "RDF, as a graph, is inherently unordered, and this can lead to difficulty when forms of description that presuppose ordering are translated into it" Needs to define RDF, a link to information about RDF, or Fedora's implementation of RDF. | |||
| Anna Dabrowski | This page needs content or to be removed. It appears that "Paired values" are supposed to be a "pattern" mentioned by the Common metadata design patterns page. | ||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| Glossary | |||
| ||||
| Design: Binaries and Descriptions |
