Multiple Libraries - Best practice

I have been using iphoto for the last 5 years, At the end of the year I move the library to an external drive and use iphoto buddy to point to it. Now I have 6-7 libraries and I would rather have everything, together.
What has people found out is the best way to combine libraries so that all files end up in 1 directory on the firewire drive and then the best way to move this years photos from the hardrive to the ext drive, later? Or is having multiple libraries the best?
Seems like i am always moving files to and from libraries and i loss any structure and backing it up is a pain. am i missing something here? Thanks in advance
jf

Jeff:
Welcome to the Apple Discussions. The only way at present to merger multiple libraries into one library and retain keywords, rolls, etc, is to use the paid version of iPhoto Library Manager. That will get you one library. If that library gets very large then you might have a storage problem on your boot drive where you want to keep adequate free space for optimal performance. In that case multiple libraries might be best for you.
FWIW here's my photo strategy. I keep my photos in folder based on the shoot (each upload from the camera after an event, usually family get togethers) in folders dated for the event and a brief description. I then import that folder into iPhoto to get a roll with the same name. Since I take the step to upload before importing to iPhoto I also batch rename the files with the international date format: YYYY-MM-DD-01.jpg and so forth.
With iPhoto's new capability of using only aliases for the original/source files (I kept my original folders as a backup on a second drive) I used those original source folders for my combined library by importing those folders into a new V6 library using the alias method. So, for 17,400+ photos that take up 27G on my second drive, my iPhoto library on my boot drive only takes up 8G. This is very valuable for PB owners who can't afford that much library space on the boot drive. The one downside to the alias method is that if you delete a photo from the library the source/original file does not get deleted. Hopefully that will be in the next update.
If the external is dismounted the library is still useable in that you can view thumbnails, create, delete and move albums, add comments and keywords (but with some effort). You can't do anything that requires moving the thumbnails or edit. I've created a workflow to convert from a conventional iPhoto library structure to an alias based one.
The downside to converting as I mentioned is that you will lose keywords, albums, etc. due to the conversion. So it's not for everyone.
Bottom line: for combining/merging libraries iPhoto Library Manager is the only option at the present time. Hope this has bee of some help to you.

Similar Messages

Embedding same images across multiple components, best practices?

Hi Guys,
Once again a great forum.
I have a fairly large dashboard application, built from many
components, from an obvious maintenance point of view this is
preferred.
To keep the look and feel the same across each component I
reuse a lot of the icons, this icons have 3 states, disabled,
normal and hot(rollover)
The mouse roll over and roll out are the same for each set of
icons. At the moment I have each component embed each icon and
repeat the functions.
This is not the optimum way to do this so I'm looking on best
practices. Should I build a separate action script package with all
the embedded images and roll over/out functions. Then import that
in to each component. But then I will embedded ALL the images in
each component. Should I embed all the images in the main container
app, then when flex sees the same image in a compoent will it not
embedded again or will it embed the images again..
In the example below 4 of the components have the same
refresh icon and roll/over states. So this code is repeated (bad
practice) in all 4. Moving to separate action-script package will
make maintenance easier, but as stated above will just one copy get
embedded for the entire app, or will 4 copies get embedded ?
[Embed(source="images/refresh_24.png")]
[Bindable]
private var refreshIcon:Class;
[Embed(source="images/refresh_24_hot.png")]
[Bindable]
private var refreshIconHot:Class;
[Embed(source="images/refresh_24_dis.png")]
[Bindable]
private var refreshIconDis:Class;
private function rollOverRefresh(event:Event):void {
if (event.target.source != refreshIconDis )
{event.target.source = refreshIconHot;}
private function rollOutRefresh(event:Event):void {
If (event.target.source != refreshIconDis )
{event.target.source = refreshIcon;}
}

Flex is able to collate those Embeds so they are only
included once IIRC.
While it may seem like bad practice to include it in each
component, it really isn't, from a code reusability standpoint. But
you could probably continue on that path and create a custom
component <mycontrols:RefreshButton> that has the the embeds
in one place for you.
You could probably also do something similar with style very
easily:
.MyButton {
overSkin="@Embed(source='../assets/orb_over_skin.gif')"
upSkin="@Embed(source='../assets/orb_up_skin.gif')"
downSkin="@Embed(source='../assets/orb_down_skin.gif')"/>
Then apply that style to your button.
You could also put the button into a single SWF file in Flash
and include it that way to reduce the number of embeds. I never
include PNG, JPG, GIF, etc files directly, always SWF as you get
better compression that way IMO. Plus I just find it gives me
greater flexibility...if I want to animate my skins in the future
(button that gleams for instance), I already have SWF's in my code
so no need to change anything out but the SWF.

Setting Disks/Caches/Vault for multiple projects - Best Practices

Please confirm a couple assumptions for me:
1. Because Scratch Disk, Cache and Autosave preferences are all contained in System Settings, I cannot choose different settings for different projects at the same time (i.e. I have to change the settings upon launch of a new project, if I desire a change).
2. It is good practice to set the Video/Render Disks to an external drive, and keep the Cache and Autosave Vault set to the primary drive (e.g. user:Documents:FCP Documents). It is also best practice to save the Project File to your primary drive.
And a question: I see that the Autosave Vault distinguishes between projects, and the Waveform Cache Files distinguishes between clips. But what happens in the Thumbnail Cache Files folder when you have more than one project targeting that folder? Does it lump it into the same file? Overwrite it? Is that something about which I should be concerned?
Thanks!

maxwell wrote:
Please confirm a couple assumptions for me:
1. Because Scratch Disk, Cache and Autosave preferences are all contained in System Settings, I cannot choose different settings for different projects at the same time (i.e. I have to change the settings upon launch of a new project, if I desire a change).
Yes
2. It is good practice to set the Video/Render Disks to an external drive, and keep the Cache and Autosave Vault set to the primary drive (e.g. user:Documents:FCP Documents).
Yes
It is also best practice to save the Project File to your primary drive.
I don't. And I don't think it matters. But you should back that file up to some other drive (like Time Machine).
And a question: I see that the Autosave Vault distinguishes between projects, and the Waveform Cache Files distinguishes between clips. But what happens in the Thumbnail Cache Files folder when you have more than one project targeting that folder? Does it lump it into the same file? Overwrite it? Is that something about which I should be concerned?
I wouldn't worry about it.
o| TOnyTOny |o

SOA 11g Composite Deployment across multiple Instances: Best Practice

Hi,
We have a requirement where we need to deploy the composite acrocss mutilple instances(DEV,TEST,Production) without JDEV.
We are using SOA11.1.3.3(cluster) and linux OS.
Pls suggest me what is the best practice to deploy the SOA composite.
Thanks,
AB

Why there are different ways to deploy the composite in different environment? Depending upon the environment, it's business importance increases and hence access to developers get more restricted and hence there are many ways for deploying. If you are developing an application, you would not like to export a SAR and then login to EM console to deploy it. For a developer it is always very convenient to use IDE itself for deployment and hence JDev is preferably used for Dev instances for deployment.
Once development finishes, developer will check in the artifacts into version control system and if you want to deploy to a test instance then you have to check out the stable version, compile it and package it and then only you can deploy. Hence for test instances, ANT is the preferable mode for deployment. (Remember that developers may not be able to connect to Test environment directly and hence deployment from JDev is not possible)
Once a configuration gets tested in Test env, it's SAR should be checked in into version control system, so that it would not be required to recompile and repackaging of it. This will also make sure that any artifact which is not tested on Test instance, must not go to higher instances (like UAT/PROD). Now in Pre-Prod/UAT/Prod, you may simply access the EM console and deploy the SAR which is already tested in Test instance. Remember that there will be very limited access to such critical environments and hence using Role based access of EM it would be very easy to deploy the resources. Moreover, it is more secure mode of deployment because only those users which have appropriate priviledge, will be able to deploy, and it would also be easier to track the changes.
What is the proc and cons if we use only one way to deploy the composite across the Instances...As such there is no major pros and cons. You may use EM for all environments but it may be a little discomfort for developers/deployers of test environment. You may also use ANT for all the environments but it is not suggested until and unless you have a very good and secure process in place for deployments.
Regards,
Anuj

Integrating Multiple systems - best practice

Hi,
I need to integrate the following scenario let me know the best practice with steps.
Scenario is end to end syncrhonous
A system(supports open tech i.e webservice client) => SAP PI<=>Oracle(call stored procedure) => Update in ECC=> Reponse back to A system (source)
Thanks
My3

Hi Mythree,
First get the request from the web service to pi and then map to stored procedure using synchronous send step (Sync Send1) in bpm and get the response back. Once when you get the response back from oracle then use another synchronus send step. Here take the response from the database and map to ecc (use either a proxy or rfc) which is Sync Send2 in the bpm and get the udpdates back. Once when you get the response back send back the response to source system. The steps in BPM would be like this:
Start --> Receive --> Sync Send1 --> Sync Send2 --> Send --> Stop
These blogs might be useful for this integration:
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
/people/luis.melgar/blog/2008/05/13/synchronous-soap-to-jdbc--end-to-end-walkthrough
Regards,
---Satish

Responsive projects autosizing for multiple devices -- best practices?

While it's a nice idea to have the three different breakpoints on width that allow you to make some major layout changes, I'm having trouble making this work well across multiple devices. With the high resolutions of current mobile devices, this model just doesn't seem to work well. For example, the iPad 2 in landscape mode select the desktop layout, which isn't bad, but in portrait mode gets the tablet layout, which by default is set up to be landscape. I changed the heights for both breakpoints to better fit the iPad, but then the iPhone in landscape gets the tablet layout, requiring a lot of scrolling.
Given the wide range of resolutions on mobile devices, it's not at all clear how this a simplistic mechanism like this could ever work. For one thing, it sure seems like you need to provide for both portrait and landscape layouts on tablets and phones, with Captivate using both width and height to select the best one. Also, is there any way to tell it to fill the screen without scrolling? How about automatically leaving the area clear where there's a status bar (or telling it to hide the status bar)?
I could just create a separate version of the project for each device, but then lose much of the value of creating a Responsive Project in the first place. Have those of you with more experience found good ways to deal with these variables, or is the best option to just create separate versions of the project?

While it's a nice idea to have the three different breakpoints on width that allow you to make some major layout changes, I'm having trouble making this work well across multiple devices. With the high resolutions of current mobile devices, this model just doesn't seem to work well. For example, the iPad 2 in landscape mode select the desktop layout, which isn't bad, but in portrait mode gets the tablet layout, which by default is set up to be landscape. I changed the heights for both breakpoints to better fit the iPad, but then the iPhone in landscape gets the tablet layout, requiring a lot of scrolling.
Given the wide range of resolutions on mobile devices, it's not at all clear how this a simplistic mechanism like this could ever work. For one thing, it sure seems like you need to provide for both portrait and landscape layouts on tablets and phones, with Captivate using both width and height to select the best one. Also, is there any way to tell it to fill the screen without scrolling? How about automatically leaving the area clear where there's a status bar (or telling it to hide the status bar)?
I could just create a separate version of the project for each device, but then lose much of the value of creating a Responsive Project in the first place. Have those of you with more experience found good ways to deal with these variables, or is the best option to just create separate versions of the project?

Archive Libraries - Best Practices?

Trying to figure out how I want to archive Libraries that I am not currently working on to save HD space.
I currently copy the Events in a Library to a new Library titled "XXX Library Archive", and elect not to include render files or optimized media to cut down on file size.
I'm wondering if it's best to simply store that Library on an external hard drive as is, or maybe to create a Disk Image and copy it to that for storage. Are there any benefits to this in terms of file size or stability of storage?
I suppose another option would be to burn that Library (or Disk Image) to DVD instead of having it on an external drive that could crash/become corrupted inthe future.
What do others do with Libraries they are no longer working with, but want to be able to access later?

What you're doing good to me. I'd just add Connsolidta eEvent Files to round up any strays.
Speaking only for myself, I typically put my arcjived projects and /or libraries on hard drives. They don't need to ve expensive drives. I con't use optical media to archive these days.
Russ

JHeadstart and multiples developers -best practices-

Hi,
Which is the best way to use JHeadstart when you have a team of several programmers?
Weve seen that several examples have only one Application Structure File, therefore it is quite difficult that a group of programmers can work in parallel.
Which is the best way to handle this situation? Several Application Structure Files?
Our project will have a team of 4 programmers and certainly we want that they work efficiently with this tool.
Any thought?
Best regards,

Michael et al,
I am working on a big ADF project where we do the following:
- one big Model project with all business component objects, but we organize the EO's, VO's and AM's in separate packages, and for the VO's, we make sub-packages per functional subsystem
- several ViewController projects for each functional subsystem, each having its own struts-config-<subsystemname> file.
- within a ViewController project, we sometimes have multiple Application Structure files generating into the same struts-config file.
Please see this thread for more info on config management tools:
Re: Jheadstart, JDeveloper and CVS and TeamWork
Steven Davelaar,
JHeadstart Team.

Terabyte Plus Libraries - What is the Best Practice?

In my current Aperture library I have 150 gigs and I have only been using it for about a year. Previous to that I used iPhoto for a short time which still has a 60 gig library and previous to that I stored my images in file folders on a windows servers which I have around 500+ gig there. Then there are are those non electronic images which should be scanned in one day.....
My hope was to have import everything into one tool and eventually to have some better organization and management of my images. At the rate I am shooting now it won't be long before I break the terabyte mark and am wondering as I try to pull al these sources together what is the best Practice?
I know I can have more than one library now with Aperture, do folks manage their libraries by themes? Weddings, Family, Commercial, etc? I just picked up a 2 terabyte drive to start moving stuff off my Mac Book but am not sure if I should use the Archive tool to do this or break apart my images into libraries and store them them and just keep a working library on my Mac?
Within Aperture I am using the Project -> Album hierarchy to manage my shoots now as well.
Also, I don't have a ton of video yet, but have started shooting a little, plus have been making slideshows and books now, so I need to start planning for that as well. Just wondering what is the best, most efficient way of large data management with Aperture.
Thanks!

The solution is to avoid the (unfortunately default) Managed Masters and instead use a Referenced Masters Library kept on an internal drive. Back up originals prior to importing and keep Masters off the Library drive. That way the Aperture Library will remain small enough to live on a standard internal drive without overfilling it.
Note that working drives (as opposed to backup-only drives) should not be allowed to exceed ~70% full for ideal speed and stability.
Multiple Libraries is almost always poor images management in a digital world unless all rights to the images, including the right to simply view any image (such as security work), belong exclusively to the client. Usage of multiple Libraries is a big backward step into film-think and very significantly limits the power of digital images management.
-Allen

Best practice for multiple instances of the same BEX query

Hi there,
I'm wondering what's the best way to use multiple instances of the same BEX query. Let me explain what I mean:
I have a dashboard with different queries feeding different period of time such as: week to date, month to date and so on. One query for each since it is based on a user exit.
For each query I want to show different data in different sections of my dashboard. Per example: sales per directors or sales per customer group, sales per day, sales per week and the like.I tried to connect a simple bar chart via a direct connection but with no success due to the multiple lines generated by the addition of the sales director, customer group, week number and so on.
My question is about the way to connect the different queries efficiently in order to show the different data while avoiding multiple useless lines.
The image above shows the query browser where, per example, for a Month to date query there will be mutiple line for each week as well as one line for each director. If, for two different components, I want to show data per week and data per director or other representation what is the best practice:
Add another instance of the same query and only put the week information and another one will only the director info?
Should I bind those to the excel file and use formulas to make final calculations?
Will there be a performance issues for adding different instances of the same query
I have 6 different queries (read 6 user exit that filters time via user exit).
Depending on the best practices there might be 4 instances for each for a total of 24 instances in the query browser.
I hope my question is clear enough, if not please do not hesitate I'll clarify as much as possible.
Regards,
Steve

Hi Steve,
Might be trying for solution for a long time, If i understood your question clear let me clarify you few points.
You are trying to access the bex query which is designed with the exit's in the background based on the logic and trying to call the entire dimensions and key-figures in a single connection. Then you are trying to map those data in the charts.
Steve, try to make more connections based upon the logic and split them. use the same query but split them by sales per customer group, sales per day, sales per week by making three different connections and try. You can merge the prompts from all connections.
Hope this Helps!!!
Sorry if i misunderstood your question.
--SumanT

Having multiple service operations in a single JMS adapter best practice

Hi All,
I am using JDeveloper and SOA Suite 11.1.1.6. I need to read from multiple JMS Topics and transform and enhance the messages through the Mediator and then persist into Database.
My question is
What is the best practice to consume from multiple topics, Should I configure separate JMS adapter for each of the Topic destination
OR
have a single JMS adapter with multiple operations by manually changing the JMS adapter wsdl and jca file?
I find cannot have
Please suggest.
Thanks in advance
Edited by: user5108636 on 15/05/2013 11:36

Hi Vijay,
did you actually test this? When I finish creating a DBAdapter, there is a operation present. Then when I click edit again on the DBAdapter, and I create another select, when I finish only the first operation is gone, and I can only see the one I've created via the last edit.
I dont understand your reply. Can I have two operations, each one with select underneath, in the same adapter?
Edited by: user13604541 on Jan 30, 2012 11:19 AM

Best Practice for External Libraries Shared Libraries and Web Dynrpo

Two blogs have been written on sharing libraries with Web Dynpro DC, but I would
like to know the best practice for doing this.
External libraries seem to work great at compile time, but when deploying there is often an error related to the external library not being a deployed component.
Is there a workaround for this besides creating a shared J2EE library which I have been able to get working? I am not interested in something that works, but really
what are the best practice for this. What is the best way to limit the number of jars that need to be kept in a shared library/ext library. When is sharing ref service/etc a valid approach vs. hunting down the jars in the portal libraries etc and storing in an external library.

Security is mainly about mitigation rather than 100% secure, "We have unknown unknowns". The component needs to talk to SQL Server. You could continue to use http to talk to SQL Server, perhaps even get SOAP Transactions working but personally
I'd have more worries about using such a 'less trodden' path since that is exactly the areas where more security problems are discovered. I don't know about your specific design issues so there might be even more ways to mitigate the risk but in general you're
using a DMZ as a decent way to mitigate risk. I would recommend asking your security team what they'd deem acceptable.
http://pauliom.wordpress.com

Best Practice for using multiple models

Hi Buddies,
     Can u tell me the best practices for using multiple models in single WD application?
    Means --> I am using 3 RFCs on single application for my function. Each time i am importing that RFC model under
    WD --->Models and i did model binding seperately to Component Controller. Is this is the right way to impliment multiple            models in single application ?

It very much depends on your design, but One RFC per model is definitely a no no.
Refer to this document to understand how should you use the model in most efficient way.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/705f2b2e-e77d-2b10-de8a-95f37f4c7022?quicklink=events&overridelayout=true
Thanks
Prashant

How to handle multiple site to site IPsec vpn on ASA, any best practice to to manage multiple ipsec vpn configrations

how to handle multiple site to site IPsec vpn on ASA, any best practice to to manage multiple ipsec vpn configurations
before ver 8.3 and after version 8.3 ...8.4.. 9 versions..

Hi,
To my understanding you should be able to attach the same cryptomap to the other "outside" interface or perhaps alternatively create a new crypto map that you attach only to your new "outside" interface.
Also I think you will probably need to route the remote peer ip of the VPN connection towards the gateway IP address of that new "outside" and also the remote network found behind the VPN connection.
If you attempt to use VPN Client connection instead of L2L VPN connection with the new "outside" interface then you will run into routing problems as naturally you can have 2 default routes active at the sametime (default route would be required on the new "outside" interface if VPN Client was used since you DONT KNOW where the VPN Clients are connecting to your ASA)
Hope this helps
- Jouni

Best practice for running multiple sites on 1 CF install?

Hi-
I'm setting up a new hosting environment (Windows Server 2008 Standard 64 bit VPS configuration, MySQL, IIS 7, CF 9)
Has anyone seen any docs or can anyone suggest best practices for configuring multiple sites in this environment? At this point I'm thinking simple is best, one new site in IIS for each client (domain) and point it to CF.
Given this environment, is anyone aware of any gotchas within the setup of CF 9 on IIS 7?
Thank you in advance,
Rich

There's nothing wrong with that approach. You can run as many IIS sites as you like against a single CF install.
As for installing CF on IIS 7, I recommend that you do the following: install CF 9 without connecting it to IIS, then installing the 9.0.1 upgrade and any hotfixes, then connecting CF to IIS using the web server configuration utility. This will keep you from having to install the IIS 6 compatibility layer that's needed with CF 9 but not with CF 9.0.1.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
http://training.figleaf.com/

Multiple Libraries - Best practice

Similar Messages

Maybe you are looking for