SharePoint
Feedback by UserVoice

Scott Brickey

My feedback

  1. 55 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Sites and Collaboration » Metadata  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Scott Brickey commented  · 

    i believe (though haven't confirmed) that if you have syndicated content types, and use the SendTo feature to copy the file to the other location... that it will retain its metadata.

    if you're doing things like downloading the file, or using Windows Explorer (via WebDAV), then there's no chance... no part of a .TXT file supports metadata, so there's nowhere to store the info when you download it, so there's no metadata when you upload it to its new location.

  2. 18 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestion Archive  ·  Flag idea as inappropriate…  ·  Admin →
    Scott Brickey supported this idea  · 
  3. 10 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SharePoint Administration » Other  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Scott Brickey commented  · 

    @Neil: What about a stretched RESOURCE farm?

    Since there aren't any requirements about RESOURCE FARM latency, the WFE to Service App communication wouldn't necessarily be subject to the same low latency requirements that you mention.

    Or, perhaps, as a feature request: failover resource farms... replication of data between the resource farms (could be as simple as log shipping)... then the consuming farms could simply define one as primary and another as failover?

Feedback and Knowledge Base