Removing ownership & permissions for all files burned to a DVD?

Hello,
I am new to the concept of "ownership & permissions". Do they apply to files burned to DVD or just the files on the computer? I would like to burn some files onto a DVD for backup and I do not want to copy the "ownership & permissions" settings of the files - I just need to backup the files only. I would like to back the files up for a year or two and I am concerned that in the future I may not remember my usernames or passwords to access these files from the burned DVD.
Do "ownership & permissions" apply to files burned onto a DVD? Or does the DVD burning process erase the "ownership & permissions" settings? I tried to burn a DVD from OSX by creating a burn folder and I didn't see any setting that allowed me to remove the "ownership & permissions" settings.
Thank you for any insite into this.

Thanks Mulder,
Here is what I am trying to do:
I do not need to backup any system files - I already have OSX on my original DVD if I needed to re-install. I only need to backup the users' document files and maybe some email folders in the users' libraries.
I set up three accounts:
1. The first account is for admin purposes only.
2. The second is for my own use - it is the account used most often on this computer.
3. The third account is for my family.
Note: I will set up a fourth account for our student renter later.
I will have access to the user names and passwords of all these accounts in case I need to go into the accounts to back up their documents. But the user(s) of the family account will not have my password - so the kids don't accidently erase any of my files.
When working in the second account (which is used most often by myself), I sometimes need to place newly created files into the "document" folder on our family account (the third account). And so I purposely changed the "Ownership & Permissions" on the "document" folder on our family account (the third account) to Group: second account. This allows me (the second account) to place files into the "Document" folder of the third account (the family account). After doing this, I also need to change the "Ownership & Permissions" of any added files to Group: third account so the user(s) of the family account can edit (read and write) the files I add from the second account.
An alternative setup that I decided not to use: I could have made use of the "users/shared" folder for this, however, I do not want everyone to be able to access these files - especially when I set up a fourth account (or even more accounts) in the future. I only would like to share the contents of the third account's "Document" folder between two users (user of the second account and the user of the third account).
Now I will continue the explanation of my setup:
Over time the "Document" folder of the third account (the family account) will become filled with a mixture of files with different Ownerships - some created from the second account and some created from the third account - but all editable from either the second account or the third account by assigning each other access via the "Group" designation in "Ownership & Permission". Because of this mix of files with different ownerships, I could, if I wanted to keep the settings consistent, select the "Document" folder of the third account (the family account) and change the ownership of all enclosed items to the user of the third account by using the "Apply to enclosed items". I would probably also change the "Group" designation to the second account too.
I will be able to make all these changes because I have the user names and passwords for all the accounts.
Now here is my main question:
My concern is that when it comes time to backup the document folders onto DVD, what if in a couple years I forget these passwords? You see, I would rather not copy any "Ownership & Permissions" settings of the files onto the DVD. Lets say that in a couple of years I go back to my DVD backup and need to pull off some old jpeg files and put them onto my computer. When I insert the old backup DVD will it say: "Sorry, you do not have access priviledges to view these files" or something like that? That would be a real problem. These are my own files. Why would I want to risk making an important backup DVD un-useable in the future because of some long-and-forgotten permission settings?
What I would like to do is copy all my files onto DVD for backup in such a way that "Ownership & Permissions" are not copied. Why put the risk of a limitation on your important backups? Is there a better way to do this? What do other people do?
Am I making this more complicated than it has to be? As you can tell, I am a beginner with OSX (and permissions) and I am looking for some advice. Thanks
Mulder, when you wrote:
"If you're trying to backup just selected files, such as your purchased music or applications, etc., then ownership and permissions shouldn't be a problem."
did you mean that ownership and permissions are not copied? That would be great. But I am not sure if that is what you meant to write. Thanks!

Similar Messages

Four Users, One Mac - Want all to have permissions for all files

Our family shares an imac on 10.6.
I want to set the machine up so all for users have access to all files.
Is this as simple as going to Get Info for the Macintosh HD and changing permissions for everybody to read and write and then choosing the "for all enclosed..."
Simple?
Problems down the road?

If you are using v7 of iPhoto them working from the Users/Shared folder will not work unless you want to get busy changing ACLs in the Terminal.
What you mean by 'share'.
If you want the other user to be able to see the pics, but not add to, change or alter your library, then enable Sharing in your iPhoto (Preferences -> Sharing), leave iPhoto running and use Fast User Switching to open the other account. In that account, enable 'Look For Shared Libraries'. Your Library will appear in the other source pane.
Any user can drag a pic from the Shared Library to their own in the iPhoto Window.
Remember iPhoto must be running in both accounts for this to work.
If you want the other user to have the same access to the library as you: to be able to add, edit, organise, keyword etc. The problem here is that OS X works very hard to keep your data safe and secure from the other users. You're trying to beat what's built in to the system. So, to beat the system
Quit iPhoto in both accounts
Move the iPhoto Library Folder to an external HD set to ignore permissions. You could also use a Disk Image or even partition your Hard Disk.
In each account in turn: Hold down the option (or alt) key and launch iPhoto. From the resulting dialogue, select 'Choose Library' and navigate to the new library location. From that point on, this will be the default library location. Both accounts will have full access to the library, in fact, both accounts will 'own' it.
However, there is a catch with this system and it is a significant one. iPhoto is not a multi-user app., it does not have the code to negotiate two users simultaneously writing to the database, and trying will cause db corruption. So only one user at a time, and back up, back up back up.
Lastly: This method seems a little clunky at first, but works very well. Most importantly, it uses the System to do the job for you.
Create a new Account on your Mac, call it Media. Create an iPhoto Library there. (BTW: This will work for iTunes too.)
Enable Sharing on the Library:(Preferences -> Sharing), leave iPhoto running and use Fast User Switching to open the other accounts. In those accounts, enable 'Look For Shared Libraries'. The Library will appear in the other source pane.
This means that both users will be able to see the pics. If you want to use a pic then simply drag it from the shared Library to your own in the iPhoto Window. This means that each user can have their own edits.
If you want to add photos to the Library: Log into the Media account for that purpose.
To make it all seamless: Set your Mac to log into the Media Account automatically. Set iPhoto to launch on log-in. Then switch to your own account using Fast User Switching.
Net result: a Library that's permanently available to all users but also protected. Each user can have their own versions of the pics if they want.
No partitioning, no permissions issues. Uses no extra disk space. What's not to like?
Regards
TD

Remove permissions for a security group for all files and folders in a folder and all subfolders?

I found a script that adds rights to files and folders.
We need to grant administrators rights to a set of folders for a specific project.
ChangePermissions.ps1
# CACLS rights are usually
# F = FullControl
# C = Change
# R = Readonly
# W = Write
$StartingDir=
"C:\Users"
$Principal="Administrators"
$Permission="F"
$Verify=Read-Host `n "You are about to change permissions
on all" `
"files starting at"$StartingDir.ToUpper() `n "for security"`
"principal"$Principal.ToUpper() `
"with new right of"$Permission.ToUpper()"."`n `
"Do you want to continue? [Y,N]"
if ($Verify -eq "Y") {
foreach ($file in $(Get-ChildItem $StartingDir -recurse)) {
#display filename and old permissions
write-Host -foregroundcolor Yellow $file.FullName
#uncomment if you want to see old permissions
#CACLS $file.FullName
#ADD new permission with CACLS
CACLS $file.FullName /E /P "${Principal}:${Permission}" >$NULL
#display new permissions
Write-Host -foregroundcolor Green "New Permissions"
CACLS $file.FullName
When the project is over, we need to undo the changes and remove administrators permissions from the same group of folders.
How do we change the script to remove administrators group members instead of adding?

I'm not sure I understand how to use that example script to undo the changes in the script I posted..
Is there a way to just change a few lines in the first script so that it removes instead of adding the administrators group?
This line appears to be the line that adds permissions:
#ADD new permission with CACLS
CACLS $file.FullName /E /P "${Principal}:${Permission}" >$NULL
What would be the syntax to remove the permissions
$Principal="Administrators"
$Permission="F"
from files and folders in $StartingDir= "C:\Users"
and everything below it?

It should be possible to set default behavior for all file types

It should be possible to set a default action for all file types. I'm so tired of having to manually sit and say "save this file" because Firefail always defaults to "open with" and has disabled the "Do this automatically for files like this from now on."
And spare me the zealotry religious excuses for why its the fault of websites and not Firefail
''edited to remove swearing''

I do want users to have full control to be able to set any folder view they want by using Apply to Folders; I just want to set the initial/default view to Detail because that matches what the majority of my users want.
That is, what registry setting changes when I go to a picture folder, change the view to Detail, and click Apply to Folders? Having done that, I still retain the ability to change it to some other view and apply that to folders. But what registry setting
represents the change I just made when applying Detail view to all Picture folders.?
This settings is simple via GUI, but it is related a lot of registry keys, I made a test in my machine, capture the "Apply to Folders" process using Regshot tool (this is a small tool which can compare the regsitry changes after you change some
settings), and this is the result:
this is part of the registry changes, a plenty of registry keys and values need to be changed. hard to list them here. if you have interests, I recommend the tool Regshot, it can help you capture the regsitry changes.
NOTE: Please Note: The third-party product discussed here is manufactured by a company that is
independent of Microsoft. We make no warranty, implied or otherwise, regarding this product's
performance or reliability.
Yolanda Zhu
TechNet Community Support

When setting up permissions for application files--URGENT

Hello All,
when setting up permissions for application files,
Is this following permisson appropriate?
If application files are owned by a single owner,
that owner should be the oracle user.
DN

Here is my question again.
when setting up permission for application file, which permission is
appropriate?
a) If application files are owned by a sigle owner,that owner should be oracle
user.
b) Application files should be owned by oracle user
c) Application files should be owned by single user.

Using an * for all file extensions in a class selection parser

Using iFS 1.1.9....
I have successfully gotten a custom document class created using
xml. I have used the following code to set up the parser, etc.
If I use a specific file extension like txt the parser will
upload the file as my custom class. However, if I use * for all
file extensions the parser uploads all files as Document class.
Here is what I am using:
<?xml version='1.0' standalone = 'yes'?>

<PropertyBundle>
<Update
Reftype='ValueDefault'>ParserLookupbyfileExtension</Update>
<Properties>
<Property Action = 'add'>
<Name>*</Name>
<Value Datatyupe = 'String'>
oracle.ifs.beans.parsers.ClassSelectionParser
</Value>
</Property>
</Properties>
</Propertybundle>
When the above is uploaded I can go into iFS Manager and see
that the parser has been registered with * as the file extention.
I then upload this:
<?xml version='1.0' standalone = 'yes'?>

<PropertyBundle>
<Update
Reftype='ValueDefault'>IFS.PARSER.ObjectTypeLookpByFileExtension
</Update>
<Properties>
<Property Action = 'add'>
<Name>*</Name>
<Value Datatype='String'>QualDocument</Value>
</Property>
</Properties>
</PropertyBundle>
If I have txt or some other extension for the Name in place of
the * and upload a document it will put the class as
QualDocument. If I have the * it defaults to Document.
Is there a way to have the parser make all uploaded documents
QualDocument instead of Document without doing this for each and
every possible file extension?
Thanks.

Using iFS 1.1.9....
I have successfully gotten a custom document class created using
xml. I have used the following code to set up the parser, etc.
If I use a specific file extension like txt the parser will
upload the file as my custom class. However, if I use * for all
file extensions the parser uploads all files as Document class.
Here is what I am using:
<?xml version='1.0' standalone = 'yes'?>

<PropertyBundle>
<Update
Reftype='ValueDefault'>ParserLookupbyfileExtension</Update>
<Properties>
<Property Action = 'add'>
<Name>*</Name>
<Value Datatyupe = 'String'>
oracle.ifs.beans.parsers.ClassSelectionParser
</Value>
</Property>
</Properties>
</Propertybundle>
When the above is uploaded I can go into iFS Manager and see
that the parser has been registered with * as the file extention.
I then upload this:
<?xml version='1.0' standalone = 'yes'?>

<PropertyBundle>
<Update
Reftype='ValueDefault'>IFS.PARSER.ObjectTypeLookpByFileExtension
</Update>
<Properties>
<Property Action = 'add'>
<Name>*</Name>
<Value Datatype='String'>QualDocument</Value>
</Property>
</Properties>
</PropertyBundle>
If I have txt or some other extension for the Name in place of
the * and upload a document it will put the class as
QualDocument. If I have the * it defaults to Document.
Is there a way to have the parser make all uploaded documents
QualDocument instead of Document without doing this for each and
every possible file extension?
Thanks.

How to get the file size (in bytes) for all files in a directory?

How to get the file size (in bytes) for all files in a directory?
The following code does not work. isFile() does NOT recognize files as files but only as directories. Why?
Furthermore the size is not retrieved correctly.
How do I have to code it otherwise? Is there a way of not converting f-to-string-to-File again but iterate over all file objects instead?
Thank you
Peter
java.io.File f = new java.io.File("D:/todo/");
files = f.list();
for (int i = 0; i < files.length; i++) {
System.out.println("fn=" + files);
if (new File(files[i]).isFile())
     System.out.println("file[" + i + "]=" + files[i] + " size=" + (new File(files[i])).length() ); }

pstein wrote:
...The following code does not work. Work?! It does not even compile! Please consider posting code in the form of an SSCCE in future.
Here is an SSCCE.
import java.io.File;
class ListFiles {
    public static void main(String[] args) {
        java.io.File f = new java.io.File("/media/disk");
        // provides only the file names, not the path/name!
        //String[] files = f.list();
        File[] files = f.listFiles();
        for (int i = 0; i < files.length; i++) {
            System.out.println("fn=" + files);
if (files[i].isFile()) {
System.out.println(
"file[" +
i +
"]=" +
files[i] +
" size=" +
(files[i]).length() );
}Edit 1:
Also, in future, when posting code, code snippets, HTML/XML or input/output, please use the code tags to retain the indentation and formatting.   To do that, select the code and click the CODE button seen on the Plain Text tab of the message posting form. It took me longer to clean up that code and turn it into an SSCCE, than it took to +solve the problem.+
Edited by: AndrewThompson64 on Jul 21, 2009 8:47 AM

How to update managed metadata column for all file in document library using powershell

Hi,
How to update managed metadata column for all file in document library using powershell?
Any help on it.
Thanks & REgards
Poomani Sankaran

Hi TanPart,
I have changed the code which you have give in order to get the files from SharePoint 2010 Foundation Document Library.But i am getting below error in powershell.
Property 'ListItemCollectionPosition' cannot be found on this object; make sure it exists and is settable.
Could you tell me which is the issues in it?
See the code below.
$web = Get-SPWeb http://ntmoss2010:9090/Site
$list = $web.Lists["DocLib"]
$query = New-Object Microsoft.SharePoint.SPQuery
$query.ViewAttributes = "Scope='Recursive'";
$query.RowLimit = 2000
$caml = '<Where><Contains><FieldRef Name="Title" /><Value Type="Text">Process Documents/Delivery</Value></Contains></Where>' +
        '<OrderBy Override="TRUE"><FieldRef Name="ID"/></OrderBy>'
$query.Query = $caml
do
    $listItems = $list.GetItems($query)
    $spQuery.ListItemCollectionPosition = $listItems.ListItemCollectionPosition
    foreach($item in $listItems)
        #Cast to SPListItem to avoid ambiguous overload error
        $spItem = [Microsoft.SharePoint.SPListItem]$item;
        Write-Host $spItem.Title
while ($spQuery.ListItemCollectionPosition -ne $null)
Thanks & Regards
Poomani Sankaran

How do I save my CMYK font settings & make it avaliable for all files ?

How do I save my CMYK font settings & make it avaliable for all files ? (adobe PS indesign file)

Could you explain what you want to do a little bit better? CMYK and fonts aren't really related to each other.
Also, are you using Photoshop or InDesign?

How to make a category required for all files created within a folder

I've defined a category. It has attributes which have been flagged as required.
When I view the properies of a particular workspace (library), the category is shown as available to the workspace. However, the category is not shown as required. And the "required" checkbox is not clickable.
So .. how, from the OCS DHTML applet, do I make a particular category a required category for all files in a folder?

Perhaps the Category Attribute is not marked as "configurable" when it was created. You can check this by "switching into Admin Mode" and drilling down the Categories using "Manage Categories" link. Check if the category attribute is marked as configurable or not.
Ravikiran

Can't export as Html (Waiting for all files to be ready...)

Made a bunch of updates last night to a client site. Everything looks great except I can't export as Html. Had my sister try to export on her computer and we both get to 87%, then it permanently stalls, saying "Waiting for all files to be ready" (See screenshots). We've ensured that no files are open or being previewed. We've rebooted and tried saving to a different location, all with no change, we still get to the 87% mark and stop. Please help. I have a client waiting for this site update.
Details:
Windows 7
Sony Vaio
Muse Version - 4.1 Build 8 *see screenshot
****Update:
I can preview the entire site in a browser as well as preview each page individually, but cannot finish a html export past 87%.

Odd are if you wait long enough, potentially a few hours, it will complete.
This huge performance hit sounds exactly like a bug that's fixed for the Muse CC 5.0 release due out next week. Sorry for the inconvenience.

"Date Modified" for all files being changed if "Automatically write to XMP" is on

Recently upgraded from LR3 (v3.4.1) from LR2 on OSX 10.6.8 and have always had Catalog Settings > Automatically write changes into XMP turned on.
When browsing existing JPG files in my Library (no Develop changes, no keywording, no Presets, no Import), LR3 is writing to disk — i.e., when I look at files in Finder, almost every viewed file’s “Date Modified” is being set to today’s date and time. (It actually creates a .swp file, then changes it's name back to .jpg)
This is really bad, as it's making it impossible for me to use Finder to figure out when I last worked with a file, it is triggering needless Time Machine and Backblaze backups, and unnecessarily churning my disk.
If I turn off "Automatically write..." this behavior stops. Per David Marx at thelightroomlab.com, I tried turning off this preference, manually doing a "Save Metadata to File" for all files, letting that complete, then turning the preference back on. This does not solve the problem.
Per a suggestion at photoshop.com, I used ExifTool to see what changes LR was writing to a sample file; from the diff below, you can see that LR is adding a bunch of new fields as well as moving other fields around. But my point is that LR3 should never overwrite a file on disk if all I am doing is browsing thru them.
Is anyone else seeing this? Any ideas would be greatly appreciated!
-- David
diff Exif5609_original Exif5609_update
2c2
< FileName: DSC_5609_original.JPG
> FileName: DSC_5609_update.JPG
5,6c5,6
< FileModifyDate: 2009:11:27 21:32:54-08:00
< FilePermissions: rwxr-xr-x
> FileModifyDate: 2011:08:07 22:06:47-07:00
> FilePermissions: rw-r--r--
27a28,29
> ShutterSpeedValue: 1/200
> ApertureValue: 7.1
55d56
< SerialNumber: 3209521
75d75
< Lens: 18-200mm f/3.5-5.6
185,188d184
< UserComment:
< SubSecTime: 00
< SubSecTimeOriginal: 00
< SubSecTimeDigitized: 00
211a208,299
> XMPToolkit: Adobe XMP Core 5.2-c004 1.136881, 2010/06/10-18:11:35
> CreatorTool: Ver.1.00
> MetadataDate: 2011:08:07 22:06:47-07:00
> SerialNumber: 3209521
> LensInfo: 18-200mm f/3.5-5.6
> Lens: 18.0-200.0 mm f/3.5-5.6
> ImageNumber: 26634
> RawFileName: DSC_5609.JPG
> SavedSettingsName: Import
> SavedSettingsType: Snapshot
> SavedSettingsParametersVersion: 6.4.1
> SavedSettingsParametersProcessVersion: 5.0
> SavedSettingsParametersWhiteBalance: As Shot
> SavedSettingsParametersIncrementalTemperature: 0
> SavedSettingsParametersIncrementalTint: 0
> SavedSettingsParametersExposure: 0.00
> SavedSettingsParametersShadows: 0
> SavedSettingsParametersBrightness: 0
> SavedSettingsParametersContrast: 0
> SavedSettingsParametersSaturation: 0
> SavedSettingsParametersSharpness: 0
> SavedSettingsParametersLuminanceSmoothing: 0
> SavedSettingsParametersColorNoiseReduction: 0
> SavedSettingsParametersChromaticAberrationR: 0
> SavedSettingsParametersChromaticAberrationB: 0
> SavedSettingsParametersVignetteAmount: 0
> SavedSettingsParametersShadowTint: 0
> SavedSettingsParametersRedHue: 0
> SavedSettingsParametersRedSaturation: 0
> SavedSettingsParametersGreenHue: 0
> SavedSettingsParametersGreenSaturation: 0
> SavedSettingsParametersBlueHue: 0
> SavedSettingsParametersBlueSaturation: 0
> SavedSettingsParametersFillLight: 0
> SavedSettingsParametersVibrance: 0
> SavedSettingsParametersHighlightRecovery: 0
> SavedSettingsParametersClarity: 0
> SavedSettingsParametersDefringe: 0
> SavedSettingsParametersHueAdjustmentRed: 0
> SavedSettingsParametersHueAdjustmentOrange: 0
> SavedSettingsParametersHueAdjustmentYellow: 0
> SavedSettingsParametersHueAdjustmentGreen: 0
> SavedSettingsParametersHueAdjustmentAqua: 0
> SavedSettingsParametersHueAdjustmentBlue: 0
> SavedSettingsParametersHueAdjustmentPurple: 0
> SavedSettingsParametersHueAdjustmentMagenta: 0
> SavedSettingsParametersSaturationAdjustmentRed: 0
> SavedSettingsParametersSaturationAdjustmentOrange: 0
> SavedSettingsParametersSaturationAdjustmentYellow: 0
> SavedSettingsParametersSaturationAdjustmentGreen: 0
> SavedSettingsParametersSaturationAdjustmentAqua: 0
> SavedSettingsParametersSaturationAdjustmentBlue: 0
> SavedSettingsParametersSaturationAdjustmentPurple: 0
> SavedSettingsParametersSaturationAdjustmentMagenta: 0
> SavedSettingsParametersLuminanceAdjustmentRed: 0
> SavedSettingsParametersLuminanceAdjustmentOrange: 0
> SavedSettingsParametersLuminanceAdjustmentYellow: 0
> SavedSettingsParametersLuminanceAdjustmentGreen: 0
> SavedSettingsParametersLuminanceAdjustmentAqua: 0
> SavedSettingsParametersLuminanceAdjustmentBlue: 0
> SavedSettingsParametersLuminanceAdjustmentPurple: 0
> SavedSettingsParametersLuminanceAdjustmentMagenta: 0
> SavedSettingsParametersSplitToningShadowHue: 0
> SavedSettingsParametersSplitToningShadowSaturation: 0
> SavedSettingsParametersSplitToningHighlightHue: 0
> SavedSettingsParametersSplitToningHighlightSaturation: 0
> SavedSettingsParametersSplitToningBalance: 0
> SavedSettingsParametersParametricShadows: 0
> SavedSettingsParametersParametricDarks: 0
> SavedSettingsParametersParametricLights: 0
> SavedSettingsParametersParametricHighlights: 0
> SavedSettingsParametersParametricShadowSplit: 25
> SavedSettingsParametersParametricMidtoneSplit: 50
> SavedSettingsParametersParametricHighlightSplit: 75
> SavedSettingsParametersSharpenRadius: +1.0
> SavedSettingsParametersSharpenDetail: 25
> SavedSettingsParametersSharpenEdgeMasking: 0
> SavedSettingsParametersPostCropVignetteAmount: 0
> SavedSettingsParametersGrainAmount: 0
> SavedSettingsParametersLensProfileEnable: 0
> SavedSettingsParametersLensManualDistortionAmount: 0
> SavedSettingsParametersPerspectiveVertical: 0
> SavedSettingsParametersPerspectiveHorizontal: 0
> SavedSettingsParametersPerspectiveRotate: 0.0
> SavedSettingsParametersPerspectiveScale: 100
> SavedSettingsParametersConvertToGrayscale: False
> SavedSettingsParametersToneCurveName: Linear
> SavedSettingsParametersCameraProfile: Embedded
> SavedSettingsParametersCameraProfileDigest: D6AF5AEA62557FCE88BC099788BBD3CC
> SavedSettingsParametersLensProfileSetup: LensDefaults
> SavedSettingsParametersToneCurve: 0, 0, 255, 255
> IPTCDigest: d41d8cd98f00b204e9800998ecf8427e
228,230d315
< SubSecCreateDate: 2009:11:27 21:32:54.00
< SubSecDateTimeOriginal: 2009:11:27 21:32:54.00
< SubSecModifyDate: 2009:11:27 21:32:54.00
http://feedback.photoshop.com/photoshop_family/topics/lr3_date_modified_for_all_files_bein g_updated_when_browsing_photos_if_catalog_settings_automatically_write_changes_into_xmp_is /replies/6313647

clvrmnky wrote:
davidpope007 wrote:
Then when LR3 loaded my old LR2 images into memory, it "dirtied" the in-memory copy of the file by adding in these new LR3 XMP fields. Then, because I had "Automatically write XMP" on, it said "I better write these changes to disk".
Yuck. As a former software engineer, this is very bad software engineering.
It should wait until the user dirties the file (via Develop, keywords, etc.) before presuming to add a bunch of metadata fields that are unique to the new version of LR3.
Well, I'm a current software developer, and this is, really, a perfectly reasonable thing to do. It is a reasonable trade-off for a convenient feature required by a small subset of users.
Yes, in most cases the in-memory copy should "never" be dirtied unless the user makes a gesture of some sort, but like I said earlier, this option (once set by the user) sets up the situation where this gesture becomes implicit. This is a clear trade-off for the sake of convenience. And if the XMP is out of date and needs to be updated en masse, so be it.
The fact is, there is no easy way around this. Do we save up /every/ dirty buffer somehow until you make a gesture that /might/ require the XMP to be up-to-date before acting on that gesture? Now we have to worry about unflushed buffers if something goes wrong and the app exits. Do we save the buffers to the DB? Now we have to block some calls to make another blocking call to flush some or all of those to DB, and then write some or all of it out to one or more files. In what order? What if there is a gesture to have X files with up-to-date XMP and some or all of those are in unflushed buffers, unflushed DB writes or we have to wait for the DB.
As you can see, this is a transactionality nightmare, and the easiest and safest thing to get what the user wants (i.e., up-to-date XMP for the purpose of talking to a third-party XMP aware app) is to simply update the sidecar or XMP block in an atomic manner using the correct file IO. The file will have to change at some point, so it may as well be now.
[Thanks to both of you for your detailed replies. I am aware of the need for tradeoffs so when you say the approach taken is quite reasonable, I do believe you. I also apologize in advance for the length of the following and am extremely aware of the time it must have taken you to compose the above replies, but I'm going to add a bit more, if only for my own piece of mind and in hopes of coming up with a solution for my workflow.]
From my naive point of view, I was expecting the answer to be simply "don't raise the XMPDirtyFlag upon reading in a file". Obviously if your architecture requires you to "upgrade to latest XMP format" upon read, and another part of the system auto-detects "out of date XMP", then it's going to write those changes to disk.
But it didn't need to be designed that way. LR obviously has mechanisms to know when a user has made a change to XMP so it is able to write XMP changes to disk only when necessary.
The promise (to me) of "Automatically Write XMP changes to disk" was to auto-save my changes, and not those made for any internal (i.e., XMP versioning related) changes.
Perhaps the premise is that it is LR3's job to update an individual file's XMP to the latest version so that other XMP-aware apps can make use of it? I would argue that those third-party XMP-aware apps already have to know how to deal with all prior versions of XMP, so LR3 should just leave well enough alone.
You asked if my problem with your approach was that it was "inelegant"; not at all, it is based on my own perception of what I need from my workflow, so let me describe that so maybe we can find a better way:
* Part of the appeal of LR to me is that it preserves my original file as it came off the memory card, allowing me to move to a different workflow/toolset in 2025 if I choose to do so
* However, with all of changes contained in a single database file, I'm concerned about rare (but possible) corruption, so to mitigate this risk, I let LR backup my database weekly and it's also backed up continuously in the cloud via Backblaze
* Even with backups of the database, there is still a chance that I could lose changes made to individual files (e.g., LR corrupts the DB and I have to go back to last week's DB)
* Thus the appeal of the "auto-write to XMP" flag -- that way critical changes (develop, crop, keywords) are saved on a per-file basis; I liked the "automatic" part of this (as opposed to a manual save) because then I don't have to teach others in my family how to manually save XMP changes
* A nice side-effect of this setting is now when I use Finder to find a file and double-click on it to edit it in Photoshop, all my develop changes are right there; (in other words, I like the flexibility of not having to fire up LR in order to just invoke PS from within it); also when I use Bridge I see all the keywords there
* So with LR2, I had gotten used to what I thought was the best of all worlds -- autosave of changes at the file level via XMP + raw negatives untouched (i.e., Date Modified == the date I took the picture); this allows me to use operating-system-level tools -- Finder -- to locate/search for files
* Now I upgrade to LR3 and I'm finally now understanding that a concept "XMP versioning" is going to result in changes to many, but not all my files. (That's something else that's annoying about this issue -- I open up the Grid and browse a folder of files, and only seemingly random ones I've cursored over seem to get written to disk -- if it's so urgent that LR3 update the XMP, then it should do it for all the files in the catalog or at least in that directory)
Here's a screenshot from Finder of what I see everytime I look at this folder:
* So now I have to assume that each new version of XMP and/or LR is going to touch my files on disk. Sigh.
* What I don't like about this is that it is ruining the promise of "untouched raw negative". Yes, the image data is untouched -- which I agree is most of the benefit; but the file has been touched.
* Perhaps you might empathize a bit more if you imagined that someone went thru all your source code or Word files and randomly changed the date to "today" because you upgraded compilers or moved to Word 2011.
I agree all of this would be solved by having an XMP sidecar file for JPGs, but you indicate that's not going to happen.
You've also alluded to the solution of "resetting the Date Modifed" to it's original value -- which I believe is what Finder does when you move or copy a file -- but that that is fraught with issues as well. I believe you when you say there are issues, but again the naive part of me wonders why that soultion would be so bad...
I just thought of another potential solution -- turning on Date Created in Finder -- but it turns out that's changed, too.
I am really at a loss as to what to do and would welcome your suggestions.
Thanks again and kind regards,
-- David

Setting CUIC user permissions for all reports at once

Hi all,
We are using CUIC 8.0(4) Standard Edition and trying to set CUIC user permissions, such as Read, Exec and Write, for reports.
If we need to give access to all reports then we should set permissions for each report separately.
Is there any way to set those permissions for all reports at once?
We attempted to set Read, Exec and Write premissions for the Reports, Stock and UCCE folders but no luck.
Thanks.
Nikolay

Hi all,
We are using CUIC 8.0(4) Standard Edition and trying to set CUIC user permissions, such as Read, Exec and Write, for reports.
If we need to give access to all reports then we should set permissions for each report separately.
Is there any way to set those permissions for all reports at once?
We attempted to set Read, Exec and Write premissions for the Reports, Stock and UCCE folders but no luck.
Thanks.
Nikolay

The specified file or folder name is too long,the url path for all files and folders

The specified file or folder name is too long,the url path for all files and folders must be 260 character or less
can we increase this limit?
MCTS,ITIL

Hi,
As I understand, you want to increase the length of URL path in SharePoint 2010.
Per my knowledge, this limit cannot be increased. SharePoint limits URL length because all relative URL links are stored in the clear forms on the SharePoint content DB and often this links are used as primary keys to link one table with another. Fields
which are used to store these links (for instance tp_DirName from the AllUserData table) allow storing only 256 characters.
There are several ways that you can resolve or mitigate URL length problems in the SharePoint Server 2010 environment. The following list provides suggestions:
1. Upgrade all the end-user browsers to Internet Explorer 8, which has a longer URL length limit.
2. Use shorter names for sites, folders, and documents and control the depth of the site and folder structures to reduce the lengths of URLs.
3. If possible or allowed, use ASCII names for sites, folders, and documents. This will avoid situations where the URL will be lengthened by being encoded.
4. To reduce the risk that the SharePoint Server 2010 end-users will encounter problems because of URL length limitations, we recommend that you apply the following effective limits in the deployment:
256 Unicode (UTF-16) Code units - the effective file path length limitation, including a domain/server name
128 Unicode (UTF-16) Code units - the path component length limitation
More reference:
http://technet.microsoft.com/en-us/library/ff919564(v=office.14).aspx
http://sharepointknowledgebase.blogspot.in/2013/04/url-path-length-restrictions-in.html#.VKJN53BJA
Best regards,
Sara Fan

ITunes drivers for importing and burning CDs and DVDs are missing

Hi,
I recently switched from a relatively small drive to a much larger one and had the larger drive taking image of the older drive. All of my older programs are now back up to working but I can still can't burn a CD.
I get the following error message "the registry settings used by the iTunes drivers for importing and burning CDs and DVDs are missing. This can happen as a result of installing other CD burning software. Please reinstall iTunes."
I have reinstalled iTunes a few times and have done soft and hard reboots but still no luck. Any ideas on the simplest way to resolve this matter?
Thank you
this is the result of the diagnostic:
Microsoft Windows 7 x64 Home Premium Edition Service Pack 1 (Build 7601)
System manufacturer System Product Name
iTunes 11.3.0.54
QuickTime 7.7.5
FairPlay 2.6.12
Apple Application Support 3.0.5
iPod Updater Library 11.1f5
CD Driver 2.2.3.0
CD Driver DLL 2.1.3.1
Apple Mobile Device 7.1.2.6
Apple Mobile Device Driver 1.64.0.0
Bonjour 3.0.0.10 (333.10)
Gracenote SDK 1.9.6.502
Gracenote MusicID 1.9.6.115
Gracenote Submit 1.9.6.143
Gracenote DSP 1.9.6.45
iTunes Serial Number 0031B3A80E383418
Current user is not an administrator.
The current local date and time is 2014-08-26 07:06:48.
iTunes is not running in safe mode.
WebKit accelerated compositing is enabled.
HDCP is supported.
Core Media is supported.
Video Display Information
NVIDIA, NVIDIA GeForce GTX 570
**** External Plug-ins Information ****
No external plug-ins installed.
iPodService 11.3.0.54 (x64) is currently running.
iTunesHelper 11.3.0.54 is currently running.
Apple Mobile Device service 3.3.0.0 is currently running.
**** CD/DVD Drive Tests ****
No drivers in LowerFilters.
No drivers in UpperFilters.
Failed loading CD / DVD drives, error -43. Try doing a repair install on iTunes from the “Add or Remove Programs” control panel.

You posted here --> Apple Support Communities / iTunes / iTunes for Mac
I will request this be moved.

Removing ownership & permissions for all files burned to a DVD?

Similar Messages

Maybe you are looking for