Skip to content
New issue

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

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

Already on GitHub? # to your account

Problem: The impact for users of the sanitize names microservice could be documented better #387

Closed
ross-spencer opened this issue Dec 17, 2018 · 1 comment
Assignees
Labels
Type: documentation The issue requires documentation.

Comments

@ross-spencer
Copy link
Contributor

Making an issue from a ticket comment as I think we were planning to do this, but the original ticket was closed as part of the 1.8 release.

Some suggested text/things to look at there: #16 (comment)

NB. There are a number of tickets outstanding for this microservice as well which might impact this one, e.g. #324


For Artefactual use:
Please make sure these steps are taken before moving this issue from Review to Verified in Waffle:

  • All PRs related to this issue are properly linked 👍
  • All PRs related to this issue have been merged 👍
  • Test plan for this issue has been implemented and passed 👍
  • Documentation regarding this issue has been written and it has been added to the release notes, if needed 👍
@ross-spencer ross-spencer added the Type: documentation The issue requires documentation. label Dec 17, 2018
@ross-spencer
Copy link
Contributor Author

@sallain sallain self-assigned this Jan 16, 2019
sallain added a commit to artefactual/archivematica-docs that referenced this issue Jan 17, 2019
This is an attempt to explain why and how Archivematica changes file
and directory names during Transfer and Ingest. Feedback welcome!

Connected to archivematica/Issues#387
sallain added a commit to artefactual/archivematica-docs that referenced this issue Jan 18, 2019
This is an attempt to explain why and how Archivematica changes file
and directory names during Transfer and Ingest. Feedback welcome!

Connected to archivematica/Issues#387
sallain added a commit to artefactual/archivematica-docs that referenced this issue Jan 18, 2019
This is an attempt to explain why and how Archivematica changes file
and directory names during Transfer and Ingest. Feedback welcome!

Connected to archivematica/Issues#387
sallain added a commit to artefactual/archivematica-docs that referenced this issue Jan 18, 2019
This is an attempt to explain why and how Archivematica changes file
and directory names during Transfer and Ingest. Feedback welcome!

Connected to archivematica/Issues#387
@sallain sallain added the Status: in progress Issue that is currently being worked on. label Jan 18, 2019
sallain added a commit to artefactual/archivematica-docs that referenced this issue Jan 18, 2019
* Add more information about name cleanup

This is an attempt to explain why and how Archivematica changes file
and directory names during Transfer and Ingest. Feedback welcome!

Connected to archivematica/Issues#387

* Incorporates review feedback
* Rebased on new 1.9 branch
sallain added a commit to artefactual/archivematica-docs that referenced this issue Feb 1, 2019
* Add more information about name cleanup

This is an attempt to explain why and how Archivematica changes file
and directory names during Transfer and Ingest. Feedback welcome!

Connected to archivematica/Issues#387

* Incorporates review feedback
* Rebased on new 1.9 branch
@sallain sallain closed this as completed May 7, 2019
@sallain sallain removed the Status: in progress Issue that is currently being worked on. label May 7, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Type: documentation The issue requires documentation.
Projects
None yet
Development

No branches or pull requests

2 participants