You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Table of Contents

Outstanding Issues


ISSUE-1: Ingest of demo:5,18,29,14 fail with non-fedora context

CAUSE: Hardcoded URLs that don't use local.fedora.server.

ACTION: Review all demo objects and use local.fedora.server where possible.  As per the solution for issue-2, use local.fedora.server/fedora/ (contiguous, not split up) where appropriate.

WHO: Aaron

STATUS: ?


ISSUE-2: Smiley demo "list" dissemination doesn't work with non-fedora context

CAUSE: The SDep, demo:CollectionImpl requires the "fedora" part of the path to be specified: <http:operation location="fedora/risearch[...]">.

ACTION:

  • (Required) Modify Fedora so that http[s]/local.fedora.server/fedora/ is interpreted at runtime (and translated when appropriate at export time) with protocol://host:port/context/ and all other occurances of http[s]://local.fedora.server/ are interpreted/translated as protocol://host:port/

    • In content of WSDL and other "special" datastreams identified in DOTranslationUtility, when in the "migration" export context (in the same spirit as is done currently with local.fedora.server).  This solution will be backward compatible.
    • For E and R datastreams
    • At runtime when reading the WSDL to decide which URL to send the dissemination request to.  In this case, "splitting up" the URL in the WSDL should work, so doing the local.fedora.server[/fedora] substitution should happen after the operation URL is constructed from the two places in the WSDL.  But it's not required for the translation at export (with "public" context) to do the replacement.

  • (Required) Make sure all demo objects use this where appropriate (See ISSUE-1)
  • (Required) Document this behavior where appropriate in the user docs.  Note that it's not recommended to "split up" local.fedora.server/fedora/ in the WSDL because replacement won't be done on export (with "public" context) that case.
  • (Optional) Create src/test-objects to make sure it works (with possible unit tests)
  • (Optional) Find a way to avoid the hardcoding of "/fedora" in the stylesheet used by the smiley demos.  Ideally, the correct URL for the images can be constructed without the stylesheet knowing where Fedora is mounted.

WHO: Aaron

STATUS: This is being tracked in FCREPO-486 and FCREPO-487.  Work is being done in branches/fcrepo-487


ISSUE-3: System tests don't pass with non-fedora context

CAUSE: Not fully determined, but ISSUE-1 above is one probable cause.  At least ConfigA was failing for Eddie when he tried it.  Eddie also saw strange references to 127.0.1.1, but grepping the code for this turned up no result.  Also, Andrew noticed a failure with testBatchModify, which Kai has fixed, and Andrew has updated the documentation.

ACTION: Re-run tests, making sure to set the correct fedora.appServerContext in build.xml and webapp_name in env-server.sh beforehand.

WHO: Eddie

STATUS: ?


ISSUE-4: fedora-ingest-demos doesn't work with non-fedora context and usage message is incorrect.

CAUSE: Doesn't pass optional parameters, so the ctx param is never passed in.

ACTION: Fix usage message and allow it to take ctx

WHO: Kai

STATUS: ?


ISSUE-5: fedora-rebuild gives confusing error message with non-fedora context when WEBAPP_NAME is not changed in env-server.sh/bat

CAUSE: The fedora-rebuild script uses this info to determine what the classpath is, in order to run the right java ... command.

ACTION: Give better error message. (Also see DOC-1)

WHO: Kai

STATUS: ?


ISSUE-6: Some commandline scripts not covered by tests (Kai noticed)

ACTION: Identify which ones

WHO: Kai

STATUS: ?


ISSUE-7: Ingest and add managed datastream not working with new admin ui.

CAUSE: Repeatable in Chris' environment when AuthN off for API-A and first attempt to POST to rest api is via one of these actions.  This appeared to be happening because the popup window closes before the browser has a chance to prompt for credentials. So we were aiming for a solution that ensured credientials would be prompted for beforehand.  However, it now appears to be happening regardless of the credentials... the data just doesn't make it into Fedora in some cases.  Keeping the upload popup open after submit has been pressed (manually removing onSubmit="window.close()") seems to consistently allow this to succeed, regardless of credentials.  Keeping it open for only two seconds causes the upload to fail when sending in a large file, so it clearly needs to remain open while the upload is in progress.

ACTION:

  • (Required) Modify the upload form to use XmlHttpRequest so it can stay open while the upload is occurring, and close when the upload is finished.
  • (Optional) Since this gives the opportunity to examine the response, provide appropriate feedback a) while the upload is in progress, b) if the upload fails, c) if the upload succeeds

WHO: Bill

STATUS: In progress Weds.


ISSUE-8: Analyzer issues  warning when running with Derby embedded

CAUSE: Derby embedded requires the database to be shutdown through java code before the vm exits, or it issues a warning.

ACTION: Document that this is a harmless warning in the migration doc

WHO: Chris

STATUS: (tick)


ISSUE-9: Upgrade from 3.1 still needs to be tested.

ACTION: Normal install (point new fcfg to old db+data/ dir), then run RI rebuilder for Mulgara

WHO: Eddie

STATUS: ?


ISSUE-10: Journal RMI Reciever not distributed or acknowledged in docs

ACTION: Make a build.xml target for a self-contained jar distribution (with version=3.2) and note it's existence in journaling documentation.

WHO: Aaron

STATUS: ?


Outstanding Documentation


DOC-1: Finish doc updates for webapp context configuration (with note that it's experimental)
- Update installer text to note "experimental"
- Write a new doc that gives:
a) General description (with note that it's experimental)
b) Instruction to change WEBAPP_NAME in server-env.sh/bat
c) Instruction to change build.xml's fedora.appServerContext if running tests from source
Link to this doc from install/config guide and commandline utils doc.

WHO: Andrew, with help from Kai

STATUS: Installer text updated. New doc started here


DOC-2: Update rebuilder documentation
- Review for accuracy
- Note that Java 1.6 is needed if running with MySQL

WHO: Chris

STATUS: ?


DOC-3: New doc: "Configuring Lowlevel Storage" (covers Akubra), linked from install/config

WHO: Chris

STATUS: ?


DOC-4: New doc: "Web-Based Admin UI"

WHO: Bill

STATUS: ?


DOC-5: Release Notes
- Take things in from JIRA
- Make 2.x support announcement with 3.2 release

WHO: Chris

STATUS: ?


DOC-6: Review migration guide for accuracy with 3.2

WHO: Chris

STATUS: (tick)


DOC-7: SWORD-Fedora integration guide (FCREPO-404)

WHO: Eddie

STATUS: ?


#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels