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.

Sign up for GitHub

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

Jump to bottom

analysis for the use of the data submodule #12

Open
eefahy opened this issue Aug 26, 2016 · 1 comment
Open

analysis for the use of the data submodule #12

eefahy opened this issue Aug 26, 2016 · 1 comment

Comments

@eefahy
Copy link
Contributor

eefahy commented Aug 26, 2016 •
edited
Loading

Seems like we could possibly manage the EAD XML files for this application within the source code repository. We should investigate the purpose of that to see if it makes sense to maintain those files within one repository. If there is some rationale to maintain two repositories for some purpose, we should document those reasons in the bassi_ead_xml repository
@atz
Copy link
Contributor

atz commented Oct 12, 2016

Yeah, that is sorta anti-pattern unless the test data is being actively used by more than one repo. Not really important though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@atz @eefahy