Automatically extracting metadata for Grey Literature reports

compared with
Version 3 by Jenny Mitcham
on Sep 27, 2011 16:39.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (4)

View Page History
| *Title* \\ | Automatically extracting metadata for Grey Literature reports |
| *Detailed description* | _Sometimes we receive batches of grey literature reports for which we don't have any metadata. This means we can not include them in the grey literature library because they will not be discoverable. The only solution to this we have used thus far is to open each report and create metadata by hand. It would be great if this could be automated in some way. Ideally the metadata we_ \\ |
| *Issue champion* | _Who owns the issue? Include an email address if possible_ |
| *Detailed description* | _Sometimes we receive batches of grey literature reports for which we don't have any metadata. This means we can not include them in the grey literature library because they will not be discoverable. The only solution to this we have used thus far is to open each report and create metadata by hand. We generally don't have time/money to do this so wait until we have a willing placement student\! It would be great if this could be automated in some way. Metadata we need is quite detailed and hard to extract (location of archaeological fieldwork, monument types, artefacts and periods) but perhaps more achievable is getting basic details from title page (Report title, author/s, date produced, name of contracting unit/organisation)_ \\ |
| *Issue champion* | Jenny Mitcham (ADS) [email protected]\\ |
| *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_ \\ |
| *Possible Solution approaches* | * Check in the pdf or doc document properties to see if any useful metadata in there. Then check to see if these appear on title page of report to assess how reliable they are |
| *Context* | _Details of the institutional context to the Issue. (May be expanded at a later date)_ \\ |
| *Lessons Learned* | _Notes on Lessons Learned from tackling this Issue that might be useful to inform digital preservation best practice_ \\ |