esri / arcgis-pro-metadata-toolkit Goto Github PK

• The styles used in the XAML should all be public styles. Refer to the Pro Style Guide for the available public styles.

• The classes for the user controls located inside the Pages folder should reside in this namespace namespace MetadataToolkit.Pages. This is the convention Visual Studio follows.

• A new Custom page should be added in the DAML. Screenshot of what we want is below along with code syntax.

DAML:

  <!-- TODO add your custom pages for Overview here -->

                  <page class="$safeprojectname$.CustomPage">
                    <validation>
                    </validation>
                  </page>

Code behind and xaml:

using ....

namespace MetadataToolkitSix
{

    internal class CustomPageLabel : ISidebarLabel
    {
        string ISidebarLabel.SidebarLabel
        {
            get { return CustomPageLabel.SidebarLabel; }
        }

        public static string SidebarLabel
        {
            get { return "Custom Page"; }
        }
    }
    /// <summary>
    /// Interaction logic for CustomPage.xaml
    /// </summary>
    public partial class CustomPage : EditorPage
    {
        public CustomPage()
        {
            InitializeComponent();

        }

        public override string SidebarLabel
        {
            get { return CustomPageLabel.SidebarLabel; }
        }
    }
}

<p:EditorPage x:Class="MetadataToolkitSix.CustomPage"
             xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
             xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
             xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" 
             xmlns:d="http://schemas.microsoft.com/expression/blend/2008" 
             xmlns:local="clr-namespace:MetadataToolkitSix"
             xmlns:p="clr-namespace:ArcGIS.Desktop.Metadata.Editor.Pages;assembly=ArcGIS.Desktop.Metadata"
             xmlns:extensions="clr-namespace:ArcGIS.Desktop.Extensions;assembly=ArcGIS.Desktop.Extensions"
             mc:Ignorable="d" 
             d:DesignHeight="450" d:DesignWidth="800">
    <UserControl.Resources>
        <ResourceDictionary>
            <ResourceDictionary.MergedDictionaries>
                <extensions:DesignOnlyResourceDictionary Source="pack://application:,,,/ArcGIS.Desktop.Framework;component\Themes\Default.xaml"/>
            </ResourceDictionary.MergedDictionaries>
        </ResourceDictionary>
    </UserControl.Resources>
    <Grid>
        <Grid.RowDefinitions>
            <RowDefinition Height="Auto"></RowDefinition>
            <RowDefinition Height="*"></RowDefinition>
        </Grid.RowDefinitions>
        <DockPanel LastChildFill="True" Grid.Row="0">
            <TextBlock Text="Custom Field:" Margin="10,0,10,0" Style="{DynamicResource Esri_TextBlockRegular}" 
                       DockPanel.Dock="Left"></TextBlock>
            <TextBox HorizontalAlignment="Stretch" VerticalAlignment="Top" Margin="10,0,10,0"></TextBox>

        </DockPanel>
    </Grid>
</p:EditorPage>

I have followed all steps however when I run 'Start' from Visual Studio and ArcGIS Pro opens, there is no custom metadata option to select, only the original base options (Step 10: click the Metadata style drop-down list and click the metadata style for your custom metadata editor, e.g. CustomMetadataEditor1 Metadata Toolkit Editor.)

I am wondering if this is related to being the updated 2.5 version of ArcGIS Pro?
Further reading I see
"NOTE: When an update is provided for ArcGIS Pro, the add-in that provides the custom metadata editor must be recompiled for the current version of ArcGIS Pro."
Is the best approach to simply revert back to 2.4, or two wait for an update of the metadata toolkit to include 2.5?

After installing the toolkit in Visual Studio, I create a new toolkit project.

Compiling is fine and running it starts ArcGIS Pro and I can select the custom style as my style.

for a layer I open the editor and see the custom page loaded with the single field.

Entering data and clicking save results the value not being saved in the metadata. In VS the following error is displayed when selecting the page 'Custom Page':

System.Windows.Data Error: 4 : Cannot find source for binding with reference 'RelativeSource FindAncestor, AncestorType='System.Windows.Controls.ItemsControl', AncestorLevel='1''. BindingExpression:Path=VerticalContentAlignment; DataItem=null; target element is 'ListBoxItem' (Name=''); target property is 'VerticalContentAlignment' (type 'VerticalAlignment')

Hi,

We are missing a few fields in the Toolkit, and can not find their formfields. Not in the other ArcGIS Pro styles either. They are Service-specific and they are:

• svDCP/DCPListCd/@value
• svOperOn
• svParName
• svParOpt
• svRepeat

So, basically the DCPList and the SV Parameters. Fields we did find - and are clearly related - are:

• dataIdInfo > svType > genericName
• dataIdInfo > svCouplType > CouplTypCd/@value
• dataIdInfo > svCouplRes > svResCitId > identCode
• dataIdInfo > svCouplRes > svOpName

For some reason they are mentioned in this files within the Toolkit:

• \Export\ArcGIS_2NPISO19115.xslt
• \Pages\Services.xaml

<!ENTITY % SvOperMD '(svOpName, svDCP+, svDesc?, svInvocName?, svParams*, svConPt+, svOper*)'>

So, even though they are mentioned, their fields do not seem to be implemented. And what seems weird to me: if we can not fill them, why would the Export check whether they exist?

Please advise, we need these fields to be there for implementation of our local ISO standard. At least the DCP-field which is required for us. Thanks in advance.

Add Design mode dictionary to the XAML

There are 3 resource files in the toolkit. Their scope needs to be public. For some reason, the designer cs file that gets generated doesn't work unless the scope is changed public through the Visual Studio UI.

we select two datasets en press the edit metadata button, the shown metadata is the metadata of the database. We expected that two tabs would be opened each showing one of the selected datasets.