You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 26, 2020. It is now read-only.
Eclipse external tools feature currently works on any files that are local resources within the project. This is done via the resources API and using $selected_resource_path as a command parameter.
This feature would make another variable available for the configuration of external tool runs, something like $selected_arrangement_item_path. A variable like that would allow external tools to run on individually selected items in the arrangement.
The text was updated successfully, but these errors were encountered:
This would allow an Eclipse build to detect new output files and link them into a mdSec in METS, then from there back to the item in the structMap for the project.
The METS builder would need the following:
tool name (used for output dir name and GROUPID in mdSec)
type of mdSec to create (techMD, rightsMD, sourceMD, digiprovMD, dmdSec)
MDTYPE, OTHERMDTYPE, MDTYPEVERSION
MIMETYPE
LABEL
The METS builder enables quick views of the output of external tools. The mdRefs could be pulled into the standard properties viewer, for example.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Eclipse external tools feature currently works on any files that are local resources within the project. This is done via the resources API and using $selected_resource_path as a command parameter.
This feature would make another variable available for the configuration of external tool runs, something like $selected_arrangement_item_path. A variable like that would allow external tools to run on individually selected items in the arrangement.
The text was updated successfully, but these errors were encountered: