Changes (1)

| *Title* \\ | Sorting Error Messages by Pdf Creation Software. The to-built-tool will detect the Software which has created the Pdf File and \\

\\

Keep it short, but make it descriptive so that other people can get the gist of what your issue is about, just from the title. \\ | | *Detailed description* | _A detailed description of the Issue. The Issue_ *{_}MUST{_}* _focus on the busines or preservation driven challenge, and should not assume or prescribe a particular solution. Describe what the Issue is, why you have the Issue, and what your requirements are for a Solution. For example, it might be important that a technical solution runs on UNIX, or has a GUI front end and is easy to use, or needs to process records efficiently as the Dataset is large._ |

...

| *Issue champion* | _Who owns the issue? Type "\[" and then your name to use autocomplete.&nbsp;_{_}This creates a link to your user profile on the wiki, including your contact details, so is the best way to add your name.._ | | *Other interested parties* \\ | _Any other parties who are also interested in applying Issue Solutions to their Datasets._ | | *Possible Solution approaches* | _Brief brainstorm of possible approaches to solving the Issue. Each approach should be described in a single sentence as part of a bulleted list. Further detail can go in a dedicated Solution page._ \\ | | *Context* | _Details of the institutional context to the Issue._ \\ | | *Lessons Learned* | _Notes on Lessons Learned from tackling this Issue that might be useful to inform digital preservation best practice_&nbsp;. \\ | | *Datasets* | _Reference to the appropriate Dataset page, by hyperlink. Note that all Issues_ *{_}MUST{_}* _be linked to at least one Dataset\!_ \\ | | *Solutions* | _Reference to the appropriate Solution page(s), by hyperlink._ |