Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with naming of directories by the DirectoryNameGiver in the importer package #151

Open
patrickzurek opened this issue Sep 9, 2016 · 1 comment

Comments

@patrickzurek
Copy link

JIRA issue created by: rcook
Originally opened: 2012-06-26 10:34 AM

Issue body:
GC issue http://code.google.com/p/xcoaitoolkit/issues/detail?id=2

[~cdelis] Is this a problem?

Reported by shreyansh.vakil, Mar 12, 2009

The problem is, that the XML directory is different when we use only
-convert and both -convert -load. There is possible, that other problems
also occur with the DirectoryNameGiver class. We should write multiple
tests to detect every possible misbehavours.

Delete comment
Comment 1 by [email protected], Apr 27, 2009

(No comment was entered for this change.)

Status: NotReleased
Owner: [email protected]
Delete comment
Comment 2 by [email protected], May 26, 2009

The bug has been fixed, released and is incorporated in the 0.6 version of the OAI
Toolkit.

Status: Done
Delete comment
Comment 3 by [email protected], Jul 29, 2009

The problem seems to be appearing again for some cases.
That is why I have re-opened this bug.

Dave came across some cases where this bug appeared again. There is still
discrepancy between the folders created by combined convert-load and importing them
separately.

Status: Accepted
Delete comment
Comment 4 by project member [email protected], Feb 18, 2010

Will not get to this before Shrey's departure.

@patrickzurek
Copy link
Author

JIRA Coment by user: rcook
JIRA Timestamp: 2012-06-26 11:43 AM

Comment body:

Chris plans to revisit the sample scripts and make sure enough scenarios are there and working (he thinks some no longer work). No plans to change code at this point as it may open more problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant